… but of course you don’t get told in anything in-your-face. To wit, this command…
… used to return stuff.. and now returns the blank line you see. Turns out this is because Get-AzureVM now refers to the “Classic” variants in the Azure Portal. If you created through the (implicitly recommended) Resource Manager in the Azure Portal, then you now have to use this command:
, where the [Rm] part stands for [Resource Manager] . This is a reasonable link.
So that took a while to get there. Next: I have 2 subscriptions. Although I could use this to enumerate my subscriptions, with  being my default subscription:
, it a LONG time to work out that a) you can only work in one subscription context at a time, and that resources not in the default subscription will not be listed until you do this:
With that context set, it will now happily list e.g. the VMs I created on my non-default subscription:
And a general MSDN link around those Azure RM cmdlets:
And just throwing in some of the keywords/cmdlets I used on the way:
Import-Module -Name PowerShellGet
Install-Module Azure -AllowClobber
By the way, June 22 2016 (that is, just 2 weeks ago) seems a date when a lot changed in PowerShell for Azure. And even the updated docs still talk about “this is early documentation, subject to change, etc…”
Hm, and now I’ve just spotted the “true” CLI ( as opposed to PowerShell):
Another time. Night.