Communication Site not a template under "New Subsite" or SharePoint Admin

%3CLINGO-SUB%20id%3D%22lingo-sub-89718%22%20slang%3D%22en-US%22%3ECommunication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89718%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20new%20Communication%20site%20has%20reached%20us.%20It%20looks%20very%20promising%2C%20but%20I%20noticed%20that%20the%20only%20way%20to%20create%20one%20is%20from%20the%20SharePoint%20home%20page%20%22Create%20a%20Site%22%20menu.%20Once%20I%20have%20a%20Communication%20site%2C%20I'd%20expect%20to%20be%20able%20to%20create%20subsites%20under%20the%20main%20communication%20site%20that%20use%20the%20same%20template%20and%20are%20communication%20sites%2C%20but%20I%20can't%20right%20now%20(see%20screenshot).%20I'd%20also%20expect%20to%20be%20able%20to%20create%20them%20from%20the%20SharePoint%20admin%20page.%20It%20looks%20like%20it%20isn't%20a%20template%26nbsp%3Boption%20under%20either%20place.%20Is%20this%20intentional%3F%20Or%20should%20I%20expect%20it%20to%20appear%20these%20places%20too%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-89718%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESites%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-156426%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-156426%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20also%20need%20the%20ability%20to%20create%20Communication%20sub-sites.%20It's%20what's%20stopping%20us%20from%20fully%20adopting%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89797%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89797%22%20slang%3D%22en-US%22%3E%3A-)...we%20might%20have%20clue%20about%20when%20the%20new%20SPO%20stuff%20could%20com%3A%20Ignite...but%20let's%20see%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89772%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89772%22%20slang%3D%22en-US%22%3EAll%20that%20is%20coming%20with%20the%20new%20SharePoint%20Admin%20center%20only....%20though%20no%20idea%20when%20that%20is%20being%20rolled-out%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89754%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89754%22%20slang%3D%22en-US%22%3EI%20guess%20this%20is%20just%20%22a%20design%22%20question%20for%20now...with%20Communication%20Sites%20is%20happening%20the%20same%20thing%20we%20have%20with%20modern%20team%20sites%3A%20you%20can%20create%20then%20only%20as%20Site%20Collections%20from%20the%20SharePoint%20landing%20page...you%20can%20create%20subsites%20under%20a%20communication%20sites%20and%20user%20modern%20pages%20and%20WebParts%20to%20have%20a%20%22similar%22%20look%20%26amp%3B%20feel%20to%20what%20you%20have%20in%20a%20communication%20site%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89724%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89724%22%20slang%3D%22en-US%22%3E%3CP%3EBTW%20-%20Thanks%20for%20asking%20I%20am%20also%20interested%20in%20the%20answer.%20%26nbsp%3B-%20Greg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89723%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89723%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20create%20one%20using%20PnPPowershell%20and%20specifying%20the%20template%20'SITEPAGEPUBLISHING%230'%20%26nbsp%3Bas%20in%26nbsp%3BNew-PnPTenantSite%20-Url%20%24siteUrl%20-Owner%20%24siteOwner%20-StorageQuota%20%24siteStorage%20-Lcid%20%24siteLocale%20-ResourceQuota%20%24siteResource%20-Template%20%24siteTemplate%20-TimeZone%20%24siteTime%20-Title%20%24siteTitle%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhere%20%24siteTemplate%20%3D%20SITEPAGEPUBLISHING%230%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-440748%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-440748%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F118146%22%20target%3D%22_blank%22%3E%40Mohammad%20Housaini%3C%2FA%3E%26nbsp%3BYep%20this%20is%20total%20BS.%20The%20Modern%20ui%20is%20nowhere%20near%20ready%20for%20production%20use.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-445888%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-445888%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F38447%22%20target%3D%22_blank%22%3E%40matt%20howell%3C%2FA%3E%26nbsp%3BThe%20IA%20recommendations%20proposed%20by%20Microsoft%2C%20are%20to%20avoid%20sub%20sites%20all%20together%20and%20to%20use%20a%20Flat%20Architecture%20for%20all%20of%20your%20sites.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-454237%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-454237%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F118146%22%20target%3D%22_blank%22%3E%40Mohammad%20Housaini%3C%2FA%3E%26nbsp%3Bwhat%20is%20your%20example%20scenario%20for%20needing%20communication%20sub-sites%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-454240%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-454240%22%20slang%3D%22en-US%22%3EBit%20harsh%2C%20all%20depends%20on%20particular%20use%20case%2C%20for%20the%20majority%20I%20feel%20modern%20is%20now%20ready%20and%20classic%20migrations%20should%20be%20of%20a%20priority%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-486292%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-486292%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51472%22%20target%3D%22_blank%22%3E%40Warwick%20Ward%3C%2FA%3E%26nbsp%3BHi%20Warwick.%26nbsp%3B%20Here%20is%20my%20situation%20where%20I%20would%20like%20to%20use%20a%20communication%20sub-site.%26nbsp%3B%20We%20are%20developing%20an%20internal%20company%20portal.%26nbsp%3B%20The%20HR%20department%20has%20a%20site%2C%20for%20content%20relevant%20to%20all%20employees.%26nbsp%3B%20They%20also%20need%20to%20develop%20a%20set%20of%20modern%20site%20pages%20that%20are%20relevant%20to%20and%20only%20viewable%20by%20supervisors.%26nbsp%3B%20This%20would%20best%20be%20served%20by%20a%20subsite%2C%20but%20they%20are%20unhappy%20with%20the%20difference%20in%20the%20look%20and%20feel%20between%20a%20communications%20site%20and%20a%20team%20site.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-504190%22%20slang%3D%22en-US%22%3ERe%3A%20Communication%20Site%20not%20a%20template%20under%20%22New%20Subsite%22%20or%20SharePoint%20Admin%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-504190%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F328290%22%20target%3D%22_blank%22%3E%40Mike-FSA%3C%2FA%3E%26nbsp%3BSub%20sites%20are%20no%20longer%20%22recommended%22%20by%20Microsoft.%26nbsp%3B%20A%20couple%20options%20would%20be%20to%20just%20permission%20the%20pages%20that%20are%20relevant%20to%20those%20supervisors%20on%20the%20same%20site.%20Or%2C%20turn%20the%20HR%20site%20into%20a%20Hub%20site%20and%20create%20an%20associated%20communication%20site%20for%20your%20supervisors%20to%20read%20content%20from%20HR%20or%20content%20living%20in%20the%20associated%20site.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

