e-jr

### Solution: Enable-AzureRmAlias -Scope LocalMachine The error was gone for me when I enabled AzureRmAlias which is officially the compatibility mode for migrating from AzureRM to AzurePowershell https://learn.microsoft.com/en-us/powershell/azure/migrate-from-azurerm-to-az?view=azps-11.3.0#option-2-use-compatibility-mode-with-enable-azurermalias. I restarted...

It looks like the newest AzurePowershell version has a dependency to AzureRM. Since enabling AzureRmAlias fixes the error. https://learn.microsoft.com/en-us/powershell/azure/migrate-from-azurerm-to-az?view=azps-11.3.0#option-2-use-compatibility-mode-with-enable-azurermalias This should be fixed because for normal use of AzurePowershell version...

Any updates here? It's not possible to properly use channels and tenants in parallel

Any plans when this could be fixed? It indicates a wrong status, all deployments are affected