Granular delegation and/or approval of group creation
The current state of GroupCreationEnabled in OWA mailbox policies makes it hellacious to delegate or control who can create groups. Customers should be able to easily delegate group creation to admins or "trained" users.
Currently this requires customers to "fork" their OWA mailbox policies, just to have a container on which to set GroupCreationEnabled to true. Then it become VERY difficult to manage as OWA mailbox policies are not "inherited"--any future change to corporate policies has to be deployed across multiple OWA mailbox policies.
Better yet, a group creation request form, with "approval" delegated.
Thanks for the feedback. We’re addressing this feedback by promoting the ability to manage group membership into Active Directory. In the near future, an admin can identify a security group that includes the users allowed to create Office 365 Groups form all endpoints. Then you can manage the membership in that security group as any other security group in your organization.
Note that the initial configuration to identify the group will be done in powershell.
This suggestion makes sense and would really help.
I think approval flow is required for the Groups feature on O365 to ensure that the groups that are created meet Organisational requirements
Rob Short commented
We already have a security group set up for approved Group creators in our tenant but it still doesn't give us the necessary safety in controlling the groups, last thing we want is users to go away creating unsuitably named Groups. When we have an Approve/Deny process for users trying to access SharePoint resources for us to have a situation whereby a user can create all the Groups they want it makes perfect sense for a single administrative approval screen for us to approve when a user creates a Group.
Even if the ability to create Groups could be assigned to an AD group it would be more manageable than currently.
Better management/admin tools are needed for Groups, approval workflow would be fine.
Currently disabled because impossible to use.