Forum Discussion
AAD PowerShell Commands not working (get-msol ...)
- These cmdlets are not supported in the Azure Active Directory Module for Windows PowerShell GA (v.1.1.166.0) which you have installed. Instead you can install V1.1.130.0 public preview and use it. See release notes from below link for more details.
http://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=59185
http://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=59185
Hi SanthoshB1 - I've been trying to evaluate the ability to limit the creation of Groups as discussed in this thread, however, it now appears that all links to the version of the Azure AD module (v1.1.130.0) have been removed from the associated and linked to pages. Therefore I am at a loss to know how to proceed as the no other versions of the module appear to have the cmdlets and the necessary module is unavailable. Has the overall approach changed? I would have thought that the introduction of Microsoft Teams will have re-ignited the question of governance with regards to the proliferation of Office 365 Groups.
Can anyone provide any guidance here, please?
Hi SimonChalfont Ivan54 Dean_Gross SanthoshB1,
The Settings cmdlets that were previously published in a preview release of the MSOL module are no longer available there. As we are deprecating the MSOL module, no more preview releases are made available and no new functionality will be added to that module.
The Settings cmdlets ycan now be found in the newer Azure AD PowerShell V2 Preview module, which can be installed from here: https://www.powershellgallery.com/packages/AzureADPreview
More information about how to use the new cmdlets for Settings can be found here: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-accessmanagement-groups-settings-cmdlets
More information about the Azure AD PowerShell V2 module can be found here: https://docs.microsoft.com/en-us/powershell/azuread/
Please reach out to me if you have any questions or concerns.
-Rob (Rodejo@Microsoft.com)
Rob de Jong Is there anything available that describes how the movement of the old cmdlets to the new modules, i.e., a cross-reference map of some kind?
Also, it can be quite challenging to understand what cmdlets are available in Preview vs GA. There is something about the docs for the modules that makes this unclear and complicated for many of us. I get confused because the version number scheme does not give any clues about the modules status, i.e., 2.0.0.52 and 2.0.0.76 were Preview, but 2.0.0.55 and 2.0.0.71 were GA. The way that the Release notes present the changes, makes it very difficult to figure out what has happened when we are trying to work out how to update an older example.
It would be helpful if there was something that explained how we should work when we have both modules installed (or even if this is a recommended approach.
The list of cmdlets on https://www.powershellgallery.com/packages/AzureAD/2.0.0.71 is not very readable which keeps it from being very helpful
Thanks, I'll give it a try. But could someone explain the versioning numbers to me please :P
Why is GA version number higher than the Public Preview? I just assumed that the GA version has caught up to public preview and the page hasn't been updated.
v1.1.166.0 GA
v1.1.130.0 Preview
EDIT1: just tried to install the preview version over the GA version and as assumed the setup says a newer version is already installed :)
Guess I'll have to use some other machine to install the public preview version.
EDIT2: commands are working in the public preview version. Though I'm able to follow the instructions for creating classification labels, but thats a topic for a different thread :)
We have one build system that build both a preview version and a GA version in the same run. Since this module is going to be deprecated in favor of the newer AzureAD V2 PowerShell module we do not add any new functionality to it and usually only release it when previously released cmdlets in a preview version are moved into GA status.
- you were faster than me :)
