Forum Discussion
Brent Ellis
Sep 01, 2016Silver Contributor
What to do when you dont necessarily want a Group?
I'm still concerned about some of the approaches being discussed (every site gets a group and every group gets a site). It seems there will be lots of unwanted sharepoint sites and o365 groups sitti...
Mark Driver
Sep 07, 2016Brass Contributor
Yep pretty much agree here as well. We have questions oustanding re Groups:-
- Will the groups that are automatically created for existing team sites be public or private?
- Will site owners automatically be granted Owner permissions on a Group?
- Will these Groups be hidden from the GAL automatically?
- Will the members of the team site be notified by Microsoft of the groups creation?
- What happens in the event that a group already exists with the same name as a team site?
- Will we get any notification from MS when they decide to implement this in our tenant?
- We currently have a different naming convention for Distribution Groups than we do for Office Groups. Will MS provide us with any scripts to help us find and rename any newly created groups from team sites, which will obviously not match our current naming convention?
- As each group will also have a Plan, will we have to turn these licenses on for each user, now that we have disabled them?
This is a nightmare for Office 365 admins in a big envrionment.
Mark
Anonymous
Sep 07, 2016I agree Mark Driver with all of your points.
BTW, no need to worry about the Planner license -- that license option literally only controls whether your users see the tile in the apps launcher. It does not prevent them from accessing Planner, as long as they know the URL. (We discovered this via a support ticket last week! The Microsoft Support Engineer pointed to the official documentation on this -- https://blogs.msdn.microsoft.com/brismith/2016/06/24/microsoft-plannerdisabling-planner-license-without-enabling-other-licenses/.)