SOLVED
Home

Convert to Communication Site

%3CLINGO-SUB%20id%3D%22lingo-sub-83044%22%20slang%3D%22en-US%22%3EConvert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83044%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20there%20be%20any%20way%20to%20convert%20a%20previous%20team%20site%20to%20a%20communication%20site%3F%20Or%20will%20we%20have%20to%20recreate%20and%20migrate%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292827%22%20slang%3D%22en-US%22%3ERe%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292827%22%20slang%3D%22en-US%22%3EThat%20is%20my%20understanding.%20Until%20then%20you%20need%20to%20use%20the%20process%20posted%20by%20Marc%20%3CA%20href%3D%22https%3A%2F%2Fsympmarc.com%2F2018%2F08%2F20%2Fcreating-a-modern-home-page-for-the-root-site-in-a-tenant%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsympmarc.com%2F2018%2F08%2F20%2Fcreating-a-modern-home-page-for-the-root-site-in-a-tenant%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292810%22%20slang%3D%22en-US%22%3ERe%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292810%22%20slang%3D%22en-US%22%3E%3CP%3EI%20also%20watched%20the%20very%20brief%20demo%20at%20Ignite.%26nbsp%3B%20If%20the%20PowerShell%20works%20for%20the%20root%20site%20are%20we%20to%20assume%20it%20will%20work%20for%20any%20existing%20team%20site%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-271278%22%20slang%3D%22en-US%22%3ERe%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-271278%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20Ignite%20just%20announced%20the%20possibility%20of%20converting%20using%20PowerShell.%20In%20this%20case%2C%20they%20demonstrated%20converting%20the%20SharePoint%20Online%20Root%20site%20to%20a%20communication%20site%3A%20More%20info%20%3CA%20href%3D%22https%3A%2F%2Feschrader.com%2F2017%2F11%2F30%2Fsharepoint-online-enable-new-modern-experience-on-root-site-collection%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Feschrader.com%2F2017%2F11%2F30%2Fsharepoint-online-enable-new-modern-experience-on-root-site-collection%2F%3C%2FA%3E%3C%2FP%3E%3CP%3EIt's%20been%20said%20this%26nbsp%3Bfeature%20should%20be%20released%20at%20the%20end%20of%202018.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-194643%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-194643%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20saw%20the%20mobile%20app%20update%20the%20shows%20the%20homepage%20of%20team%20site%20just%20like%20it%20does%20for%20communication%20sites.%20That%20helps.%20Thanks%20for%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20really%20see%20a%20usecase%20for%20a%20Yammer%20%2F%20Communication%20site%20combo.%20For%20large%20audiences%20sites%2C%20we%20do%20not%20need%20nor%20want%20all%20the%20other%20Groups'%20services.%20Just%20a%20site%20and%20a%20place%20to%20discuss.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20current%20workaround%20is%20a%20PowerShell%20script%20that%20will%20use%20the%20same%20.csv%20format%20as%20Yammer%20wants%20to%20assign%20visitors%20access%20to%20the%20communication%20site.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-192143%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-192143%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20is%20quite%20confusing.%3CBR%20%2F%3EI%20am%20pretty%20sure%20that%20if%20i%20create%20a%20Modern%20Team%20Site%20from%20the%20NEW%20SP%20admin%20center%20(preview)%2C%20it%20does%20create%20the%20site%20and%20a%20group.%20I%20have%20verified%20this.%3C%2FP%3E%3CP%3Ewhat%20i%20don't%20understand%20is%20why%20the%20webparts%20aren't%20available.%3C%2FP%3E%3CP%3EWhat%20is%20the%20point%20of%20being%20able%20to%20create%20a%20Modern%20Team%20Site%20without%20an%20Office%20group%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-192141%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-192141%22%20slang%3D%22en-US%22%3EThe%20Site%20must%20be%20Group%20connected%20to%20get%20those%20webparts.%20So%20communication%20sites%20will%20not%20work.%20However%20if%20you%20create%20a%20site%20from%20admin%20console%20you%20can%20later%20use%20the%20new%20PowerShell%20commands%20when%20they%20go%20live%20to%20convert%20them%20to%20Group%20connected%20sites%2C%20then%20you%20will%20be%20able%20to%20use%20those%20web%20parts.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-192140%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-192140%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20statement%20still%20true%3F%3C%2FP%3E%3CP%3EI%20am%20struggling%20with%20understanding%20where%20i%20can%20use%20the%20o365%20connectors%20webpart%20and%20where%20i%20cannot.%3C%2FP%3E%3CP%3EMy%20testing%20so%20far%20has%20yielded%20this%3A%3C%2FP%3E%3CP%3ENew%20Connector%20webpart%20is%20seems%20to%20only%20be%20available%20in%20these%202%20scenarios%3A%3C%2FP%3E%3CP%3E1.%20create%20a%20sharepoint%20modern%20team%20site%20from%20SHarePoint%20Landing%20Page%3C%2FP%3E%3CP%3E2.%20create%20a%20teams%20channel%20with%20associated%20team%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConnector%20webpart%20does%20not%20show%20up%20when%3A%3C%2FP%3E%3CP%3E1.%20you%20create%20a%20modern%20team%20site%20from%20the%20new%20sharepoint%20admin%20console.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183830%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183830%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E%26nbsp%3Bthank%20you%20again%20for%26nbsp%3Bthe%20conversation%26nbsp%3B-%20I%20did%20notice%20that%2C%20and%20it%20does%20work...%20but%20as%20you%20noted%20it%20just%20moves%20the%20web%20parts%20farther%20to%20the%20left.%20The%20%22modern%20page%22%20already%20leaves%20a%20large%20amount%20of%20unused%20real%20estate%20to%20the%20right%20already.%20Adjusting%20the%20layout%20of%20the%20page%20has%20become%20extremely%20deprecated%20-%20again%20no%20more%20Oslo%20or%20Seattle%20choice%20once%2C%20the%20site%20is%20created.%26nbsp%3BAdditionally%2C%20there%20is%20no%20choice%20to%20use%20the%20%22Full%20Width%22%20web%20part%20in%20the%20standard%20modern%20page.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20would%20be%20nice%20is%20if%20the%20page%20choice%20would%20consist%20of%20a%20%22team%20page%20layout%22%20or%20a%20%22communications%20page%20layout%22%20in%20the%20interim%20until%20we%20are%20allowed%20to%20have%20more%20control%20over%20the%20layout%20of%20the%20page%20-%20like%20centering%20the%20web%20parts...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20just%20currently%20seems%20that%20the%20new%20modern%20features%20enforce%20to%20many%20%22ball%20and%20chain%22%20type%20scenarios%20where%20you%20are%20forced%20to%20have%20%3CEM%3E%3CSTRONG%3Eless%3C%2FSTRONG%3E%3C%2FEM%3E%20flexibility.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHoping%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F96%22%20target%3D%22_blank%22%3E%40Mark%20Kashman%3C%2FA%3E%26nbsp%3Band%20team%20are%20working%20on%20this%20-%20maybe%20something%20in%20the%20works%20for%20%23SPC18%20-%20one%20can%20only%20hope.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183758%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183758%22%20slang%3D%22en-US%22%3EI%20noticed%20something%20recently%20(not%20sure%20if%20this%20is%20new%20or%20not)%20but%20there%20is%20a%20way%20to%20hide%20the%20left%20navigation%20on%20a%20team%20site.%20In%20Site%20Settings%20%26gt%3B%20Look%20and%20Feel%20%26gt%3B%20Navigation%20Elements%20you%20can%20un-check%20Enable%20Quick%20Launch.%20This%20won't%20center%20your%20web%20parts%20on%20the%20page%20like%20the%20Comm%20Site%20page%20layout%2C%20but%20it%20will%20remove%20the%20Quick%20Launch.%20(It%20basically%20%22pushes%22%20the%20web%20parts%20to%20the%20left.)%20I%20know%20this%20isn't%20a%20perfect%20answer%2C%20but%20it%20might%20help.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20know%20that%20Microsoft%20has%20heard%20the%20message%20loud%20and%20clear%20that%20we%20would%20like%20to%20be%20able%20to%20use%20a%20Comm%20Site%20for%20the%20root%20site.%20I%20agree%20that%20the%20real%20difference%20between%20team%20site%20and%20comm%20site%20is%20intent%20and%20purpose%20(and%20the%20security%20model%20and%20services)%2C%20not%20how%20it%20looks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183656%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183656%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F875%22%20target%3D%22_blank%22%3E%40Christopher%20Webb%3C%2FA%3E%26nbsp%3Bgreat%20point%20on%20the%20%22Modern%20UI%22.%20Our%20users%20want%20to%20use%20the%20modern%20UI%20and%20we%20are%20not%20using%20Office%20365%20Groups.%20Additionally%2C%20we%20have%20some%20users%20that%20like%20the%20Centered%20look%20of%20the%20Communications%20Sites.%20Not%20like%20the%20old%20days%20when%20we%20could%20choose%20the%20%22Seattle%20or%20Oslo%22%20Layout%20on%20the%20fly.%20You%20either%20have%20the%20left%20NAV%20or%20you%20don't.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E%26nbsp%3Bthe%20point%20I%20was%20trying%20to%20make%20earlier%2C%20I%20guess%20what%20I%20am%20trying%20to%20say%20is%20a%20%22Communications%20site%20vs%20a%20Team%20Site%22%20is%20all%20in%20how%20you%20use%20it%20not%20how%20it%20looks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20still%20love%20to%20convert%20my%20root%20site%20to%20a%20Communications%20Site%20using%20the%20%22Communications%20Site%20Template%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183653%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183653%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F38%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E%26nbsp%3Brealize%20this%20post%20is%20a%20little%20old%2C%20but%20I%20am%20dealing%20with%20this%20issue%20currently%20and%20was%20reading...%20My%20issue%20is%20that%20we%20cannot%20use%20the%26nbsp%3B%22View%22%20or%20Layout%20of%20the%20Communications%20sites%20as%20team%20sites.%20I%20have%20plenty%20of%20users%20that%20do%20not%20like%20the%20Left%20Navigation%20and%20would%20rather%20have%20the%20full%20scope%20of%20the%20real-estate.%20Right%20now%2C%20there%20is%20not%20easy%20way%20to%20choose%20that%20layout%20with%20Modern%20Pages%20-%20once%20the%20Left%20Nav%20is%20there%2C%20no%20removing%20it%20-%20specifically%20for%20those%20of%20us%20in%20very%20large%20Hybrid%20Setups%20that%20are%20not%20actively%20using%20Office%20365%20Groups.%20Currently%20our%20hundreds%20of%20Site%20Collections%20start%20as%20classic%20team%20sites%20and%20have%20educated%20the%20users%20on%20creating%20a%20modern%20home%20page.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20real%20issue%20for%20me%20is%20that%20I%20have%20this%20home%20site%20-%20Classic%20-%20that%20I%20would%20like%20to%20convert%20to%20a%20Communications%20Template%20-%20where%20%22there%20are%20a%20small%20number%20of%20users%20and%20a%20large%20number%20of%20readers%20and%20the%20security%20groups%20are%20the%20more%20traditional%20SharePoint%20groups%22%20and%20I%20cannot%20find%20an%20easy%20way.%20Any%20thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160209%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160209%22%20slang%3D%22en-US%22%3EGot%20the%20feedback%20in%20terms%20of%20preference%2C%20though%20I%20was%20encourage%20you%20to%20consider%20the%20length%20you%20can%20take%20your%20desired%20outcome%20to%20come%20from%20a%20serious%20reworking%20of%20the%20related%20site's%20home%20page%2C%20to%20mock%20it%20up%20as%20close%20to%20what%20you%20like%20about%20the%20communication%20site%20-%20aka%2C%20use%20the%20right%20web%20parts%2C%20layouts%2C%20etc%20as%20you%20edit%20the%20home%20page.%20And%20if%20you%20create%20any%20subpages%2Fnews%2C%20consider%20them%20a%20form%20of%20communication%20within%20the%20site.%20And%20know%20that%20if%20you%20nailed%20the%20right%20group%20membership%2C%20then%20you're%20mainly%20structuring%20how%20the%20users%20experience%20the%20site%2C%20engage%20with%20Yammer%2C%20media%2C%20etc..%20Hope%20that%20helps%2C%20and%20thanks%20to%20Sue%20for%20engaging%20and%20working%20on%20a%20solution%2Fanswer.%20Cheers%2C%20Mark.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158979%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158979%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20read%20that%20the%20mobile%20experience%20is%20very%20different%20on%20a%20Communication%20site.%20After%20a%20quick%20comparison%20on%20my%20iPhone%2C%20I%20changed%20my%20mind.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20will%20be%20a%20Comm%20site%20NOT%20linked%20to%20the%20Yammer.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EToo%20many%20limitations%20%2F%20restrictions.%20No%20perfect%20solution.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20input.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158973%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158973%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20could%20Pin%20the%20SharePoint%20Comm%20Site%20to%20the%20Yammer%20group%20site.%20That%20way%20the%20link%20would%20be%20there.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158946%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158946%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20I%20do%20that%2C%20the%20links%20in%20the%20Yammer%20group%20to%20the%20SharePoint%20%26nbsp%3B%2F%20OneNote...%20will%20not%20redirect%20users%20to%20the%20right%20site.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'll%20go%20for%20the%20features%20instead%20of%20the%20look%20and%20stick%20to%20the%20Team%20Site.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20hope%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F96%22%20target%3D%22_blank%22%3E%40Mark%20Kashman%3C%2FA%3E%26nbsp%3Band%20his%20team%20have%20a%20%C2%ABSelect%20page%20layout%C2%BB%20or%20%C2%ABUse%20top%20navigation%C2%BB%20it%20in%20his%20backlog.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158914%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158914%22%20slang%3D%22en-US%22%3E%3CP%3EOK!%20Now%20I%20get%20it.%20No%2C%20the%20site%20that%20you%20get%20when%20you%20provision%20the%20Yammer%20group%20is%20a%20%22team%22%20site%2C%20not%20a%20Communication%20Site.%20But%20-%20you%20don't%20have%20to%20use%20it.%20You%20can%20create%20a%20parallel%20Comm%20Site%20and%20embed%20the%20Yammer%20Group%20on%20the%20site%20-%20either%20on%20the%20home%20page%20or%20on%20another%20page.%20Does%20that%20work%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158841%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158841%22%20slang%3D%22en-US%22%3E%3CP%3EI'll%20try%20to%20rephrase%20it%20(would%20be%20easier%20in%20french).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAn%20Office%20365%20connected%20Yammer%20group%20allow%20users%20to%20have%20discussion%20in%20Yammer%20and%20have%20access%20to%20all%20the%20Group%20services.%20One%20of%20the%20being%20the%20SharePoint%20site.%20It's%20exactly%20what%20I%20need.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnly%20issue%20is%2C%20since%20the%20site%20is%20created%20in%20the%20background%20as%20a%20part%20of%20the%20Group%20provisioning%2C%20I%20cannot%20select%20a%20communication%20site%20template.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20only%20looking%20for%20a%20way%20to%20keep%20the%20Communication%20Site%20look%20with%20the%20group%20connected%20team%20site%20features.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158827%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158827%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20not%20sure%20I'm%20following.%20Hoping%20someone%20else%20can%20chime%20in!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158823%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158823%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Sue%20for%20the%20quick%20reply.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20will%20not%20be%20an%20open%20group.%20I%20need%20to%20control%20yammer%20and%20SharePoint%20access.%20One%20option%20is%20to%20manage%20the%20access%20with%20dynamic%20membership%20and%20use%20the%20same%20rules.%20But%20again%2C%20on%20a%20communication%20site%2C%20I%20will%20not%20have%20a%20group%20for%20that.%20I%20would%20need%20to%20create%20an%20AAD%20group%20and%20assign%20it%20as%20a%20member%20of%20the%20site.%20Doing%20that%2C%20I%20loose%20visibility%20of%20the%20members.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEasiest%20way%20would%20be%20to%20use%20the%20Group's%20site%20and%20hope%20that%20there%20will%20be%20a%20way%20in%20a%20not%20too%20distant%20future%20to%20change%20the%20site%20page%20layout.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDo%20you%20see%20another%20option%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158784%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158784%22%20slang%3D%22en-US%22%3E%3CP%3ECould%20you%20just%20add%20the%20Yammer%20web%20part%20to%20the%20page%3F%20The%20permissions%20on%20the%20web%20part%20align%20with%20the%20permissions%20on%20the%20Yammer%20group%20so%20if%20you%20show%20an%20open%20Yammer%20group%20on%20a%20page%2C%20anyone%20in%20that%20group%20can%20interact%20with%20the%20group%20directly%20on%20the%20Comm%20Site%20page.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158774%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158774%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E%26nbsp%3Bhere%20is%20an%20example%20of%20a%20similar%20situation.%20I%20have%20to%20create%20a%20Yammer%20connected%20Office%20365%20group.%20Discussions%20will%20take%20place%20on%20Yammer%20between%20members%20of%20that%20community%20and%20documents%20will%20be%20shared%20%2F%20published%20on%20the%20SharePoint%20site%20by%20the%20community%20managers.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20would%20really%20like%20to%20use%20the%20look%20of%20a%20communication%20site%20as%20it%20will%20be%20more%20a%20publishing%20site%20than%20a%20collaboration%20site.%20To%20use%20full%20width%20of%20the%20page%20and%20the%20top%20navigation.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20want%20to%20connect%20the%20Yammer%20and%20the%20site%20because%20I%20want%20the%20membership%20to%20be%20shared.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20I%20could%20change%20the%20site%20layout%2C%20it%20would%20solve%20my%20needs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F96%22%20target%3D%22_blank%22%3E%40Mark%20Kashman%3C%2FA%3E%26nbsp%3Bis%20there%20something%20that%20could%20be%20done%20on%20the%20SharePoint%20side%20to%20alter%20the%20look%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139642%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139642%22%20slang%3D%22en-US%22%3EWithout%20trying%20to%20make%20this%20too%20long%2C%20I%20would%20use%20Comm%20Sites%20for%20your%20file%20drop%20sites.%20The%20permissions%20on%20that%20site%20use%20classic%20SharePoint%20Groups%2C%20which%20sounds%20like%20a%20better%20fit%20for%20that%20purpose.%20You%20can%20then%20see%20if%20you%20can%20create%20a%20Flow%20to%20change%20the%20permissions.%20Instead%20of%20thinking%20everything%20has%20to%20be%20a%20traditional%20team%20site%2C%20think%20about%20the%20combination%20of%20Communication%20Sites%20%2B%20modern%20Team%20Sites%20and%20see%20if%20that%20might%20help%20you%20let%20go%20a%20little%20bit.%20This%20doesn't%20have%20to%20be%20an%20all%20or%20nothing%20proposition%20-%20you%20can%20transition%20over%20time%20(thought%20that%20could%20be%20confusing%20to%20users%20who%20work%20on%20multiple%20teams).%20I%20think%20you%20might%20end%20up%20finding%20that%20you%20are%20using%20Team%20Sites%20today%20for%20things%20that%20might%20actually%20be%20better%20as%20Comm%20Sites%20in%20modern%20SharePoint.%20If%20you%20think%20about%20your%20world%20from%20the%20perspective%20of%20whether%20the%20focus%20is%20collaboration%20(everybody%20contributes)%20or%20communication%20(most%20people%20just%20read%20but%20there%20may%20be%20some%20areas%20where%20readers%20can%20write)%2C%20you%20just%20might%20be%20able%20to%20go%20modern%20for%20the%20new%20year!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139636%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139636%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Susan%20-%20Traditional%20SharePoint%20site%20collections%20can%20be%20configured%20using%20Modern%20pages%20and%20Lists%20so%20they%20do%20support%20mobile%20device%20users.%26nbsp%3B%20I%20am%20typing%20my%20response%20slowly%20since%20I%20am%20trying%20to%20weigh%20if%20I%20am%20being%20'old%20school'%20and%20resistant%20to%20change.%20I%20acknowledge%20that%20there%20is%20some%20of%20that%20in%20play.%26nbsp%3B%20When%20I%20use%20a%20'group%20site'%26nbsp%3B%20(see%20I%20won't%20even%20call%20it%20a%20team%20site%20%3A)%3C%2Fimg%3E%20)%20there%20are%20fewer%20settings%20available%20(about%201%2F2%20as%20many%20on%20the%20site%20settings%20page)%20and%20I%20can't%20do%20simple%20things%20like%20change%20the%20title%20of%20the%20site.%26nbsp%3B%20In%20our%20environment%20we%20do%20NOT%20have%20self-service%20site%20creation%20or%20O365%20Group%20creation%20enabled.%20We%20provision%20these%20by%20request%20and%20for%20O365%20groups%20we%20enforce%20a%20naming%20convention%20so%20they%20don't%20collide%20with%20groups%20created%20in%20on%20on-premises%20identity%20management%20system%20that%20are%20replicated%20to%20the%20cloud.%26nbsp%3B%20%26nbsp%3BThis%20means%20that%20all%20our%20group%20sites%20are%20also%20named%20according%20to%20this%20convention.%26nbsp%3B%20%26nbsp%3BWe%20also%20have%20a%20number%20of%20sites%20where%20we%20use%20role%20based%20permissions%20on%20site%20objects.%26nbsp%3B%20I%20think%20we%20could%20still%20do%20some%20of%20that%20on%20group%20sites%2C%20but%20it%20not%20how%20group%20site%20permissions%20are%20managed%20by%20design%20and%20I%20wonder%20if%20this%20will%20cause%20me%20problems%20moving%20forward.%26nbsp%3B%20%26nbsp%3BOnce%20use%20case%20that%20comes%20to%20mind%20is%20when%20I%20want%20to%20configure%20a%20SharePoint%20site%20for%20a%20business%20process.%26nbsp%3B%20For%20example%20I%20have%20a%20few%20'file-drop'%20sites%20where%20anyone%20can%20upload%20a%20file%2C%20but%20once%20they%20do%20the%20permissions%20on%20the%20file%20are%20changes%20so%20that%20they%20have%20read%20permissions%2C%20everyone%20except%20the%20file%20admins%20has%20no%20permissions.%26nbsp%3B%20I%20admit%20this%20model%20requires%20a%20SP2010%20SPD%20workflow%20that%20uses%20an%20impersonation%20step%20and%20the%20days%20are%20limited%20(2021%3F)%20for%20this%20approach.%26nbsp%3B%20%26nbsp%3BI%20appreciate%20your%20response%20-%20I've%20switched%20to%20encouraging%20the%20use%20of%20modern%20lists%20and%20pages%20were%20possible%2C%20but%20I%20am%20still%20holding%20on%20to%20traditional%20SharePoint.%26nbsp%3B%20%26nbsp%3BI%20think%20part%20of%20it%20is%20that%20I%20know%20the%20settings%20and%20features%20and%20functionality%20of%20traditional%20SharePoint%20very%20well%20and%20I%20am%20wary%20that%20the%20functionality%20to%20solve%20a%20given%20problem%20is%20in%20one%20of%20the%20settings%20that%20are%20no%20longer%20available%20in%20the%20group%20connected%20sites.%26nbsp%3B%20%26nbsp%3BMerry%20Christmas%2C%20Happy%20Holidays%20and%20Happy%20New%20Year.%26nbsp%3B%20Greg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139435%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139435%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Greg!%20I'm%20struggling%20to%20think%20of%20a%20use%20case%20where%20I%20%3CEM%3Ewouldn't%3C%2FEM%3E%20want%20a%20new%20team%20site%20associated%20with%20an%20Office%20365%20Group.%20There%20are%20so%20many%20advantages%20from%20a%20mobile%2C%20UX%2C%20and%20governance%20perspective.%20There%20is%20obviously%20going%20to%20have%20to%20be%26nbsp%3Ba%20transition%20period%20where%20complex%20team%20sites%20with%20(ugh!)%20lots%20of%20sub-sites%20have%20to%20remain%20%22un-Groupified%2C%22%20but%20for%20any%20new%20team%20site%2C%20Groups%20are%20the%20way%20to%20go.%20For%20legacy%20team%20sites%2C%20I%20would%20look%20for%20opportunities%20to%20Groupify%20if%20the%20team%20is%20going%20to%20persist%20into%20the%20future.%20Am%20I%20missing%20a%20use%20case%20where%20you%20might%20not%20want%20to%20do%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139424%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139424%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4971%22%20target%3D%22_blank%22%3E%40Katrin%20Weixel%3C%2FA%3E%26nbsp%3B-%20If%20I%20had%20to%20accomplish%20this%20today%20I%20would...%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EMigrate%20the%20content%20of%20my%20existing%20site%20e.g.%20ServiceSite%20to%20ServiceSiteTemp%3C%2FLI%3E%0A%3CLI%3EDelete%20ServiceSite%3C%2FLI%3E%0A%3CLI%3EAs%20a%20SharePoint%20Service%20admin%20or%20Global%20Admin%20I%20would%20use%20PowerShell%20to%20remove%20the%20ServiceSite%20from%20the%20Tenant%20recycle%20bin.%3C%2FLI%3E%0A%3CLI%3ECreate%20a%20new%20Comm%20site%20on%20the%20URL%20of%20ServiceSite%3C%2FLI%3E%0A%3CLI%3EMigrate%20Content%20(files%20and%20lists)%20from%20ServiceSiteTemp%20to%20my%20new%20ServiceSite%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EI%20will%20have%20to%20create%20new%20modern%20pages%20and%20configure%20the%20new%20modern%20web%20parts.%26nbsp%3B%20If%20I%20had%20to%20do%20a%20number%20of%20Service%20sites%20and%20I%20wanted%20them%20to%20have%20a%20common%20layout.%26nbsp%3B%20I%20would%20see%20if%20I%20could%20configure%20one%20and%20use%20my%20migration%20tool%20to%20copy%20the%20Service%20site%20pages%20to%20the%20other%20new%20service%20sites%20that%20are%20based%20on%20the%20Communications%20site%20template.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139422%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139422%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F38%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E%26nbsp%3B-%20What%20do%20think%20the%20role%20of%20a%20non-group%20associated%20Team%20site%20is%20and%20will%20be%20moving%20forward%3F%26nbsp%3B%20I%20probably%20should've%20posted%20this%20as%20it's%20own%20discussion%20topic%2C%20but%20I%20read%20your%20reply%20and%20I%20value%20your%20opinion%2C%20experience%20and%20knowledge%20so%20I%20posted%20my%20question%20here.%26nbsp%3B%20Thanks%20-%20Greg%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137535%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137535%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20details%2C%20the%20ability%20to%20say%20an%20existing%20site%20is%20the%20hub%20would%20be%20great.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137525%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137525%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20as%20of%20right%20now%2C%20aparently%20you%20have%20to%20create%20a%20new%20Hub%20site%2C%20they%20are%20looking%20at%20trying%20to%20make%20it%20able%20to%20use%20an%20existing%20site%20to%20be%20the%20hub%20site.%20So%20I%20am%20wrong%20about%20the%20comm%20site%2C%20I%20thought%20I%20saw%20somewhere%20at%20ignite%20but%20guess%20I%20was%20mistaken.%20Here%20is%20a%20recent%20comment%20to%20a%20post%20fro%20Mark%20on%20the%20SharePoint%20team%20regarding%20this.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F25692iDA63465F732C0AE5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.JPG%22%20title%3D%22Capture.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EFrom%20the%20comments%20of%20this%20post%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Blog%2FSharePoint-hub-sites-new-in-Office-365%2Fba-p%2F109547%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Blog%2FSharePoint-hub-sites-new-in-Office-365%2Fba-p%2F109547%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20this%20helps.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137515%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137515%22%20slang%3D%22en-US%22%3EHi%20Christopher%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20was%20unaware%20that%20the%20root%20hub%20site%20had%20to%20be%20a%20communication%20site%2C%20have%20you%20seen%20this%20specified%20somewhere%20or%20it%20that%20just%20based%20on%20the%20screenshots%20provided%20here%3F%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Blog%2FSharePoint-hub-sites-new-in-Office-365%2Fba-p%2F109547%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Blog%2FSharePoint-hub-sites-new-in-Office-365%2Fba-p%2F109547%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137389%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137389%22%20slang%3D%22en-US%22%3EAlso%2C%20I%20meant%20as%20the%20actual%20parent%20level%20hub%20site%2C%20should%20have%20been%20more%20clear%20there%20%3Ap.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137388%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137388%22%20slang%3D%22en-US%22%3ETrust%20me%2C%20I%20feel%20the%20pain%20too%2C%20I%20prefer%20the%20comm%20site%20template%20over%20quick%20launch%20bar%20for%20most%20applications.%20Shouldn't%20be%20that%20hard%20to%20let%20us%20pick%20the%20template%20for%20the%20modern%20sites%20you%20would%20think%2C%20simillar%20to%20the%20whole%20oslo%20%2F%20seattle%20selection%20from%20the%20past.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137377%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137377%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20Chris.%20For%20this%20site%2C%20I%20think%20it's%20okay%20that%20it%20won't%20be%20able%20to%20serve%20as%20a%20hub%20site%2C%20so%20long%20as%20it%20can%20link%20to%20a%20hub%20site%20(and%20according%20to%20Mark%20Kashman%2C%20that%20will%20be%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Blog%2FSharePoint-hub-sites-new-in-Office-365%2Fbc-p%2F129970%2Fhighlight%2Ftrue%23M1184%22%20target%3D%22_blank%22%3Epossible%20so%20long%20as%20the%20classic%20site%20uses%20a%20modern%20page%20as%20a%20homepage%3C%2FA%3E).%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20is%20a%20shame%20there%20is%20no%20OOTB%20option%20for%20hiding%20the%20quick%20launch.%20It%26nbsp%3Bseems%20like%20switch%20the%20layout%20to%20Oslo%20worked%20for%20classic%20team%20sites%2Fclassic%20home%20pages%2C%20though%20it%20did%20leave%20tons%20of%20excess%20padding.%20I%20would%20love%20an%20easy%20way%20to%20switch%20to%20have%20a%20homepage%20layout%20match%20the%20Comm%20site%20design...at%20least%20until%20it's%20easy%20and%20clean%20to%20migrate%20to%20a%20comm%20site.%20Nothing%20is%20ever%20easy%20with%20Microsoft!%20%3A%5C%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137367%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137367%22%20slang%3D%22en-US%22%3EQuestion%202%3A%20You%20won't%20be%20able%20to%20make%20your%20site%20a%20hub%20site%20when%20that%20feature%20is%20released%2C%20that%20is%20restricted%20to%20comm%20sites.%20So%20if%20you%20have%20seen%20that%20feature%20and%20plan%20to%20use%20it%20in%20the%20future%20this%20is%20one%20thing%20you%20will%20miss%20out%20on%20by%20mimicing%20a%20comm%20site.%20%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20for%20hiding%20the%20quick%20launch%2C%20no%20you%20cannot%20do%20that%20out%20of%20box.%20You%20can%20probably%20write%20some%20kind%20of%20custom%20webpart%20that%20will%20hide%20it%20via%20css%20overrides%20somehow%2C%20or%20by%20using%20application%20customizer%2C%20but%20this%20will%20require%20code%20etc.%20in%20order%20to%20acommplish%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137365%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137365%22%20slang%3D%22en-US%22%3E%3CP%3EFollow-up%20question%20(after%20I%20played%20around%20much%20more%20yesterday)%3A%3C%2FP%3E%0A%3CP%3EI%20had%20issues%20with%20migrating%20lists%2Flibraries%20into%20a%20new%20comm%20site.%20I'm%20concerned%20the%20migration%20tool%20isn't%20quite%20ready%20for%20this%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20did%20have%20success%20creating%20a%20modern%20page%20on%20the%20old%20team%20site%2C%20removing%20the%20banner%20image%20using%20a%20PnP%20script%20to%20change%20layout%20from%20%22article%22%20to%20%22home%22%2C%20and%20it's%20all%20good%20except%20for%20the%20ugly%20quick%20launch%20display.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EQuestion%201%3A%20does%20anyone%20know%20of%20a%20way%20to%20make%20this%20look%20more%20like%20a%20comm%20home%20page%20by%20hiding%20the%20QL%20from%20the%20left%20nav%20and%20displaying%20it%20as%20a%20top%20nav%20instead%3F%20I%20tried%20%22changing%20the%20look%22%20from%20Seattle%20to%20Oslo%2C%20but%20that%20appears%20to%20only%20help%20with%20classic%20experience%2C%20not%20modern%20pages.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EQuestion%202%3A%20is%20the%20any%20major%20difference%20in%20how%20Comm%20sites%20are%20set%20up%20in%20the%20background%20that%20I%20will%20be%20missing%20out%20on%2Fmessing%20up%20by%20%22mocking%22%20the%20experience%20via%20a%20modern%20page%20homepage%20on%20a%20classic%20team%20site%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20this%20all%20makes%20sense!%20Thanks%20for%20any%2Fall%20advice%20on%20this%20matter!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136943%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136943%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20Lou!%20I%20need%20to%20learn%20a%20lot%20more%20about%20PnP!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136941%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136941%22%20slang%3D%22en-US%22%3EThanks%2C%20Sue!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136931%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136931%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20post%20adds%20some%20insight%20to%20replicating%20the%20Communication%20site%20homepage%20but%20only%20in%20a%20Communication%20site.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhangconsult.com%2F2017%2F11%2F05%2Fcreating-a-new-client-side-page-with-pnp-powershell%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fhangconsult.com%2F2017%2F11%2F05%2Fcreating-a-new-client-side-page-with-pnp-powershell%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20created%20new%20pages%20in%20a%20classic%20using%20the%20new%20modern%20page%20using%20PnP.%20You%20need%20to%20set%20the%20LayoutType%20to%20%22Home%22%20so%20that%20the%20big%20banner%20image%20is%20not%20included.%20It%20is%20included%26nbsp%3Bwhen%20it%20is%20an%20Article%20LayoutType.%26nbsp%3BThe%20above%20link%20does%20show%20how%20he%20creates%20a%20new%20page.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20were%20recent%20updates%20to%20the%20PnP%20so%20that%20needs%20to%20be%20explored%20to%20see%20if%20we%20can%20now%20get%20the%20layout%20we%20want%20on%20other%20sites.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136930%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136930%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20your%20use%20case%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4971%22%20target%3D%22_blank%22%3E%40Katrin%20Weixel%3C%2FA%3E%2C%20it%20sounds%20like%20you%20do%20want%20to%20make%20new%20Communication%20Sites%20for%20your%20service%20center%20sites.%20Yes%2C%20it%20would%20mean%20a%20URL%20change%20and%20yes%2C%20your%20links%20might%20break%2C%20but%20at%20the%20end%20of%20the%20day%2C%20the%20short%20term%20pain%20would%20give%20you%20the%20best%20long%20term%2C%20sustainable%20outcome.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136926%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136926%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20also%20very%20interested%20in%20this%20topic.%20We%20have%20mostly%20classic%20team%20sites%20that%20were%20set%20up%20for%20both%20collaboration%20(private%20team)%20efforts%20as%20well%20as%20broadcasting%20services%20(service%20center%20sites).%20We%20really%20want%20to%20use%20communication%20sites%20for%20those%20service%20center%20sites%2C%20and%20I%20was%20trying%20to%20decide%20if%20I%20should%20migrate%20content%20from%20the%20service%20centers%20into%20new%20comm%20sites%20(but%20that%20would%20mean%20URL%20change%20and%20potential%20issues%20with%20migration)%20or%20if%20I%20should%20use%20a%20modern%20page%20as%20the%20homepage%20of%20the%20old%20existing%20sites.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20I%20hate%20with%20the%20option%20of%20setting%20a%20modern%20page%20as%20the%20homepage%20of%20a%20team%20site%20is%20that%20the%20look%20isn't%20nearly%20as%20pretty%20as%20the%20comm%20sites.%20You%20are%20stuck%20with%20a%20quick%20launch%2C%20a%20site%20title%2C%20AND%20a%20weird%20banner%20image%20and%20title.%20So%20to%20update%20an%20existing%20service%20center%20site%20and%20use%20a%20HERO%20web%20part%2C%20that%20HERO%20web%20part%20would%20now%20be%20stuck%20under%20a%20page%20banner%20and%20title%2C%20which%20would%20be%20under%20the%20site%20title%2Fheader.%20And%20all%20would%20be%20pushed%20over%20because%20of%20the%20quick%20launch.%20Yuck!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20looking%20forward%20to%20hearing%20from%20anyone%20who%20has%20a%20good%20solution%20for%20this.%20I%20fear%20the%20current%20answer%20is%20%22wait%20until%20Microsoft%20sets%20up%20an%20option%20that%20meets%20your%20needs.%22%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134398%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134398%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20has%20been%20awhile%20since%20this%20was%20posted.%20I%20want%20to%20see%20if%20anyone%20has%20figured%20out%20how%20to%20apply%20the%20stuff%20that%20makes%20a%20Communication%20into%20a%20Team%20site.%26nbsp%3B%20I%20have%20clients%20who%20want%20the%20look%20of%20the%20communication%20topic%20site%20for%20their%20SPO%20root%20site.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20tried%20to%20apply%20a%20Communication%20template%20to%20the%20root%20web%20using%20SharePoint%20PnP.%20The%20home%20page%20picked%20up%20the%20elements%20but%20the%20quick%20launch%20is%20still%20there.%20I%20am%20guessing%20there%20is%20either%20a%20hidden%20feature%20or%20master%20page%20that%20goes%20with%20the%20communication%20site.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91745%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91745%22%20slang%3D%22en-US%22%3E%3CP%3EYour%20correct%2C%20there%20is%20currently%20no%20%22Modern%20UI%22%20Templates%20for%20existing%20sites.%20That%20aparently%20is%20coming%20at%20a%20later%20date.%20They%20are%20going%20to%20talk%20about%20it%20at%20Ignite%2C%20no%20clue%20on%20timeline%2C%20but%20my%20guess%20is%20their%20Year%20End%20release.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWish%20we%20could%20at%20least%20change%20Modern%20UI%20to%20existing%20Comm%20site%20template%20at%20a%20minimum%20earlier%20than%20that%2C%20but%20one%20could%20wish.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91638%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91638%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F875%22%20target%3D%22_blank%22%3E%40Christopher%20Webb%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20a%20side%20note%20to%20this%20thread.%20The%20reason%20people%20want%20to%20use%20comm%20sites%20for%20their%20current%20sites%20is%20the%20existing%20modern%20UI%20with%20the%20side%20quicklaunch%20bar%20has%20too%20muich%20wasted%20space%20and%20isn't%20very%20intuitive.%20The%20top%20quick%20launch%20bar%20is%20much%20better.%20That%20IMO%20is%20the%20biggest%20reason%20why%20people%20want%20to%20use%20the%20sites%20over%20just%20adding%20webparts%20to%20the%20existing%20parts.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EAm%20I%20to%20understand%20that%20currently%20there%20is%20no%20option%26nbsp%3Bto%20reclaim%20the%20side%20quick%20launch%20space%3F%26nbsp%3B%20I%20created%20a%20new%20modern%20page%20(thanks%20Andrew)%2C%20made%20it%20the%20home%20page%2C%20and%20now%20experimenting%20with%20the%20various%20comm%20template%20web%20parts%20(screenshot).%26nbsp%3B%20I%20have%20at%20least%20two%20clients%20that%20will%20want%20to%20'convert'%20their%20home%20page%20to%20comm%20templates%20and%20they%20will%20probably%20want%20to%20remove%20the%20side%20quick%20launch.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F17951i7B4D26579E0AF8B7%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22converted%20page.JPG%22%20title%3D%22converted%20page.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86431%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86431%22%20slang%3D%22en-US%22%3EYou%20are%20absolutely%20right.%20I%20don't%20know%20why%20I%20assumed%20sites%20created%20a%20group.%20Thanks%20for%20the%20input.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86380%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86380%22%20slang%3D%22en-US%22%3E%3CP%3EComm%20sites%20don't%20create%20groups.....it%20created%20a%20secondary%20site%20collection%20maybe%20in%20terms%20of%20naming%2C%20but%20it%20doesn't%20create%20a%20office%20365%20group%20tied%20to%20it.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20a%20side%20note%20to%20this%20thread.%20The%20reason%20people%20want%20to%20use%20comm%20sites%20for%20their%20current%20sites%20is%20the%20existing%20modern%20UI%20with%20the%20side%20quicklaunch%20bar%20has%20too%20muich%20wasted%20space%20and%20isn't%20very%20intuitive.%20The%20top%20quick%20launch%20bar%20is%20much%20better.%20That%20IMO%20is%20the%20biggest%20reason%20why%20people%20want%20to%20use%20the%20sites%20over%20just%20adding%20webparts%20to%20the%20existing%20parts.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20they%20are%20going%20to%20talk%20about%20templates%20and%20color%20modifications%20at%20ignite%20etc.%20for%20modern%20sites%20but%20that's%20just%20so%20far%20away%2C%20I%20wish%20we%20could%20just%20get%20a%20temporary%20solution%20in%20place%20to%20turn%20the%20%22look%20and%20feel%22%20into%20%22Modern%22%20similar%20to%20oslo.%20on%20the%20old%20sites%20would%20really%20help%20appease%20the%20mojority.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86351%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86351%22%20slang%3D%22en-US%22%3EI%20only%20mention%20that%20because%20that%20came%20up%20in%20our%20organization.%20A%20department%20created%20a%20group%20using%20stream%20to%20put%20all%20of%20their%20videos%20(Not%20HR%2C%20it%20was%20just%20an%20example).%20Later%2C%20I%20receive%20a%20request%20to%20build%20them%20a%20site%20that%20will%20be%20used%20to%20communicate%20updates%20to%20the%20whole%20organization.%20I%20went%20to%20create%20the%20site%20using%20the%20new%20communications%20site%20template%20and%20it%20created%20a%20secondary%20group.%20I%20wanted%20to%20use%20the%20current%20group%20already%20in%20place.%20You%20are%20right%2C%20the%20web%20parts%20and%20such%20could%20be%20used%20on%20the%20Team%20Site%20template%20as%20well.%20Not%20a%20big%20issue%20but%20would%20have%20preferred%20to%20use%20the%20Communication%20Site%20template%20from%20the%20get%20go.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86071%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86071%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20you%20might%20want%20to%20think%20about%20this%20differently.%20If%20HR%20wants%20a%20private%20team%20site%2C%20you%20should%20use%20a%20Team%20Site%20-%20which%20leverages%20the%20Office%20365%20Group%20for%20identity.%20If%20they%20want%20the%20%22look%22%20of%20a%20Communication%20Site%20(i.e.%20the%20web%20parts)%2C%20they%20can%20use%20the%20same%20web%20parts%20in%20the%20Team%20SIte%20-%20but%20the%20audience%20is%20private.%20A%20key%20difference%20with%20the%20Communication%20Site%20template%20is%20that%20the%20security%20model%20does%20not%20use%20an%20Office%20365%20group%20by%20default.%20It%20makes%20sense%20that%20the%20other%20places%20to%20create%20a%20site%20are%20%22team%22%20based%20-%20because%20they%20are%20typically%20for%20getting%20team%20work%20done.%20Communication%20Sites%20are%20more%20about%20showcasing%20a%20service%2C%20telling%20a%20story%2C%20or%20communicating%20more%20broadly%20-%20not%20about%20collaboration%20as%20with%20team%20sites.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86050%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86050%22%20slang%3D%22en-US%22%3E%3CP%3EI%20believe%20the%20issue%20here%20is%20due%20to%20the%20many%20locations%20that%20Office%20365%20groups%20are%20created%20(i.e.%20Planner%2C%20Stream%2C%20Teams%2C%20etc.)%20that%20will%20also%20create%20a%20'team%20site'%20by%20default.%20For%20example%2C%20Let%20say%20I%20am%20using%20Microsoft%20Stream%20and%20click%20on%20%22My%20Groups%22%20I%20create%20a%20group%20for%20the%20HR%20department%20to%20upload%20all%20their%20videos%20and%20add%20channels%20under.%20Later%20on%20they%20want%20build%20a%20site%20for%20their%20department%20using%20the%20Communcations%20site%20template.%20By%20default%20when%20a%20group%20is%20created%2C%20a%20'Team%20Site'%20is%20created%20with%20that%20group.%20If%20I%20went%20to%20create%20a%20new%20site%20with%20the%20communications%20site%20template%20it%20will%20create%20the%20url%20with%20https%3A%2F%2F%3CTENENT%3E%2Fsites%2FHumanReources2%20which%20is%20a%20whole%20different%20group%20now.%20What%20I%20am%20saying%20is%20if%20the%20group%20is%20created%20first%20and%20later%20they%20try%20to%20create%20the%20site%20with%20the%20business%20purpose%20of%20using%20communications%20site.%20This%20makes%20it%20difficult.%26nbsp%3B%3C%2FTENENT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-84267%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-84267%22%20slang%3D%22en-US%22%3E%3CP%3ESome%20web%20parts%20and%20changes%20are%20not%20visable%20by%20those%20without%20first%20release.%20%26nbsp%3BFor%20example%20the%20grey%20bar%20still%20appears%20for%20those%20without%20first%20release.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83609%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83609%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20for%20selected%20users%20--%20I'm%20assuming%20that%20means%20the%20first%20release%20users%20can%20create%20communications%20sites%20and%20use%20the%20new%20web%20parts%2C%20but%20all%20users%20can%20see%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83468%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83468%22%20slang%3D%22en-US%22%3EYou%20can%20add%20a%20modern%20page%20to%20an%20old%20school%20SharePoint%20site%20by%20adding%20a%20Site%20page%20to%20a%20site%20pages%20library%20and%20setting%20it%20as%20the%20homepage.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83333%22%20slang%3D%22en-US%22%3ERe%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83333%22%20slang%3D%22en-US%22%3ETeam%20Site%20used%20as%20a%20Publishing%20Site%3F%20No%20way.%20I%20don't%20believe%20you!!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83322%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83322%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20on%20first%20release%20for%20all%20users%2C%20or%20do%20you%20have%20selected%20users%20setup%3F%20Hoping%20First%20Releast%20option%20by%20itself%20is%20enough%20to%20get%20the%20quicker%20release!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83317%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83317%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-right%22%20style%3D%22width%3A%20304px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F16588i2DA8ECD840931C88%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22hero-web-part.PNG%22%20title%3D%22hero-web-part.PNG%22%20%2F%3E%3C%2FSPAN%3EJust%20got%20the%20Communications%20Site%20on%20first%20release%2C%20and%20checked%20back%20on%20some%20team%20sites.%26nbsp%3B%20Looks%20like%20the%20Hero%20web%20part%20and%20other%20communications%20components%20are%20now%20available%20on%20the%20team%20sites%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83270%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83270%22%20slang%3D%22en-US%22%3Ecan%20you%20even%20create%20comm%20sites%20yet%3F%20They%20haven't%20pushed%20this%20to%20most%20people%20yet.%20Once%20you%20can%20create%20site%20%26gt%3B%20Comm%20site%20shows%20up%2C%20my%20guess%20is%20then%20you%20should%20have%20the%20webparts%20set%20to%20modern%20team%20sites.%20BUT%20if%20your%20existing%20site%20is%20just%20a%20site%20collection%2C%20I%20don't%20think%20they%20have%20put%20in%20the%20mechanism%20to%20convert%20an%20old%20school%20site%20to%20a%20modern%20site%20yet.%20So%20until%20that%20happens%20your%20only%20option%20would%20be%20to%20create%20a%20Comm%20site%20and%20more%20content.%203rd%20party%20tool%20is%20a%20must%20IMO%20these%20days%20for%20doing%20that.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83187%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83187%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20pretty%20sure%20you%20can%20use%20the%20same%20web%20parts%20on%20Team%20Sites%20and%20Comm%20Sites.%20So%20you%20wouldn't%20have%20to%20migrate%20your%20content%20if%20you%20are%20already%20successfully%20collaborating%20on%20a%20team%20site%20-%20but%20maybe%20you%20want%20to%20add%20a%20Hero%20web%20part%20to%20the%20home%20page%2C%20which%20you%20should%20be%20able%20to%20do.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83178%22%20slang%3D%22en-US%22%3ERe%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83178%22%20slang%3D%22en-US%22%3EThis%20is%20a%20very%2C%20very%20common%20use%20case.%20Would%20very%20much%20like%20to%20get%20some%20kind%20of%20solution%20for%20it.%20We%20have%20many%20tenants%20who%20have%20been%20round%20and%20used%20extensively%20before%202016%2C%20so%20there%20have%20been%20different%20approaches%20as%20to%20what%20templates%20were%20used%20to%20provide%20an%20intranet%20(Non-collab)%20portal.%20It%20would%20be%20helpful%20to%20have%20some%20way%20of%20modernizing%20them.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83156%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83156%22%20slang%3D%22en-US%22%3E%3CP%3EReally%3F%20So%20far%20I%20haven't%20been%20able%20to%20use%20communication%20site%20components%20on%20my%20team%20sites.%20Am%20I%20understanding%20you%20incorrectly%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83150%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83150%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20fully%20on%20the%20same%20page%2C%20I%20was%20just%20wondering%20for%20a%20specific%20situation%20where%20I%20don't%20want%20to%20have%20to%20change%20URLs%20for%20a%20team%20site%20(pre%20groups%20era)%20we've%20been%20mainly%20using%20as%20a%20comm%20site.%20I%20could%20just%20delete%20and%20recreate%2C%20but%20that's%20a%20bit%20of%20downtime.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83142%22%20slang%3D%22en-US%22%3ERe%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83142%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20great%20responses%20everyone.%20I%20understand%20team%20sites%20are%20based%20on%20the%20group%20models%2C%20I%20am%20just%20thinking%20of%20one%20of%20my%20customers%20who%20has%20an%20old%20team%20site%20(pre-groups%20era)%20that%20they%20used%20for%20mainly%20this%20purpose.%20Would%20be%20nice%20to%20retain%20the%20same%20URL%2C%20and%20the%20only%20way%20to%20do%20that%20without%20downtime%20would%20be%20to%20change%20the%20template%20(if%20it%20was%20possible)%2C%20otherwise%20it%20would%20be%20a%20delete%20and%20recreate%20situation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83112%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83112%22%20slang%3D%22en-US%22%3EFrom%20what%20I%20read%2C%20they%20are%20also%20providing%20the%20template%20and%20the%20top%20nav%20to%20existing%20sites%20as%20well.%20We%20should%20be%20able%20to%20recreate%20the%20whole%20comm%20site%20with%20an%20existing%20site%2C%20however%20to%20echo%20others%20if%20you%20have%20a%20site%20that%20is%20modern%20tied%20to%20a%20group%20might%20not%20be%20ideal%2C%20but%20I'm%20with%20you%2C%20I%20just%20want%20alot%20of%20the%20look%20and%20feel%20for%20existing%20site%20even%20for%20existing%20team%20sites.%20Which%20I%20believe%20we%20should%20be%20able%20to%20use%20most%20of%20the%20elements%20on%20existing%20Modern%20sites.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83105%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83105%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E%26nbsp%3BI%20would%20say%20people%20will%20want%20to%20turn%20on%20full%20page%20communication%20features%20on%20existing%20team%20sites%20%2F%20group%20sites%20as%20they%20have%20started%20down%20that%20aspect%20for%20modern%20lists%20%2F%20libraries%20prior%20to%20them%20being%20deployed%20to%20other%20site%20templates.%26nbsp%3B%20In%20addition%2C%20if%20there%20was%20an%20easy%20way%20to%20MOVE%20data%20between%20sites%20(not%20just%20documents%2C%20but%20pages%2C%20list%20items%2C%20etc.)%20that%20would%20make%20this%20issue%20moot.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83095%22%20slang%3D%22en-US%22%3ERE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83095%22%20slang%3D%22en-US%22%3EWould%20you%20really%20want%20to%20do%20this%3F%20Team%20sites%20are%20focused%20on%20Collaboration%20and%20backed%20by%20Office%20365%20Groups.%20Communication%20sites%20are%20focused%20on%20broadcasting%20or%20communicating%20a%20message%20to%20a%20wide%20audience.%20In%20a%20team%20site%2C%20most%20users%20contribute%20content.%20In%20a%20Communication%20site%2C%20typically%20there%20are%20a%20small%20number%20of%20users%20and%20a%20large%20number%20of%20readers%20and%20the%20security%20groups%20are%20the%20more%20traditional%20SharePoint%20groups.%20Just%20like%20team%20sites%20and%20publishing%20sites%20previously%2C%20you%20want%20to%20chose%20the%20type%20of%20template%20that%20fits%20your%20business%20purpose.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83090%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83090%22%20slang%3D%22en-US%22%3EBut%20the%20pages%20include%20full%20width%20vs%20modern%20with%20left%20nav.%20If%20we%20could%20create%20full%20width%20pages%20on%20the%20root%20we%20could%20get%20closer.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83086%22%20slang%3D%22en-US%22%3ERE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83086%22%20slang%3D%22en-US%22%3EYou%20can%20think%20of%20Comm%20sites%20as%20another%20site%20template%2C%20i.e.%20another%20in%20the%20list%20of%20classic%20team%20sites%2C%20modern%20team%20sites%2C%20publishing%20sites%2C%20etc.%20We%20have%20never%20been%20able%20to%20truly%20convert%20a%20site%20from%20one%20site%20template%20to%20another.%20Currently%20there%20is%20no%20method%20to%20convert%20any%20type%20of%20existing%20site%20to%20a%20comm%20site%2C%20nor%20have%20I%20heard%20of%20this%20feature%20on%20the%20roadmap%20but%20MS%20may%20be%20able%20to%20provide%20more%20info.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83085%22%20slang%3D%22en-US%22%3ERE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83085%22%20slang%3D%22en-US%22%3EThe%20fastest%20way%20to%20get%20your%20site%20up%20and%20running%20will%20be%20to%20copy%20and%20paste%20content%20from%20your%20existing%20site%20pages.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83071%22%20slang%3D%22en-US%22%3ERE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83071%22%20slang%3D%22en-US%22%3ENo%20to%20recreate%20and%20migrate.%20Should%20be%20able%20to%20just%20create%20it%20quickly%20with%20current%20layout.%20Just%20update%20things.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83067%22%20slang%3D%22en-US%22%3ERE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83067%22%20slang%3D%22en-US%22%3EAll%20Communication%20site%20is%2C%20is%20a%20template.%20All%20the%20web%20parts%20used%20on%20the%20site%20are%20available%20to%20your%20other%20sites%2C%20so%20technically%20no.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633006%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633006%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F38%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3EExcept%20when%20a%20site%20has%20been%20created%20incorrectly%2C%20by%20mistake%3B%20or%20predates%20the%20release%20of%20Comms%20sites%20or...%20reasons%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20a%20need%20for%20this%20(I%20know%2C%20as%20we%20have%20it).%3C%2FP%3E%3CP%3EWe%20are%20still%20having%20issues%20converting%20some%20root%20level%20sites%20(esp%20when%20we%20had%20publishing%20enabled).%20What%20is%20the%20work%20around%3F%20Can%20we%20just%20blow%20the%20current%20root%20site%20away%20and%20recreate%20a%20new%20one%20at%20the%20root%20level%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633072%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633072%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8401%22%20target%3D%22_blank%22%3E%40Simon%20Hudson%3C%2FA%3EI%20would%20be%20very%20interested%20to%20know%20the%20answer%20as%20our%20root%20site%20was%20also%20created%20with%20publishing%20enabled.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633142%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633142%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6224%22%20target%3D%22_blank%22%3E%40Paul%20Mitchell%3C%2FA%3E%26nbsp%3BThe%20PowerShell%20script%20to%20convert%20the%20root%20site%20to%20a%20communication%20site%20is%20not%20yet%20released%20but%20as%20far%20as%20I%20know%2C%20it%20only%20works%20if%20you%20do%20not%20have%20publishing%20enabled%20on%20the%20root%20site.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633203%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633203%22%20slang%3D%22en-US%22%3EIf%20so%20it%E2%80%99s%20not%20the%20end%20of%20the%20world%20thou.%20There%20is%20a%20switch%20site%20feature%20coming%20so%20you%20can%20take%20any%20random%20comm%20site%20and%20set%20it%20as%20your%20root%20site%20collection.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633272%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633272%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3Bnot%20a%20random%20site%2C%20it%20is%20a%20script%20to%20convert%20the%20legacy%20team%20site%20that%20is%20currently%20the%20root%20of%20older%20tenants%20to%20be%20a%20comm%20site.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633284%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633284%22%20slang%3D%22en-US%22%3ECheck%20site%20swap%20section%20towards%20bottom%20of%20page%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FUpdates-to-SharePoint-security-administration-and-migration%2Fba-p%2F549585%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FUpdates-to-SharePoint-security-administration-and-migration%2Fba-p%2F549585%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%E2%80%9CSharePoint%20Site%20Swap%20(Coming%20Soon)%3CBR%20%2F%3EIn%20addition%20to%20these%20improvements%20to%20the%20SharePoint%20admin%20center%2C%20we%E2%80%99re%20also%20introducing%20new%20Windows%20PowerShell%20cmdlet%20(invoke-spositeswap)%20that%20allows%20you%20to%20replace%20the%20root%20site%20within%20a%20tenant%2C%20e.g.%20%3CA%20href%3D%22https%3A%2F%2Fcontoso.sharepoint.comwith%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcontoso.sharepoint.comwith%3C%2FA%3E%20an%20existing%20site%2C%20such%20as%20%3CA%20href%3D%22https%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2F%26lt%3Bsite%26gt%3B.%E2%80%9D%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2F%3CSITE%3E.%E2%80%9D%3C%2FSITE%3E%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633299%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633299%22%20slang%3D%22en-US%22%3EWith%20that.%20You%20don%E2%80%99t%20have%20to%20use%20your%20root%20site%20collection%20even%20if%20you%20turned%20on%20that%20publishing%20by%20accident%20so%20you%20won%E2%80%99t%20be%20tied%20down%20by%20that%20restriction%20in%20putting%20modern%20site%20as%20your%20root.%20%3CBR%20%2F%3E%3CBR%20%2F%3ENow%20if%20you%20have%20a%20big%20site%20with%20tons%20of%20content%20on%20it%2C%20it%E2%80%99ll%20be%20a%20bit%20more%20difficult%20but%20there%20will%20be%20a%20few%20more%20options%20than%20just%20converting%20the%20one%20that%20is%20there.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633328%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633328%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BDidn%E2%80%99t%20see%20that%20part.%20I%20can%20scenarios%20where%20I%20have%20been%20redirecting%20to%20a%20comm%20site%20where%20that%20will%20come%20in%20handy.%20Still%20wouldn%E2%80%99t%20recommend%20any%20old%20site%2C%20but%20if%20you%20have%20carefully%20curated%20and%20planned%20a%20great%20user%20experience%2C%20for%20sure!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%3CBR%20%2F%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633333%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633333%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BDidn%E2%80%99t%20see%20that%20part.%20I%20can%20scenarios%20where%20I%20have%20been%20redirecting%20to%20a%20comm%20site%20where%20that%20will%20come%20in%20handy.%20Still%20wouldn%E2%80%99t%20recommend%20any%20old%20site%2C%20but%20if%20you%20have%20carefully%20curated%20and%20planned%20a%20great%20user%20experience%2C%20for%20sure!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633354%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Convert%20to%20Communication%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633354%22%20slang%3D%22en-US%22%3EIt%E2%80%99ll%20be%20nice%20for%20those%20of%20us%20that%20use%20a%20comm%20site%20now%20as%20a%20landing%20page%20etc.%20and%20instead%20of%20having%20to%20migrate%20to%20root%20we%20can%20just%20use%20the%20rename%20feature%20to%20swap%20it.%20Will%20be%20interesting%20how%20content%20works%20since%20it%E2%80%99s%20a%20swap%20you%20might%20not%20get%20the%20link%20redirecting.%3C%2FLINGO-BODY%3E

I am not sure I'm following. Hoping someone else can chime in!

I'll try to rephrase it (would be easier in french).

 

An Office 365 connected Yammer group allow users to have discussion in Yammer and have access to all the Group services. One of the being the SharePoint site. It's exactly what I need.

 

Only issue is, since the site is created in the background as a part of the Group provisioning, I cannot select a communication site template.

 

I am only looking for a way to keep the Communication Site look with the group connected team site features.

 

 

OK! Now I get it. No, the site that you get when you provision the Yammer group is a "team" site, not a Communication Site. But - you don't have to use it. You can create a parallel Comm Site and embed the Yammer Group on the site - either on the home page or on another page. Does that work?

If I do that, the links in the Yammer group to the SharePoint  / OneNote... will not redirect users to the right site.

 

I'll go for the features instead of the look and stick to the Team Site.

 

I hope @Mark Kashman and his team have a «Select page layout» or «Use top navigation» it in his backlog.

 

 

You could Pin the SharePoint Comm Site to the Yammer group site. That way the link would be there.

I just read that the mobile experience is very different on a Communication site. After a quick comparison on my iPhone, I changed my mind. 

 

It will be a Comm site NOT linked to the Yammer.

 

Too many limitations / restrictions. No perfect solution.

 

Thanks for your input.

Got the feedback in terms of preference, though I was encourage you to consider the length you can take your desired outcome to come from a serious reworking of the related site's home page, to mock it up as close to what you like about the communication site - aka, use the right web parts, layouts, etc as you edit the home page. And if you create any subpages/news, consider them a form of communication within the site. And know that if you nailed the right group membership, then you're mainly structuring how the users experience the site, engage with Yammer, media, etc.. Hope that helps, and thanks to Sue for engaging and working on a solution/answer. Cheers, Mark.

@Susan Hanley realize this post is a little old, but I am dealing with this issue currently and was reading... My issue is that we cannot use the "View" or Layout of the Communications sites as team sites. I have plenty of users that do not like the Left Navigation and would rather have the full scope of the real-estate. Right now, there is not easy way to choose that layout with Modern Pages - once the Left Nav is there, no removing it - specifically for those of us in very large Hybrid Setups that are not actively using Office 365 Groups. Currently our hundreds of Site Collections start as classic team sites and have educated the users on creating a modern home page.

 

The real issue for me is that I have this home site - Classic - that I would like to convert to a Communications Template - where "there are a small number of users and a large number of readers and the security groups are the more traditional SharePoint groups" and I cannot find an easy way. Any thoughts?

@Deleted great point on the "Modern UI". Our users want to use the modern UI and we are not using Office 365 Groups. Additionally, we have some users that like the Centered look of the Communications Sites. Not like the old days when we could choose the "Seattle or Oslo" Layout on the fly. You either have the left NAV or you don't.

 

@Susan Hanley the point I was trying to make earlier, I guess what I am trying to say is a "Communications site vs a Team Site" is all in how you use it not how it looks.

 

I would still love to convert my root site to a Communications Site using the "Communications Site Template".

I noticed something recently (not sure if this is new or not) but there is a way to hide the left navigation on a team site. In Site Settings > Look and Feel > Navigation Elements you can un-check Enable Quick Launch. This won't center your web parts on the page like the Comm Site page layout, but it will remove the Quick Launch. (It basically "pushes" the web parts to the left.) I know this isn't a perfect answer, but it might help.

I know that Microsoft has heard the message loud and clear that we would like to be able to use a Comm Site for the root site. I agree that the real difference between team site and comm site is intent and purpose (and the security model and services), not how it looks.

@Susan Hanley thank you again for the conversation - I did notice that, and it does work... but as you noted it just moves the web parts farther to the left. The "modern page" already leaves a large amount of unused real estate to the right already. Adjusting the layout of the page has become extremely deprecated - again no more Oslo or Seattle choice once, the site is created. Additionally, there is no choice to use the "Full Width" web part in the standard modern page.

 

What would be nice is if the page choice would consist of a "team page layout" or a "communications page layout" in the interim until we are allowed to have more control over the layout of the page - like centering the web parts...

 

It just currently seems that the new modern features enforce to many "ball and chain" type scenarios where you are forced to have less flexibility.

 

Hoping @Mark Kashman and team are working on this - maybe something in the works for #SPC18 - one can only hope.

Is this statement still true?

I am struggling with understanding where i can use the o365 connectors webpart and where i cannot.

My testing so far has yielded this:

New Connector webpart is seems to only be available in these 2 scenarios:

1. create a sharepoint modern team site from SHarePoint Landing Page

2. create a teams channel with associated team site.

 

Connector webpart does not show up when:

1. you create a modern team site from the new sharepoint admin console.

The Site must be Group connected to get those webparts. So communication sites will not work. However if you create a site from admin console you can later use the new PowerShell commands when they go live to convert them to Group connected sites, then you will be able to use those web parts.

That is quite confusing.
I am pretty sure that if i create a Modern Team Site from the NEW SP admin center (preview), it does create the site and a group. I have verified this.

what i don't understand is why the webparts aren't available.

What is the point of being able to create a Modern Team Site without an Office group? 

I just saw the mobile app update the shows the homepage of team site just like it does for communication sites. That helps. Thanks for that.

 

I really see a usecase for a Yammer / Communication site combo. For large audiences sites, we do not need nor want all the other Groups' services. Just a site and a place to discuss.

 

My current workaround is a PowerShell script that will use the same .csv format as Yammer wants to assign visitors access to the communication site.

Microsoft Ignite just announced the possibility of converting using PowerShell. In this case, they demonstrated converting the SharePoint Online Root site to a communication site: More info https://eschrader.com/2017/11/30/sharepoint-online-enable-new-modern-experience-on-root-site-collect...

It's been said this feature should be released at the end of 2018.

I also watched the very brief demo at Ignite.  If the PowerShell works for the root site are we to assume it will work for any existing team site?

That is my understanding. Until then you need to use the process posted by Marc https://sympmarc.com/2018/08/20/creating-a-modern-home-page-for-the-root-site-in-a-tenant/

@Susan HanleyExcept when a site has been created incorrectly, by mistake; or predates the release of Comms sites or... reasons

 

There is a need for this (I know, as we have it).

We are still having issues converting some root level sites (esp when we had publishing enabled). What is the work around? Can we just blow the current root site away and recreate a new one at the root level?

@Simon HudsonI would be very interested to know the answer as our root site was also created with publishing enabled.  

 

 

@Paul Mitchell The PowerShell script to convert the root site to a communication site is not yet released but as far as I know, it only works if you do not have publishing enabled on the root site.

If so it’s not the end of the world thou. There is a switch site feature coming so you can take any random comm site and set it as your root site collection.

@Chris Webb not a random site, it is a script to convert the legacy team site that is currently the root of older tenants to be a comm site. 

Check site swap section towards bottom of page: https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Updates-to-SharePoint-security-admi...

“SharePoint Site Swap (Coming Soon)
In addition to these improvements to the SharePoint admin center, we’re also introducing new Windows PowerShell cmdlet (invoke-spositeswap) that allows you to replace the root site within a tenant, e.g. https://contoso.sharepoint.comwith an existing site, such as https://contoso.sharepoint.com/sites/<site>.”
With that. You don’t have to use your root site collection even if you turned on that publishing by accident so you won’t be tied down by that restriction in putting modern site as your root.

Now if you have a big site with tons of content on it, it’ll be a bit more difficult but there will be a few more options than just converting the one that is there.

@Chris Webb Didn’t see that part. I can scenarios where I have been redirecting to a comm site where that will come in handy. Still wouldn’t recommend any old site, but if you have carefully curated and planned a great user experience, for sure! :)



 

@Chris Webb Didn’t see that part. I can scenarios where I have been redirecting to a comm site where that will come in handy. Still wouldn’t recommend any old site, but if you have carefully curated and planned a great user experience, for sure! :)


It’ll be nice for those of us that use a comm site now as a landing page etc. and instead of having to migrate to root we can just use the rename feature to swap it. Will be interesting how content works since it’s a swap you might not get the link redirecting.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
30 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies