Modules

Search…
Modules
Module management for PowerShell Universal.
The Modules page provides information about the modules installed in the system. 
Viewing Modules
You can view and search the modules accessible by PowerShell Universal by visiting the Platform \ Modules page. Searching provides a wildcard result of the modules found in each of the environments defined within PowerShell Universal. 
Install Modules from the Gallery
Modules can be installed from the PowerShell Gallery. To search for a module, you can change the drop down next to the search box from Local to PowerShell Gallery. Searches conducted will run against the Gallery rather than locally. 
Once a module is found, you'll be able to click the Install button to save it locally. Modules installed in this method will be installed into the Repository directory under Modules. 
Creating Modules 
You can also create modules directly in PowerShell Universal. These modules will be created in the Repository directory under Modules. 
These modules will be available in all environments.
To create a new module navigate to Platform \ Modules and click Create New Module. Define the module name and version. 
Once created, the module will be listed under Universal Modules with the option to edit properties and content as well as delete the module. 
When editing the module, it will open a code editor where you can define functions, variables and aliases to export. 
Module Information
This section includes information about certain modules and their use within PowerShell Universal.
ActiveDirectory
The ActiveDirectory module supports native PowerShell 7 support when using the 1.0.1.0 version. When using the 1.0.0.0 version, the Windows Compatibility layer is used when running the commands in PowerShell 7 and the Integrated environment. This can cause problems within PowerShell Universal. Our guidance for this module is as follows. 
Windows Server 2019 and above
Update the ActiveDirectory module to version 1.0.1.0 which has PowerShell Core support
Windows Server 2016 and below
Choose from 1 of 2 available workarounds:
Include the -SkipEditionCheck parameter with Import-Module when importing the ActiveDirectory module
Use the Windows PowerShell 5.1 environment instead of Integrated/PowerShell Core
Further Reading
​https://devblogs.microsoft.com/powershell/increased-windows-modules-coverage-with-powershell-core-6-1/​
​
Last modified 1mo ago
Copy link
Outline
Viewing Modules
Install Modules from the Gallery
Creating Modules
Module Information
ActiveDirectory