Azure-docs: AzureRM

[yourekillingmesmalls]

How about providing a link to the azureRM documentation?
I don't need coercion to move to AZ, I need the azureRM documentation, please.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2ca47ab5-b553-c0e1-5736-cf4d9081d139
• Version Independent ID: bb85e0c9-3e55-749d-769e-7953479dccda
• Content: Create a Windows VM from a specialized VHD in Azure
• Content Source: articles/virtual-machines/windows/create-vm-specialized.md
• Service: virtual-machines-windows
• GitHub Login: @cynthn
• Microsoft Alias: cynthn

[Karishma-Tiwari-MSFT]

This article has been updated to use Az instead of AzureRm and the remaining docs are in the process of getting updated.
We do not have any other doc to create a Windows VM from a specialized VHD in Azure using AzureRm.
You can refer to this commit where the changes were made to replace AzureRm with Az commands.

[cynthn]

@yourekillingmesmalls you can still use the AzureRM commands locally and in Cloud Shell. The only real change was the prefix of the cmdlet. So, New-AzVM is New-AzureRmVM if you prefer using AzureRM. The Cloud Shell has the aliasing turned on, so you can type New-AzureRmVM, but it will be using -Az in the background.

[yourekillingmesmalls]

@Cynthn, thanks for the reply.
What's been overlooked here, is that many people have only begun their journey with Azure & PowerShell, & are just beginning to understand how to effectively perform tasks with them. For advanced users & those well versed in PS, sure, this is likely not too much of an interruption. For the rest of us, this has taken what would have been a productive day hostage, & forced us to stop our work until we re-tool.
We have many scripts utilizing AzureRM. According to the documentation, AzureRM needs to be un-installed prior to installing az, & then we would need to flip back & forth with compatibility mode, & in addition, if I understand correctly, the az module doesn't support azure stack?
Sorry for the negative feedback, but it would be great if more consideration were given to the needs of the customer & how these mid-stream changes can negatively affect us.

[cynthn]

@yourekillingmesmalls Feedback is always welcome :)

I'm not sure whether the Az module supports Azure Stack, maybe @MicahMcKittrick-MSFT knows or knows someone who can answer that part of the question.

If you are working locally and install the Az module locally, you can enable the AzureRM compatibility by running "Enable-AzureRmAlias".

Or, you could use Cloud Shell, because it already has this enabled. This should keep your older scripts running without having to update them. Then keep the older module locally for Azure Stack, if it isn't supported?

I get what you are saying. For new folks, using the PowerShell ISE makes it easier to find and use cmdlets, but you would need to choose whether to use the old version locally (for compatibility with anything that hasn't moved to the Az module) or move to Az so you have the latest and greatest

I do think we should do a better job of explaining that almost everything is exactly the same, except you use -Az instead of -AzureRm. The only "big" disruptions are that a couple components have new names, so importing them changes a bit. Like "AzureRM.Profile" is now "Az.Accounts".

[mimckitt]

As far as I know, Stack is not yet integrated with the new modules. Not sure when it would be though. @TravisCragg-MSFT works in Stack and might have an idea

[TravisCragg-MSFT]

@yourekillingmesmalls at this time Azure Stack still uses AzureRM. Azure Stack Powershell uses specific versions of AzureRM, and they are documented.

[Karishma-Tiwari-MSFT]

@yourekillingmesmalls Hope that helped answer your question.
We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.