SOLVED

Msol and OWA commands to disable groups

Steel Contributor
Do you have to run both the Owa and Msol commands to disable O365 Groups creation, or is the Msol command enough?

 

Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -GroupCreationEnabled $false

Set-MsolCompanySettings - UsersPermissionToCreateGroupsEnabled $false

5 Replies
What you have to do is work with the Azure AD policy...working with OWA policy only will allow you to disable groups creation in OWA. https://thoughtsofanidlemind.com/2016/06/07/controlling-the-creation-of-office-365-groups-using-an-a...
Additionally you can also refer these blogs.

Disable Office 365 Group Creation in Azure AD
http://www.jijitechnologies.com/blogs/disable-office365-group-creation-in-azureAD

Control Office365 Group creation permission using OwaMailboxPolicy
http://www.jijitechnologies.com/blogs/control-office365group-creation-permission

Thansk, so my question still is to fully disable O365 groups, do you apply use both the Azure AD policy and OWAMailboxPolicy?  We've already run the Azure AD policy, and I can see that's working correctly as I get an error if trying to create a Plan in Planner.  We haven't yet moved to ExO, but will be starting to move mailboxes shortly so am trying to figure out if I need to let Exchange team know to run the OWAMailBoxPolicy to disable so people can't create groups from OWA.  The last sentance of the article Juan Carlos linked to, "However, the old OWA mailbox policy method continues to work for OWA and Outlook until superseded by the new method" seems to suggest that we may need to run both? 

best response confirmed by Erin Scupham (Steel Contributor)
Solution
Running script in Azure alone will suffice. This will block group creation from all endpoints.
OWAMailBoxPolicy will block the Groups creation from OWA alone. So there is no need to run both.
Yeap, the OWA policy was designed just for this: provide a centralized point to disable Groups creation and also who can create Groups in a centralized way so it does not matter the place where you try to create a Group, Planner and a Team...the underlying policy is going to control everything
1 best response

Accepted Solutions
best response confirmed by Erin Scupham (Steel Contributor)
Solution
Running script in Azure alone will suffice. This will block group creation from all endpoints.
OWAMailBoxPolicy will block the Groups creation from OWA alone. So there is no need to run both.

View solution in original post