Closed sptramer closed 5 years ago
@sptramer Hey Stephen, since this is an entirely new module, there will be breaking changes when migrating from AzureRM
to Az
; however, we added an Enable-AzureRmAlias
cmdlet that will create an alias for each of the new *-Az*
cmdlets to the corresponding *-AzureRm*
cmdlet, which will mitigate this issue.
@cormacpayne - This is not a sufficient response. The current workflow, documented everywhere on the site, is to use Connect-AzureRmAccount
. Making this change outside of the current flow of updating the documentation to use the Az
module isn't really possible or appropriate. Also without the lack of aliasing on by default there will be serious issues with the documentation set migration. You need to discuss this with myself and @JasonRShaver.
Updated title to reflect the work we're tracking with docs
Title seems more appropriate since I double-checked, it looks like Connect-AzureRmAccount is included in the aliases. I have no idea why it wasn't loading/running correctly in the Docker container. Possibly related to #7370.
This issue can either be kept open or migrated back to azure-docs-powershell.
Closing this in favor of other docs issues.
Description
The
Az
module does not include theConnect-AzureRmAccount
command. See https://github.com/Azure/azure-docs-powershell/issues/732 for the initial report.Script/Steps for Reproduction
Attempt to run the
Connect-AzureRmAccount
command.Module Version
Environment Data
This test was run on the officially maintained Docker container image
azuresdk/azure-powershell-core:latest
.IMPORTANT NOTE: The
Connect-AzureRmAccount
command is referenced 474 times in the online Azure documentation set, not including#include
files which are used in multiple locations.