Forum Discussion
Difference between a SharePoint site created via Groups/planner/Teams etc and a standalone SP site
I compared Site Collection settings on an SPO Team site vs a Group Team site. On the Site Settings page there are 83 links to settings on an SPO Team site and on a Group Team site there are 43. On a Group Team site you can append links to settings pages (using an SPO Team as a reference) and those pages still exist (didn't try all). I did try to change the site title to something friendlier than the group name, but the title changed back to the group name pretty quickly. The menu's have changed for example, site settings is not listed off the 'cog' dropdown. It will be an interesting process to adopt and adjust to these changes over time. I had a conversation with a Knowledge Management Specialist today and he was concerned that the SharePoint sites associated with Groups and Teams would undermine the use of the SPO Site used for managing authoritative reference content. The main site has a well developed role based permission model that is used to ensure that different categories of content are edited and maintained by the appropriate team.
- Andrew SilcockAug 10, 2017Iron ContributorThanks for the information.
"I had a conversation with a Knowledge Management Specialist today and he was concerned that the SharePoint sites associated with Groups and Teams would undermine the use of the SPO Site used for managing authoritative reference content."
It's a battle we've stopped fighting. We looked into containment, but the beast that is O365 is constantly evolving and we'd be fighting a losing battle.
ShareGate bring it up in this blog, might be worth a read: https://en.share-gate.com/blog/microsoft-modern-workplace
If you need containment then on premise is the way to go.