This command no longer works: azure config mode ASM. We need an equivalent command in order to download config.xml for ASM deployments and make modifications to the file
Repro steps:
Install-Module Azure -AllowClobber
Import-Module Azure
Add-AzureAccount
azure config mode asm
Error: azure : The term 'azure' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@bradyson , thank you for your feedback. We'll investigate this and get back to you shortly.
@bradyson , I reproduced the issue and received the same error as you mentioned:

I have engaged our VPN backend team for help. I will update you as soon as I hear from them.
@yushwang , could you please provide some insights on this query? The command "azure config mode asm" doesn't seem to be working any longer. Is there a change in this command?
I'll take a look. This is for the classic system (service management) and it's just switching between the resource manager mode to service management. It's not specific to VPN Gateway.
OK, I've updated the articles in that set. The requirement to change to asm mode doesn't exist any longer. I think the only thing that may trip people up is the requirement to run the legacy version of PowerShell from their desktop. They can't do it from CloudShell and the steps are not available in the portal. I've attempted to make this very clear in the articles that this is the case and that the cmdlets are the older version, Service Management, and therefore use a different cmdlet to sign into Azure. #please-close