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
AdminSharePoint Experiences Team
(spexcustomerengagement@service.microsoft.com, Microsoft SharePoint)
responded
This was just demoed at Ignite 2018 session BRK2136. Read more about it : https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Build-your-modern-intranet-with-SharePoint-in-Office-365-Ignite/ba-p/255453
38 comments
-
Chris Smith commented
Still need an update on this please, or hopefully can just be released soon! Thanks!
-
Matt Hong
commented
If I have a Classic Publishing root site today with various subsites, what happens to those subsite when we run the CommSite PowerShell cmdlet? Do those stay as they are, or are those deleted?
-
Anonymous
commented
Any update one when this is going live?
-
This is awesome, now just need the Enable-CommSite cmdlet to work for me!
-
jg
commented
I found a solution to this issue and I am so happy about it. Microsoft also provided some updates on the ignite that occurred this week.
-
Jenkins NS
commented
@Redjesh Behari
Enable-CommSite -Url https://tenant-admin.sharepoint.com -
Redjesh Behari
commented
so what are those commands anyone? The session is not on demand
-
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!