PowerShell command Announced to move and replace SharePoint Sites, including the Root Site (!!!)

This email is for the direct recipient only and contains a link to activate your Yammer account. Wayne Ewington sent you a message. Hi All, Just to let you know that we have a new PowerShell cmdlet in the pipeline that will allow the SharePoint Tenant Admin to swap the location of a Site Collection with another Site Collection without deleting the original one. Or in other words… We are providing the ability to archive the Site Collection at https://<tenant>.sharepoint.com to https://<tenant>.sharepoint.com/sites/<ArchiveSite> and then move an existing Site Collection at https://<tenant>.sharepoint.com/sites/<NewRootSite> to https://<tenant>.sharepoint.com as a single action. Or in yet more other words… We are providing the ability to replace the existing root site with something shiny and new! We are also currently making this available for the tenants in the Early Preview group (which should be completed within the next 48 hours and hopefully sooner), so that you can start using this. Please note that this is still in early release so there are a few caveats and things that you need to be aware of: This is an early release and we still have some more work to do before making this generally available. After performing the swap, the target site can return an HTTP 404 error for about five minutes (until the caches are cleared). Searches indexes of the swapped sites will be stale until the content is recrawled. Anything dependent on "static" links (such as File Sync and OneNote files) will need to be manually corrected. We also have the following constraints in place (some of which we which we may remove shortly) as to what you can currently swap: Only Team Sites (STS#0), including Modern Team Sites (STS#3) and Communication Sites (SITEPAGEPUBLISHING#0) can be swapped. Only sites within the "Root", i.e. https://<tenant-name>.sharepoint.com can be swapped. Target site must be the Root site at https://<tenant-name>.sharepoint.com. Site cannot be "linked" to an Office 365 Group or a Hub Site. BTW we are planning to demo this at SPC NA (May 21 - 23) so if you keep this internally until then, then that would be fantastic. Anyway, to get started, you need to install version 16.0.8812.1200 (or later) of the Microsoft SharePoint Online Services Module for Windows PowerShell available from https://www.powershellgallery.com/packages/Microsoft.Online.… You can then use the following new PowerShell cmdlet: Invoke-SPOSiteSwap -SourceUrl "https://<tenant-name>.sharepoint.com/sites/<SiteName>" -TargetUrl "https://<tenant-name>.sharepoint.com" -ArchiveUrl "https://<tenant-name>.sharepoint.com/sites/<ArchiveSite>" Hopefully this is great news - We are certainly excited about this! Looking forward to getting your feedback and I'll also follow up with a survey in a few days time. Enjoy! Thanks, Wayne Ewington       Reply on Yammer     Microsoft Corporation | One Microsoft Way, Redmond, WA 98052, USA..