Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to work with Windows Azure PowerShell module on Windows 8.1. I have downloaded and installed the Azure module and in start I can run and use the "Windows Azure PowerShell" which is a PS that just loads Azure. When I open just a plain PS window and do Import-Module Azure it fails with:

import-module : The specified module 'Azure' was not loaded because no valid module file was found in any module directory.

I suspect that it have something to do with powershell versions or 64\32 bit versions.

Anyone has any experience with this?

share|improve this question
up vote 18 down vote accepted

The Windows Azure SDK binaries and pertaining PowerShell cmdlets are all 32-bit, which is why the "Windows Azure Powershell" shortcut always launches a 32-bit shell.

You can import the Azure module to an existing PowerShell session by referencing the filesystem path to the module manifest:

Import-Module "C:\Program Files (x86)\Microsoft SDKs\Windows Azure\PowerShell\Azure\Azure.psd1"

To access the module by name alone, you'll need to include its location in the PSModulePath environment variable (here in excruciating detail, for developers):

$oldPSModulePath = [Environment]::GetEnvironmentVariable("PSModulePath")

$azureModulePath = "C:\Program Files (x86)\Microsoft SDKs\Windows Azure\PowerShell\"

$newPSModulePath = $oldPSModulePath,$azureModulePath -join ";" 

And a shorthand expression for your powershell

$env:PSModulePath += ";C:\Program Files (x86)\Microsoft SDKs\Windows Azure\PowerShell\"
Import-Module Azure # <-- Now you can do this!

You could include the above in your PowerShell profile

share|improve this answer
Thanks, that works also for 64 bit PS. Is there a way to make the shortcut work in 64 bit PS as well? – itaysk Jan 19 '14 at 10:12
For me command I had to run was: Import-Module "C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure\Azure.psd1" – Kai G Mar 9 at 8:03

If you just installed the Azure PowerShell SDK, then restart the computer first. A restart is required after installation, otherwise this exception will be thrown.

share|improve this answer
That was exactly it!!! – Luis Gouveia Mar 2 at 11:48

For the azure resource manager mode module (2015/09/11), use the following:

import-module "C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ResourceManager\AzureResourceManager\AzureResourceManager.psd1"

share|improve this answer

Also try running the installer as Administrator, by right clicking on the installer executable and choosing Run as Administrator. Once complete, reboot. You can also run the import as stated above but you should not need to do that with the newer installers.

share|improve this answer

Depending on the SDK version that you have installed, you may have a "Windows Azure" or just "Azure" folder on the path.

For my setup, I use this:

"C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure

share|improve this answer

In Windows 10, the path has changed. See correct version below:

$oldPSModulePath = [Environment]::GetEnvironmentVariable("PSModulePath")
$azureModulePath = "C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement"
$newPSModulePath = $oldPSModulePath,$azureModulePath -join ";" 
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.