Microsoft
MicrosoftMark-Kashman @Thanks for the post.
Cc: Rachel_Davis
Comments on item #4 - Groupifying and Teamifying a ShrePoint site without an O365 Group connected.
This might be problematic from permission perspective as described below ...
Yes, Teams provides better collaboration experience and has superb integration with other services ( OneDrive, Planner, Forms, Yammer, PowerBi, etc...) and is the ideal tool for focused conversation and managing content.
But the permmisision concept in Teams is so different than the SharePoint Sites w/o O365 group connected. In Teams all members can see and edit any content throuout the Teams. (Though Private channel is coming to Teams sometimes this year.) Members in Teams are encouraged to be active contributor.
Vs in a SharPoint Site, permission can be very granular - you define the permission based on your need - some may have Full Control, some may have Edit/Contribute and some may have just Visitor permission. And some content may not be visible to some. And this permission can be on List/Libraries/Folders levels with broken inheritance from parent. And there could be subsites with mixed of different permissions. If such a site gets Groupified / Teamified then this is a huge problematic from prrsmission perspective as not all Team members should be allowed to edit some content and some content may not be visible to all based on needs. Yes, someone can go at the back door to set the SharePoint site (connected wih the Team) permission to be granular but that’s not how Teams concept is. This causes managing permission in Teams and its connected SharePoint sites a challenge and should be avoided. And this is why - backed by users’ demands Microsoft now have Modern SharePoint team site without the connected O365 Group to keep the permission properly managed.
So if people wants to Groupify and Teamify a SharePoint site they need to understand how the permission is impacting them.
Would love to hear from you on your thoughts on this .. Thanks..
Cheers
MK
