Open agerasimchikeg opened 9 months ago
Thanks for reporting! Could you try explicitly Import-Module Azure
first?
Hello @isra-fel, unfortunately running Import-Module Azure
has no change. The warning is still presented.
You can suppress this specific warning by setting the environment variable "SuppressAzureRmModulesRetiringWarning" to "true".
$env:SuppressAzureRmModulesRetiringWarning = 'true'
/unresolve @isra-fel I was aware that the warnings can be suppressed, the concern is that the commands will stop functioning when the AzureRM modules have been retired if the Azure modules are in fact using an incorrect dll. I have a Microsoft support case open as well and they were not able to confirm, so they directed me to open the issue here to have it investigated.
@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?
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