Forum Discussion
Curious- Are you allowing all users to create O365 groups or limiting self-service creation?
Hey all... just wondering how everyone else is approaching this. Group sprawl is a concern, but at the same time, business user agility is a primary benefit of Groups... SO... Are you allowing se...
Hello John,
We have been using groups for about 1 year now. It has been a great success with geographically dispersed businesses groups.
When we enabled Groups, we quickly realized the pain of identifying the groups by their oddly given names, and we decided to lock creation to a small admin team who would create modern groups and train biz teams.
However, much later on, we found people creating plans, were able to create Groups that way, and Group restriction usability is not as clear (to the user) as it is with Groups. Add to this the somewhat recent introduction of Teams, which has a clontrol of "everyone OR no one", and you end up with frustrated admins, power, regular, and even ocasional users.
So to summarize... Groups, Teams, Yammer groups, Plans, will enhance your business teams collaboration, including their clients. If you restricted the creation of Groups you quickly realize users will find another app that will creat the group for you. There are PS to ensure some naming conventions, but in a hybrid environment this could generate a huge effort to adjust the old groups to the new standard. I believe user awareness of standardized names are the key to maintain a well balanced self-service system. Users are good with file systems (in their majority), so if we give them the opportunity with Groups, I'm confident they will learn.
We have been using groups for about 1 year now. It has been a great success with geographically dispersed businesses groups.
When we enabled Groups, we quickly realized the pain of identifying the groups by their oddly given names, and we decided to lock creation to a small admin team who would create modern groups and train biz teams.
However, much later on, we found people creating plans, were able to create Groups that way, and Group restriction usability is not as clear (to the user) as it is with Groups. Add to this the somewhat recent introduction of Teams, which has a clontrol of "everyone OR no one", and you end up with frustrated admins, power, regular, and even ocasional users.
So to summarize... Groups, Teams, Yammer groups, Plans, will enhance your business teams collaboration, including their clients. If you restricted the creation of Groups you quickly realize users will find another app that will creat the group for you. There are PS to ensure some naming conventions, but in a hybrid environment this could generate a huge effort to adjust the old groups to the new standard. I believe user awareness of standardized names are the key to maintain a well balanced self-service system. Users are good with file systems (in their majority), so if we give them the opportunity with Groups, I'm confident they will learn.
Thanks Phil-- regarding the "create a Planner and get a Group even if Group creation is disabled"... i wonder if this is an artifact of Planner initially not recognizing the "no self-service creation" setting which was in the OWA mailbox policy but is now in AAD where Planner can see it. Hopefully that will stop that loophole for unsactioned users to create Groups.
