Forum Discussion
Are subsites getting deprecated in SPO?
Thank you Trevor Seward for the response! Yeah I was told this by a client today that it was deprecated and that put me on the back foot. Thank you for the confirmation that it is recommended not to use.
Is there any evidence that Microsoft are going to ‘actually’ deprecate subsites, or is there an element of reading between the lines here? I can see that hub sites have a roll to play as they offer valuable cross-site publishing which has been problematic in the past, but subsites offer site columns, metadata navigation, and permission inheritance. All the features of subsites have not be made available in other ways if you flatten the structure to use site collections alone.. As an example, if you have a site collection for each and every project in an organisation, there is massive administration overhead compared to each project being a subsite of a ‘programme’ site collection.
MichM any classic feature, e.g. metadata navigation, is "deprecated" (hence being called 'classic'). Hub sites are adding permission-push down soon.
And remember, deprecated means "may be removed in the future/no new features being developed" and not "removed".
Trevor Seward I was told by a Program Manager at Microsoft Ignite that there are no plans to get rid of subsites.
There are lots of use cases where subsites are mandatory.
Here is one:- Company wide site (communication site), used for announcements
- Department sites (Team sites accessible only for team members)
Give me a solution to display department wide announcement in company wide site.
My suggestion: Create subsites for each department.
If we go for flat structure, are we going to create two site collections for same department? Remember, there will be divisions in each department.
Subsites are MANDATORY !!!!!
