06-28-2017 02:12 AM
06-28-2017 02:12 AM
Will it be possible to change the tenant root site collection into a Communication Site? It seems to be the perfect spot for a new companywide site/intranet that could benefit highly from the new features.
It would be nice for users to set a SharePoint site as the landing page after login, currently only a fixed set of locations are possible but not a specific SharePoint sitecollection. Any plans for this?
06-28-2017 06:54 AM
06-28-2017 07:10 AM
I imagine this make for an interesting debate going forward! Lots of organizations still are looking for the classic traditional intranet experience with a News/publishing homepage experience and then a nicely organized collection of sites/pages to share and publish corporate assets. The new Communications Site will push people to rethink if they want a traditional expeirence or instead if they want to try using the Communications Site as the root intranet and then have navigation that takes employees to other content areas (sub-sites) or other site collections as microsites. Interestingly, the larger the organization, the harder it is to have one giant intranet that perfectly caputres everything and the reality is there is a large ecosystem of sites that contain critical information, assets and applications for employees.
06-28-2017 08:20 AM
07-20-2017 02:44 AM
This is something I am eagerly awaiting for! I need to update our root site, and don't want to have to do it twice - once now, and then again when I can convert to communication site
07-21-2017 06:26 AM
07-29-2017 04:41 PM
Just imagine being able to set a SharePoint communcation site as the Office 365 landing page, then being able to add this app launcher as a single modern webpart:
Would be a great tool for us to introduce and push SharePoint to our O365 customer
07-29-2017 11:51 PM
01-25-2018 06:36 AM
There's a Uservoice request for this. Please can I encourage as many people as possible to cast their vote to bump it up the the agenda with the Microsoft Developers https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/20308864-set-comm... This is a really important feature for many of us who want to embrace the new Communication sites .
08-31-2018 01:48 AM
08-31-2018 01:48 AM
I have a classic root in a government space that cannot be changed. I can build communication site collections off that root. So “https://******.sharepoint.com/sites/home” is created as a communication site and much more attractive than building a modern page off the root of a classic site. We have several other communication sites with that same look for branding/navigation consistency. One of the communication sites is a redesign of the homepage. So now I want that communication redesign to be the root at “https://******.sharepoint.com” without latency on the redirect.
For more information, I just opened a question here:
Any help would be much appreciated!
09-27-2018 10:55 AMSolution
12-12-2018 03:56 PM
Love the excitement around this feature. We've identified a few issues and are working hard to get this out to everyone ASAP. We are now targeting Q1 CY2019 timeframe for roll out.
Thank you !
01-30-2019 08:49 AM
I was looking on the roadmap and I don't see this on it, then again I may just be missing it. I know for our org, this is a top priority, so is there any more of an update on the progress for updating the root site collection?
I know, Q1 CY2019 still has quite a few days left in it, but I am so excited by this, it will go a long way of helping us get the rest of the company using SharePoint more.
01-30-2019 09:06 AM - edited 01-30-2019 09:17 AM
If you want to change anything on the rootsite you can use ‘https://<TenantName>.sharepoint.com/SitePages/Forms/AllPages.aspx’
or wait for other great releases like the modern mega menu Navigation ;)
02-19-2019 08:06 AM
@DC Padur wrote:
We've just announced that we will be supporting this, in a limited scope, by end of this year. Please check out this blog post https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Build-your-modern-intranet-with-Sha... and this tweet thread: https://twitter.com/dcpadur/status/1044954711349055490
@DC Padur any updates? This is truly needed to be able to make a transition of our and others intranets instead of migrating content. Pls advise!
04-26-2019 08:15 AM
The feature took longer than expected to ship. We are just a couple of weeks away from starting the roll out. Please see https://twitter.com/dcpadur/status/1118367712177205248
05-09-2019 07:30 AM
I can notice the documentation mentions a current restriction around sites where the classic publishing feature has been enabled.
Typically, we have enabled the feature. Does anybody know if this limitation is here to stay? I assume the PowerShell will just not work for sites where the feature was previously enabled?
05-10-2019 09:05 PM
Yes. That limitation is not going away in the near future. There is another feature we've announced that would let you move an existing comm site to the root location of the tenant. See this: https://www.microsoft.com/en-us/microsoft-365/roadmap?featureid=51259
05-13-2019 03:56 AM
Thank you for the link to the new feature.
Do you know what would happen to the sub-sites if we moved an existing comms site to the root location? Currently we have a ‘classic’ root site and a number of ‘modern’ sub-sites.
05-16-2019 12:05 PM
@DC Padur thx for the update. Which way would you go about with getting a modern site as the root site? I.e would you convert the current one or would you change a modern communication site to be the root? Are there any caveats to have in mind?
06-05-2019 08:24 AM
@DC Padur I saw in the roadmap that it's being pushed back to Q4?
There are a ton of development projects that we have been keeping on the back burner waiting for this. I know there was a ton of excitement regarding Home sites, but I know for us, implementing Home sites without having the root as a Communications site is going to slow down our development and use of SharePoint.
06-10-2019 04:55 PM
@Jens Balondo I know this might be a simple question, however now that I have implemented your change what is the easiest way to get to the Root site of the tenant again in the event I need to make changes to this site and/or change the 'Link to a document' URL? BTW, thank you for this solutions, as it is a very simple solution to the root site not being converted to a communications site problem.
06-10-2019 04:57 PM
07-08-2019 09:29 AM
I'm currently trying to do our Intranet architecture for O365 and want to have a communication site as the root site. I've created one and want to make this my root site. We have several other sites already under the old classic root site so need to know when we will be able to have this capability.
07-15-2019 07:27 AM
There is a feature in the Microsoft Office 365 roadmap to convert a tenant home site to a communications site. It is targeted to be released at the end of this year. See https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=46338. I imagine it will be demo'd at Ignite.
10-21-2019 05:53 PM
The site-swap code which allows an existing Communication site to be moved to the tenant root is apparently rolling out now to tenants with between 1,000 - 10,000 licences. See O365 Message centre message MC189866 dated September 6 2019 and is meant to be completed worldwide by end of October.
Unfortunately, I haven't been able to find any information on how we can tell whether the code is available in our tenant, apart from attempting to implement the code. This is not something I want to do, I have to put this type of change through my organisation's change management processes, communicate to users about upcoming change etc.
Perhaps I've missed a message somewhere.
Has anyone else found any articles on how we can tell whether the Powershell cmdlet Invoke-SPOSiteSwap will work in our tenant without having to give it a try?
11-06-2019 02:39 PM
@Mary F Harvey thanks for the info. I have tried several times recently to do the Site Swap but I get the message that it's not available for my tenant as of yet. Our licensing is >10K. I don't understand why this isn't being rolled out to everyone. This is a MAJOR deal. The whole thing with O365 is this modern experience and to not be able to have the root site be set as a Modern site to start building off of it is painful and hard to plan for when MS doesn't even have a plan for implementation of this feature for large clients.
11-07-2019 03:15 PM
Hi @Anne Kelley, Size of a tenant does not determine when updates are applied, but rather when the infrastructure that hosts your tenant and others is scheduled to be updated. However, I would have thought this would have been deployed to almost everyone by now. You might want to open a support ticket and see if you can find out if there is any issue with the update to your tenant.
by Suolon Hu on June 28, 2017
by Michael Böhm on June 28, 2017
by Bogdan Mocanu on June 28, 2017
by Cathy Dew on May 21, 2020
by Mark Kashman on May 19, 2020