Get-AzureADMSDeletedGroup is not recognized

While playing around with Office 365 Groups expiration and the AzureADPreview module in PowerShell, I ran into the error below:

The term ‘Get-AzureADMSDeletedGroup’ is not recognized as the name of a cmdlet, function, script file, or operable program.

After a bit of trial and error, and some searching I found an important note in the Azure Active Directory PowerShell Module documentation.  The documentation notes that the preview module cannot be installed on the same machine as the production module.  I didn’t seem to have an issue actually doing the installation using the PowerShellGet Module, and tab completion for the cmdlets even worked, but the cmdlets would not work.

Indeed, after uninstalling the production module (Uninstall-Module AzureAD), I was able to work with the preview cmdlets.

Using a Separate Domain for Office 365 Groups

Office 365 Groups, sometimes referred to as Unified Groups, have been around for a while now.  Groups are excellent for collaboration, and allowing the end user to be in control of their own collaboration experience.  Groups are bad news for IT workers who need control or are resistant to change.  The latter group of IT workers will need to get on board though as it is evident that much of the Microsoft Office 365 ecosystem will be intertwined with Groups going forward.

For the past year, I have restricted group creation in production.  There are a multitude of reasons for not using Groups upon their initial release but, ultimately, it was lack of enterprise controls.  Most of those limitations have been remediated and the time for Groups is now.

In an effort to keep some form of structure around Groups, using a multi-domain approach is useful.

Continue reading

Microsoft modifies stance on automatic group creation for managers

Microsoft recently announced that beginning on April 13, 2017 an Office 365 group would automatically be created for managers with at least 20 direct reports.  Office 365 administrators quickly let Microsoft know that they were unhappy with these forced group creations.

This evening, though, Microsoft released an update to the Message Center that they have changed their original stance.  According to the new message below, the feature will not be released as announced.  Instead, the feature is going to be rolled to a smaller group for additional testing.  Stay tuned to see what the eventual rollout looks like, if it happens at all.