Forum Discussion
MicrosoftAbility to connect existing SharePoint team sites to Office 365 Groups is coming later this year
Hi all - yes our plan is to provide the ability to connect only root site collections to new Office 365 Groups. We've considered enabling subsite-to-group connections, but there are enough gotchas both architecturally as well as from a design standpoint in delivering an experience that is comprehensible to most humans. One example is that when we start rolling out classification-based policy (e.g. Confidential classification equates to group guests being disabled, SharePoint external sharing turned off, etc. - this is just an example for discussion), those policies apply at the site collection container level. If we enabled subsite connection to groups, we would have to deal with site parent-child policy conflicts, inheritance-based permissions, etc. Not saying it's impossible but cleary stands in the way of shipping an experience sooner.
Having looked at all site collections in the service, the vast majority are flat (i.e. no subwebs), for which this experience should work seamlessly. That said, we acknowledge that there are some very active site collections with subsite hierarchies. For these subwebs, there are a couple of paths to get to 'modern'. One is a migration effort from subsite to root site collection, and then connecting the collection to a new group with the feature described in this thread. The other, is a 'modernize this site' type of experience that brings the classic subsite to the modern experiences without a group connection. This is also a body of work we are investing in and will share additional details in the future.
Hope this helps to clarify. We'll definitely be talking more about this in the coming months as we make progress on the feature.
Thanks
Wait...site collections. That would be no good. Our site collections are per regional office and our subsites are departments. We NEED to be able to connect an 0365 group to a sub-site. Please clarify Microsoft.
You might try mapping Channels from Teams to the sub-webs of your Site (site collection).
Team, Group, and Site are all a one-to-one relationship. Probably best we keep it that way or we might all go mad. So for example, if "Products" is the subject matter, then there's one Team / Group / Site called Products.
However, there is a one-to-many relationship between a Team and its sub-Channels.
And there's a one-to-many between a Site (site collection) and its sub-Webs.
So you can create a Channel (sub-Team, so to speak) for each sub-Web (sub-Site). Then add a tab in the Channel that connects to the corresponding sub-web, and put a link back to the corresponding Channel from the left nav (Quick Launch) of the sub-web. The Channels then map the augmented functionality for conversations etc. to the sub-webs on one-to-one basis.
So for each actual product sub-Web (Grommet, Rivet, Bracket, etc.) you might have below the Products Site, there's a corresponding Channel (Grommet, Rivet, Bracket, etc.) below the Products Team.
I'm just waiting for the programmatical interface to Teams to become available before setting up some automation provisioning whereby the associated Channels are created automatically from the sub-Webs. This will work for Customers, Suppliers, Employees, as well as Products, where the one-to-many-ness abounds.
- This wouldn't work for us. We have a handful of site collections all of which have hundreds of subsites under them. Because there's no way to set permissions per channel, everyone would be able to see everyone's conversations etc.
Tejas MehtaHi all - yes our plan is to provide the ability to connect only root site collections to new Office 365 Groups. We've considered enabling subsite-to-group connections, but there are enough gotchas both architecturally as well as from a design standpoint in delivering an experience that is comprehensible to most humans. One example is that when we start rolling out classification-based policy (e.g. Confidential classification equates to group guests being disabled, SharePoint external sharing turned off, etc. - this is just an example for discussion), those policies apply at the site collection container level. If we enabled subsite connection to groups, we would have to deal with site parent-child policy conflicts, inheritance-based permissions, etc. Not saying it's impossible but cleary stands in the way of shipping an experience sooner.
Having looked at all site collections in the service, the vast majority are flat (i.e. no subwebs), for which this experience should work seamlessly. That said, we acknowledge that there are some very active site collections with subsite hierarchies. For these subwebs, there are a couple of paths to get to 'modern'. One is a migration effort from subsite to root site collection, and then connecting the collection to a new group with the feature described in this thread. The other, is a 'modernize this site' type of experience that brings the classic subsite to the modern experiences without a group connection. This is also a body of work we are investing in and will share additional details in the future.
Hope this helps to clarify. We'll definitely be talking more about this in the coming months as we make progress on the feature.
Thanks
Hi,
If there is a need to add existing O365 groups to Sharepoint subsites, there is always the possiblity to grant access to the AD Seurity group equivalent of the O365 group via the site's SharePoint group.
- I guess so!
