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
MicrosoftHi 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.
- Sorry, but I'm not following you here: can you elaborate what you mean? You can add Office 365 Groups to your SPO Subsites security configuration with no problems
For migration scenarios with nested sites and where the Teams functionality is also required: it could be an option to grant access separately to the SP sites, and "Teamify" the O365 groups where Teams make sense and the group is to interact across the collaboration and communication apps. Links can be added to the above mentioned Sharepoint sub webs to the Teams' tabs.
That's a handy integration during a migration: using Teams as a portal to tab-aggregate the old "classic" SP site with the new "group" site, and drop the new Teamified Office 365 group security principal into the required SP group of the old "classic" SP site, but ...
Don't let Redmond off the hook! Those so-and-so's will do anything to get you off the line! If you don't want to migrate, and do want to Groupify-Teamify an existing "classic" site to save unnecessary hours of extra migration work with users, make MS work for it.
- how?
