Modules
Module management for PowerShell Universal.
Last updated
Module management for PowerShell Universal.
Last updated
The Modules page provides information about the modules installed in the system.
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.
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.
PowerShell Universal integrates with the PackageManagement v3 module and will automatically pick up on registered package sources. For example, you can register a package source with the command below.
Once the source has been registered, it will be shown within the drop down on the modules page.
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.
An example module can be found here.
Modules can contain PowerShell Universal resources such as scripts, APIs and apps. Adding these modules to your environment will automatically add these resources to your PowerShell Universal instance. These resources will be read-only within the environment. To remove them, you will have to remove the module.
Within the Admin Console, click Platform \ Modules and then select PowerShell Universal Modules.
Click the download button on the left size of the module to install it. Once installed, read-only resources will be added to your environment.
You can also save modules directly to the PowerShell Universal repository folder.
Below is an example of the layout of a Universal module. If the module contains the .universal folder, resources will be loaded from it automatically.
Resources cannot use paths and must use the module and command name to associate resources with their respective scripts.
For example, the above scripts.ps1 file would have to be written such as this.
Within PSUModule.psm1, you would need to define the Start-MyScript function. This is the function that will be called when running the script.
When creating modules that extend PowerShell Universal, you can include the PowerShellUniversal tag in your module manifest for them to be listed within the PowerShell Universal Modules page and within the PSU admin console.
Publish modules to the PowerShell Gallery in order to share them with others.
PowerShell Universal will add the repository's Modules directory to the $ENV:PSModulePath for all environments. Adding modules to this directory will ensure the module is available to any PowerShell process running with PowerShell Universal.
This section includes information about certain modules and their use within PowerShell Universal.
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.
Update the ActiveDirectory module to version 1.0.1.0 which has PowerShell Core support
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
