Feedback by UserVoice

I suggest you ....

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

1,013 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Con shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • Markus commented  ·   ·  Flag as inappropriate

    Update please. Can this be expected within the next few weeks or are we talking months?

  • Anonymous commented  ·   ·  Flag as inappropriate

    When is this feature going to be released ? I still can not use it in my tenant.

  • Stephen Kowalski commented  ·   ·  Flag as inappropriate

    Microsoft really needs better communication around the release of key features. This is a critical feature required for many updates or launches of Intranets. Telling my boss, "Microsoft said, 'soon', so it could be tomorrow, or next year, or maybe never!" isn't great.

  • GanL commented  ·   ·  Flag as inappropriate

    will this be released to the tenants in NA soon ? what is the release timeline?

  • Max Goss commented  ·   ·  Flag as inappropriate

    Hi guys, can you let us know when this will hit general availability? We are particularly interested in the search across org scope which seems to be available by default at the root site level whereas other site collections are scoped to site collection search by default. I think this is a key feature for Intranets based on modern SharePoint architecture. Any update would be appreciated.

  • Chris Smith commented  ·   ·  Flag as inappropriate

    Still need an update on this please, or hopefully can just be released soon! Thanks!

  • Matt Hong commented  ·   ·  Flag as inappropriate

    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?

  • jg commented  ·   ·  Flag as inappropriate

    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.

  • Ciprian commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

Feedback and Knowledge Base