Forum Discussion
Is it now recommended or okay to create subsite under a Communication or a Teams site?
Hello Monir
it's ok (it's available), but it's not recommended. You can also deactivate the option: https://learn.microsoft.com/en-us/sharepoint/manage-site-creation#manage-detailed-site-and-subsite-creation-settings-in-the-classic-sharepoint-admin-center
All the new technologies (e.g. teamsite, groups, teamsite not groups connected) and site architecture features (e.g. global/hub navigation) based on site-concept, not subsite. So it is better to to the change to a new site based infrastructure.
Best regards, Dave
Thank you Dave.
Microsoft should set the recommended options as default. People tend to use what they find by default in most cases. In the past subsite was a norm so users are used to use them in regular basis.
However, there’re benefits of using subsites. For example: you have a project/program that has multiple initiatives - in this case each initiative can have a subsite dedicated to it under a project/program site collection.
In the new site recommended structure you have to create new site collection for each initiative and managing permissions and keeping track of them could be challenging for all these site collections.
Monir creating a hub site for the main project site and then associating your initiative sites to the hub works well. It means all the sites share a common theme and menu structure, and news can flow up to the main hub site from the different initiatives.
Rob
Los Gallardos
Microsoft Power Automate Community Super User.
Intranet, SharePoint and Power Platform Manager (and classic 1967 Morris Traveller driver)
- Thx, yes that will work but it just more work for permission wise - too many site collections to manage.
Monir due to my understanding it's an individual decision to use or not to use it depending on the content you want to build in the site.
If there is a slight chance the built side will to have been moved in the future regarding to organisational restructuring it's better not to use it.
E.g. if you create a site for a project which (content) is 100% sure bound to the main side and you want to avoid extended management overhead - permissions and so on - you can go for a subside.
- Thanks Sigi7.
Yes, the usage of subsite can be case by case and in some cases it’s probably makes better sense.
However, in the future, Microsoft may say subsite is no longer supported and all subsites needs to be on it’s own site collection and that could be a tedious task then. For example Microsoft is retiring Stream (classic) and forcing to use Stream (on SharePoint).
