-
Notifications
You must be signed in to change notification settings - Fork 4k
Azure PowerShell Module Shows Warnings About AzureRM Retirement #23000
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for reporting! Could you try explicitly |
Hello @isra-fel, unfortunately running |
You can suppress this specific warning by setting the environment variable "SuppressAzureRmModulesRetiringWarning" to "true".
|
/unresolve |
@agerasimchikeg, did you get any update on this? I've got the same issue, same service management module. When removing AzureRM locally it works as expected but I'm unable to easily remove AzureRM modules from all our VMs. |
Hi All, @agerasimchikeg, i too got the same error, did you got some update on this issue? |
AzureRM already retired, closing this issue. |
Description
If you install both the “Azure” and the “AzureRM” modules, when using "Azure" module cmdlets you receive warnings about “AzureRM” module retirement:
'Because the Az modules have all the capabilities of AzureRM modules and more, we will retire the AzureRM modules on 29 February 2024. Learn more about the migration to Az: http://aka.ms/azpsmigrate.'
The “Azure” and “AzureRM” PowerShell modules comes with their own copies of an internal library called Microsoft.WindowsAzure.Commands.Common.dll. This library contains various infrastructure-logic and it’s this library which produce the retirement-warning. There appears to be an issue with the DLL search order when this library is loaded - when you are using the Azure module, the AzureRM-copy of this library is loaded.
Reproducing the issue:
Issue script & Debug output
Environment data
Module versions
Error output
The text was updated successfully, but these errors were encountered: