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)
  • Grant commented  ·   ·  Flag as inappropriate

    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.

  • Simon Hudson commented  ·   ·  Flag as inappropriate

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

    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).

  • Chris Webb commented  ·   ·  Flag as inappropriate

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

    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...

  • Ciprian commented  ·   ·  Flag as inappropriate

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

    It would also be good to be able to create Communication sites under the "sites" path and not just under the "teams" path.

  • Anonymous commented  ·   ·  Flag as inappropriate

    I am very interested in when the root site can become a modern communication site, and how to minimize impact on existing content/site structure

  • Anonymous commented  ·   ·  Flag as inappropriate

    Agreed. We need this option right away. Quick launch bar on the left is a waste of space since we already have navigation on top. Also, Comm site look much more sleeker and professional for your home page. Teams and department´s pages can use the team site template.

  • Joel Chmiel commented  ·   ·  Flag as inappropriate

    To be honest, I cannot understand why this wasn't in the first release? Assuming we're all moving to modern, does a team site with site pages make sense as the root for mid to large sized organizations? Is there some other plan for the root site if not a Communication Site in the Modern world? If not, we need this feature right away! My humble opinion, SharePoint team, you need to provide a story around the purpose for the root site if the vision is not for it to be a Communication Site. The root site is the first step in a planned migration to modern, and I don't have a validated direction to give to our leadership.

Feedback and Knowledge Base