Set "Communication Site" as Root site collection
For organisations that would like to use Communication site as their intranet it would be great if you could provision the root site as a Communication site, rather than a team site with a redirect to the communication site.
There is a workaround as mentioned here but i'd prefer a Microsoft supported method https://hangconsult.com/2017/06/29/change-sharepoint-online-root-site-collection-to-use-the-new-communication-site-template/
Con
shared this idea
You can now enable communication site experience at the classic root site with http://spo.ms/enablecommsite or swap a new communication site to the root with http://aka.ms/siteswap
71 comments
Comments are closed-
Fady Sharobeem
commented
Hello Microsoft, any updates on this. You have been thinking for a while.
-
Ciprian
commented
Hey Microsoft, any updates on this? You've been thinking about it for more than a year. I mean, this is a pretty basic requirement urgently needed by any company with an intranet.
-
Chris Helsby
commented
The ability to have the root site and indeed create communication sites within the /sites/ managed path via Powershell and Central administration is very important. Self-service site creation is still not viable for many intranets.
-
Phil
commented
Need this please!
-
Srrinath
commented
Yes, please..
-
Grant
commented
Ideally a Communication site, but even a Modern Team Site (without associated o365 group) would be ok.
Still think it's crazy that you can't do this - would have thought that the root site collection would have been the first one to allow for the Modern Sites as it's almost every tenant's landing page.
-
Fschick
commented
Please. Do. This.
-
Simon Hudson
commented
It's a key requirement that the top level Site Collection can act as a full Communications Site. It seems like this is the most obvious use of Comms sites.
Failing that there needs to be a simple way to redirect the root directly to a chosen Home Page on a Comms site -
Graham Potter
commented
This should be seen as a critical fix. You can already make a top level site collection a HUB, and so it makes total sense that we at least have the option to have the root site collection be based off a truly modern communications site (or any other modern site).
-
Prakash
commented
BIG YESS
-
Anonymous
commented
YES PLEASE
-
Anonymous
commented
I Need This!
-
Dr. Sushi
commented
Can't agree more, Spot on!
-
Chris Webb
commented
Here is the slide, later in 2018 "Select nav location" Basically setting this to top will give you Comm site look and feel of standard Team sites.
-
Chris Webb
commented
This option was on the slides for coming to SHarePoint in the design sessions at SPC. They are adding the comm site template as an option.
-
Marcel
commented
We definitely want a modern Communications site as root site too.
The only alternative is to buy/develop a custom theme, but that may break with future O365 developments. Getting OOTB functionality is our main reason to move to O365...
-
Jason Keys
commented
This was a First Release option in 2016? 45% through 2018 now.
-
Ciprian
commented
This is such a must. Especially for large intranets that benefit from full width landing pages. Like Joel said earlier, Comms template should have been the default, makes no sense to make the Team template as default for root, no sense at all.
-
Anonymous
commented
It would also be good to be able to create Communication sites under the "sites" path and not just under the "teams" path.
-
Thomas Baklund
commented
This should most def happen!
