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
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.
- thanks Lawrence, I'm maybe being a little thick here, but I see the words you're saying about migration and teams and classic and groups etc. - but if you don't mind could you clarify how I would go about going from our current SharePoint Online "classic" sites to somehow them being linked to or as groups. Do I need to contact Microsoft or something I am not clear on how you do it....
Hi Baronne,
Let's say your old "classic" site is called Old-Contoso, and it has the usual 3x SP Groups: Old-Contoso Owners, Old-Contoso Members, Old-Contoso Visitors. You manage members of the SPG's in the usual manner, by selecting security principals from the people picker.
And you've got a new Office Group called New-Contoso. So this comes with its own membership management, surfaced in the Office 365 Admin Centre -> Groups, and also in the Outlook Groups presentation of the OG functionality.
If you go to the Old-Contoso SP site -> Site Settings -> People and Groups, and select one of the SPG's, say Old-Contoso Members, then add a new user, the people picker will let you select the OG's like they were users. If you add an OG to an SPG, the members of the OG membership gets the access that the SPG has to sites, libraries, folders, and docs in the Old-Contoso site.
Likewise, if you go to a site, library, folder, or document in the Old-Contoso site, and disinherit its permissions from its parent, and add permissions, the people picker will allow you to add an OG and grant it permissions.
So you can use OG's, for example the New-Contoso OG, to puppet master the permission across your old "classic" SP sites, for example Old-Contoso, by adding the OG's as members of the old "classic" SP sites' SPG's, or by directly granting the OG's access permissions on the old "classic" SP sites' containers (sites, libraries, folders) and documents.
So in a migration or hybrid you can manually configure the OG's to duplicate the old permissions by creating OG's with memberships, adding them to the old sites SPG's, containers, and documents permissions. Then delete the old memberships of old SPG's.
The old sites and SPG's are then security "zombies" from a group membership point of view. All granting of collective permissions is made by member management of the new OG's, and by granting permissions of those OG's onto the resources of the old sites.