The new Communication site has reached us. It looks very promising, but I noticed that the only way to create one is from the SharePoint home page "Create a Site" menu. Once I have a Communication site, I'd expect to be able to create subsites under the main communication site that use the same template and are communication sites, but I can't right now (see screenshot). I'd also expect to be able to create them from the SharePoint admin page. It looks like it isn't a template option under either place. Is this intentional? Or should I expect it to appear these places too?

12 Replies
Highlighted

Can you create one using PnPPowershell and specifying the template 'SITEPAGEPUBLISHING#0'  as in New-PnPTenantSite -Url $siteUrl -Owner $siteOwner -StorageQuota $siteStorage -Lcid $siteLocale -ResourceQuota $siteResource -Template $siteTemplate -TimeZone $siteTime -Title $siteTitle

 

Where $siteTemplate = SITEPAGEPUBLISHING#0

Highlighted

BTW - Thanks for asking I am also interested in the answer.  - Greg

Highlighted
I guess this is just "a design" question for now...with Communication Sites is happening the same thing we have with modern team sites: you can create then only as Site Collections from the SharePoint landing page...you can create subsites under a communication sites and user modern pages and WebParts to have a "similar" look & feel to what you have in a communication site
Highlighted
All that is coming with the new SharePoint Admin center only.... though no idea when that is being rolled-out
Highlighted
:-)...we might have clue about when the new SPO stuff could com: Ignite...but let's see
Highlighted

We also need the ability to create Communication sub-sites. It's what's stopping us from fully adopting them.

Highlighted

@Mohammad Housaini Yep this is total BS. The Modern ui is nowhere near ready for production use. 

Highlighted

@matt howell The IA recommendations proposed by Microsoft, are to avoid sub sites all together and to use a Flat Architecture for all of your sites. 

Highlighted

@Mohammad Housaini what is your example scenario for needing communication sub-sites?

Highlighted
Bit harsh, all depends on particular use case, for the majority I feel modern is now ready and classic migrations should be of a priority
Highlighted

@Warwick Ward Hi Warwick.  Here is my situation where I would like to use a communication sub-site.  We are developing an internal company portal.  The HR department has a site, for content relevant to all employees.  They also need to develop a set of modern site pages that are relevant to and only viewable by supervisors.  This would best be served by a subsite, but they are unhappy with the difference in the look and feel between a communications site and a team site.

Highlighted

@Mike-FSA Sub sites are no longer "recommended" by Microsoft.  A couple options would be to just permission the pages that are relevant to those supervisors on the same site. Or, turn the HR site into a Hub site and create an associated communication site for your supervisors to read content from HR or content living in the associated site.