Import EXISTING O365 group, but restrict NEW group creation
Would like to see more administration options regarding O365 group creation and publishing to Teams.
Currently there is only 1 option - turn new O365 group creation OFF at all or allow to create groups everywhere.
Would be good to allow owners import already existing O365 groups example (or give admins option to allow users to do that).
In our example we have controlled way (self-service portal) where users can order new O365 groups, but problem is that if we can control new O365 creation there, this group is not added into Teams after creation. And there is possibility now to change this group in some way, so it appears in Teams, without user giving access to create new O365 groups everywhere again.
Users should now have the ability to convert an existing Office 365 group to a team even though team creation is disabled for them.
Users will be able to do this by simply clicking on “Add team” in the “Teams” left rail, then clicking on the “Create team” tile in the team gallery. This should bring them straight to the list of Office 365 groups they can convert as long as they are currently a group owner.
5 commentsComments are closed
I'm surprised there are so few comments here. Our organisation has many sub teams that use the existing Groups in O365, this was the first question we were asked.
Does MS have an answer for this?
And I advise my customers to only create groups through the Team app now - not Outlook or anywhere else. I know Teams can (reliably?) enable Team functionality onto an existing group but I'm making sure of it by having Team add the group. Team really is the command-centre AFAIC and it could be problematic if Microsoft doesn't keep Outlook and Teams parity when allowing both environments to seed new groups.
Team add needs a wizard to guide steps because groups add has such important decision implications when they start getting used. e.g. confusion, manual repairs, no archiving available, etc. The wizard (and whatever automated switches for command-line ops), could support the decision process by directing the goal and not just 'seeing what happens'.
Matt Shafer commented
Agreed! We've had several users create teams for distribution lists that already exist. This triggers a O365 group to be created with random number appended to the name so that it's unique. It would be nice if there was some check to indicate that this name already exists and to contact your administrator.
Another issue that's come up as a result of this is users creating teams representative of other departments. This is usually because the user doesn't understand that the team is not just in their UI, but becomes a Global object.
The Admin UI needs to be further built out to support more granular levels. There is at least 1 more request that access for the admin tooling to support who can create groups in teams.