Forum Discussion
Difference between a SharePoint site created via Groups/planner/Teams etc and a standalone SP site
Hi all,
We are often asked what the difference is between the sites that are automatically created when you create something through groups, i.e. Planner, Microsoft Teams team etc. (let's call these groups sites) and a "regular SharePoint site" that IT would create. I guess you might call these a Team site template site, created under a subsite of a site collection.
I have come up with a list and wonder if anyone has any more to add or any different opinions to the following points?
- Max 1TB storage space in groups sites.
- SharePoint admins don't automatically have access to group sites - harder to support.
- Fewer options available in site settings on group sites - Can't use list templates for example.
- All site owners of group sites get permission requests. - As opposed to only one person being emailed for access requests on Team site template sites.
Thanks,
Andy.
4 Replies
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.
- Thanks 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.
- A SPO Site created from Groups, Teams and Planner is just a modern SPO Team site where you have everything modern by default including security configuration for the site. In regards of your additional questions:
(1) Max. storage per site collection is the same no matter if we are talking about modern SPO Site Collections or classic ones...indeed Microsoft is expanding the limit to 25 TB per site collection
(2) This is correct, but you can grant access to SPO Group sites by adding the SPO Admins through PowerShell just in case you cannot add them as members of the Groups
(3) Also correct, Microsoft is reducing administration options you have in moder SPO Team Sites
(4) Correct too...this is by design due to the fact that everything is governed by the underlying Group- Thanks Juan,
Pleased I was wrong about the site collection size.
