Can you remember 2015? Apple launched the Apple Watch, Microsoft launched Windows 10, and we announced AzureRM v1.0!
After years of service and coexistence with its replacement, the time has come to share the next steps we are taking with AzureRM.
In 2018, we introduced a new generation of PowerShell modules named “Az”, bringing several advantages:
After two years of existence and continuous improvements, the Az PowerShell modules feature the following benefits:
Prevention of man-in-the-middle attack type
Support authentication with ADFS 2019
Username and password authentication in PowerShell 7
Support for all Azure services
All generally available Azure services have a corresponding supported Az PowerShell module
Multiple bug fixes and API version upgrades since AzureRM
New capabilities
Support in Cloud Shell and cross-platform
Can get and use access token to access Azure resources
Cmdlet available for advanced REST operations with Azure resources
We are now announcing that the AzureRM PowerShell module will retire by 29 February 2024.
If you are still using AzureRM modules, we advise you to migrate to Az at your earliest convenience.
When we talked with customers, the effort needed to migrate scripts based on AzureRM to Az was one of the main blockers.
We provide a toolkit comprised of three options to help you migrate to Az:
The following page has all the resources and technical information to help you migrate your scripts to Az: https://docs.microsoft.com/powershell/azure/migrate-from-azurerm-to-az
Open an issue on GitHub if you encounter problems with the migration toolkit.
Some products and services have dependencies on the AzureRM modules. We are working closely with them to provide you with a path forward.
We encourage you to start your migration as soon as possible and share with the community best practices that you may have, including tips and tricks.
The entire team is listening to your feedback and welcomes issues and contributions.
And as always, you can reach out to us via Twitter @azureposh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.