Today while preparing for an Azure Cloud Lab that I will be delivering next week, I installed the latest version of Azure PowerShell (which in this case is version 1.2.0).

Normally, when you have Azure PowerShell installed, you can search for it and it will appear.

Search Result for Azure PowerShell

Also, in the All Apps list (in Windows 10), there should be an entry under Microsoft Azure.

Azure PowerShell Start Menu Entry

But when you install the latest version of Azure PowerShell (1.2.0), these 2 entries are removed!

Azure PowerShell – February 2016 Version (aka 1.2.0)

 So how can you work with Azure PowerShell, without these entries?

Easy. The “work-around” is to use the normal Windows PowerShell, and type: Import-Module Azure.

Import Azure Module in PowerShell

It’s not really that big of a deal, but I did log a bug just in case:

I just wanted to share this observation, in case anyone else encounters it.

Additionally, if you are trying to find a previous version to use, look here: under the Command-Line Tools section. Listed under Windows PowerShell, there will be a link for Install Legacy.

Install Legacy Azure PowerShell
Install Legacy Azure PowerShell

This will download the installer for Microsoft Azure PowerShell

Install Azure PowerShell
Install Azure PowerShell

NOTE: Since the original posting of this article, it has been suggested that the Azure PowerShell modules are automatically loaded in the “regular” PowerShell, and you shouldn’t have to use Import-Module Azure. It has also been suggested that the removal of the Start Menu entries may be “by design”. Once we have confirmed this statement, this article will be updated accordingly.

UPDATE: This must have been a bug, since this morning I checked my installation of Azure PowerShell, and there was an update/new version available (via the Web Platform Installer). Now, with version 1.2.1, the Start Menu item still isn’t present, but when I search for Azure PowerShell, it does appear.

UPDATE 2: Mark Cowlishaw from Microsoft replied to my reported “bug” on GitHub, and provided the following clarification:

This is, indeed by design. Since both azure and AzureRM modules are in the PSModulePath, so that they are automatically loaded in any PowerShell or PowerShell ISE session, and since we are ensuring the global ExecutionPolicy, there is no longer any real reason for the AzurePowerShell shortcut, so it was removed.

Mark Cowlishaw's Reply
Mark Cowlishaw’s Reply

So there you have it.