Ability to control which Office 365 services are available for use within groups
Creation of an Office 365 Group will automatically provision a number of O365 services (SP doc library, team site, OneNote, Planner, Calendar, etc). For organizations who are not ready (or able) to leverage certain services, how about providing the ability to control which services can be provisioned for use in groups?
For example, if our organization is only able to leverage an SP doc library and a OneNote, I would be able to configure groups to only make those specific services visible to our end users (items like a team site and Planner would be hidden/unavailable). This would be critical to organizations in more regulated industries, which may hinder their ability to simply turn on and leverage all O365 services as they become available.
The user should have the ability to define what is provisioned with the Office 365 group. For example, I want to create a private channel in Stream so a select few are able to view specific videos. My only option is to create an Office 365 group, which then creates everything else under the sun for these few. They do not need any of the other apps in this case so it is creating unnecessary bloat for the team.
Please allow admins/group owners the ability to provision/deprovision the applications associated with the group on demand. This will keep the group lean when necessary and expand to the desired amount of applications should the team chose to use multiple applications together.
Abhimanyu Singh commented
Yes this. O365 Groups the way is currently implemented is a total mess. Just let users create a group, and that's it. Do not create all kinds of associated artefacts like site and planner and stream and what not. Let the user add a service which is required only. Give the administrators ability to block a service from being used in a group.
In our case, we're a highly regulated business, so we would be more than happy for people to be able to use the benefits of a shared calendar and mailbox in Outlook, possibly with Tasks being shared in the Planner since the Tasks aggregation Web Parts were removed from My Sites, thanks MS! We already have structured team sites and libraries in SharePoint, so we would like to prevent the Shared Documents and Notebook from being created.
Could this be implemented with some checkboxes but with dependencies enforced so you obviously couldn't have a Notebook or Document Library without the SharePoint Site as these would need to be hosted there?
Brent Ellis commented
I have been asking for this forever as well. Here is a supporting case: We have gone to great lengths to build a sharepoint intranet with sites based on organization and projects, etc. If we create an department or project Group, it will automatically create a SharePoint site for that Group, which means now that group will have technically 2 SharePoint sites, one used, the other not. But since it is wide open, some users might start using the wrong SharePoint site. It is almost forcing our hand to do tons of "mini-migrations" of sharepoint team sites just to avoid tons of unused empty sites sitting out there.
I would like to see this on a Group by Group basis. Go to a settings menu, and choose which services to "hide". Maybe they can be provisioned, just dont show them in the menus or search/delve capabilities.