Jul 14 2017
- last edited on
Jan 14 2022
Sorry if I posted this twice, to me it seems that the first post did not succeed.
Installed PowerShellGet using the MSI.
Installed the Azure AD PowerShell v2 GA module using Install-Module AzureAD.
Connected and authenticated to our Azure AD tenant successfuly using Connect-AzureAD as can be seen below.
PS C:\Users\Administrator> connect-azuread
Account Environment TenantId TenantDomain AccountType
------- ----------- -------- ------------ -----------
firstname.lastname@example.org AzureCloud xxxxxxxx-0599-4cd4-8... xxxxxxxx.onmicrosof... User
But when running the Get-AzureADPolicy I get the error that this cmdlet is not available as can be seen below.
PS C:\Users\Administrator> Get-AzureADPolicy
Get-AzureADPolicy : The term 'Get-AzureADPolicy' 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
+ CategoryInfo : ObjectNotFound: (Get-AzureADPolicy:String) , CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
What am I doing wrong?
I urgently need to adjust the token lifetimes.
Jul 14 2017 09:49 AM
Jul 14 2017 11:34 AM
Which version of the Preview module you have, works fine here with 126.96.36.199. Make sure you are actually loading the correct module, as when you have matching cmdlets between both (Connect-AzureAD is the same for AzureADPreview and AzureADPreview). For example, open a fresh PowerShell window, do a Import-Module AzureADPreview, connect and then try running Get-AzureADPolicy.
Jul 15 2017 12:44 AM
Thank you very much! I was not aware that I had to import the module. Hope this wil change in the future so that the module loads automatically when start PowerShell like the MSOL module does.
Jul 15 2017 09:47 AM
It does load, but you have matching cmdlets between the two modules, and the non-preview version takes precedence. Unless you load it explicitly :)
Jul 25 2017 04:10 PM
First uninstall using
then install the preview module
May 23 2018 02:33 PM
Having same issue. If I import the AzureADPreview module only the same thing occurs, so its loading the AzureAD module in the background. You should be able to run both side by side for production.
Jun 13 2018 11:45 AM
I have the same issue. The AzureADPreview module was working fine with 188.8.131.52 (I think that was the version) but updated to 2.0.11 I get the same experience. If I run Install-Module AzureADPreview, then run Connect-AzureAD, it loads AzureAD module and the Preview cmdlets can't be found... I can't run Preview cmdlets anymore.
Jun 13 2018 12:52 PM
Jun 14 2018 12:26 PM
This worked. Installing the AzureADPreview module was failing as there were too many conflicting commands with the AzureAD Module. Once I uninstalled AzureAD and then Installed AzureADPreview (latest version 184.108.40.206) then everything worked as expected. Thank you
Jun 14 2018 12:27 PM
Feb 01 2019 02:21 AM
This worked for me. I had a new Win10 laptop and installing the preview (v220.127.116.11) would work but Get-AzureADPolicy didn't.
I just had to run "UnInstall-Module AzureAD" in a fresh elevated PowerShell console and then the preview cmdlets worked perfectly
Mar 22 2021 07:36 AM
when i am setting up for mapping policy on my Machin,
Somehow after all install module below is still not working - i am using with 18.104.22.168 AzureADPreview
Get-AzureADPolicy is not recognized as the nameof a cmdlet.........
Jun 08 2021 01:05 PM
In order to have both AzureAD and AzureADPreview installed, but decide to use one or the other, you can use this: AzureADPreview\Connect-AzureAD to use preview instead of normal.
Nov 18 2021 02:00 AM
At the moment I have the same issue.
I tried multiple version of AzureADPreview, removing AzureAD module and many other combinations but the command is still not found.
Related issue: https://github.com/Azure/CloudShell/issues/111
Feb 15 2023 07:56 AM - edited Feb 15 2023 08:12 AM
@Benoitt Use below command and it works
Install-Module -Name AzureADPreview -AllowClobber
and run Import-Module Azureadpreview before running policy commands