How to update Azure PowerShell modules in Azure Automation
The most common Azure PowerShell modules are provided by default in each Automation account. The Azure team updates the Azure modules regularly, so in the Automation account you are provided a way to update the modules in the account when new versions are available from the portal.
Because modules are updated regularly by the product group, changes can occur with the included cmdlets, which may negatively impact your runbooks depending on the type of change, such as renaming a parameter or deprecating a cmdlet entirely. To avoid impacting your runbooks and the processes they automate, it is recommended that you test and validate before proceeding. If you do not have a dedicated Automation account intended for this purpose, consider creating one so that you can test many different scenarios and permutations during the development of your runbooks, in addition to iterative changes such as updating the PowerShell modules. After the results are validated and you have applied any changes required, proceed with coordinating the migration of any runbooks that required modification and perform the following update as described in production.
A new Automation account might not contain the latest modules.
Updating Azure Modules
In the Modules page of your Automation account, there is an option called Update Azure Modules. It is always enabled.
Click Update Azure Modules, a confirmation notification is shown that asks if you want to continue.
Click Yes and the module update process begins. The update process takes about 15-20 minutes to update the following modules:
If the modules are already up-to-date, then the process completes in a few seconds. When the update process completes, you are notified.
Azure Automation uses the latest modules in your Automation account when a new scheduled job is run.
If you use cmdlets from these Azure PowerShell modules in your runbooks, you want to run this update process every month or so to make sure that you have the latest modules. Azure Automation uses the AzureRunAsConnection connection to authenticate when updating the modules, if the service principal is expired or no longer exists on the subscription level, the module update will fail.
To learn more about Integration Modules and how to create custom modules to further integrate Automation with other systems, services, or solutions, see Integration Modules.