Move a SharePoint site to a different geo location
With SharePoint site geo move, you can move SharePoint sites to other geo locations within your multi-geo environment.
The following types of site can be moved between geo locations:
- Microsoft 365 group-connected sites, including those sites associated with Microsoft Teams
- Modern sites without a Microsoft 365 group association
- Classic SharePoint sites
- Communication sites
You must be a Global Administrator or SharePoint Administrator to move a site between geo locations.
There is a read-only window during the SharePoint site geo move of approximately 4-6 hours, depending on site-contents.
- Try a SharePoint site move on a test site to get familiar with the procedure.
- Validate whether the site can be moved prior to scheduling or performing the move.
- When possible schedule cross-geo sites moves for outside business hours to reduce user impact.
- Communicate with impacted users prior to the sites move.
Communicating to your users
When moving SharePoint sites between geo locations, it's important to communicate to the sites' users (generally anyone with the ability to edit the site) what to expect. This can help reduce user confusion and calls to your help desk. Email your sites' users before the move and let them know the following information:
- When the move is expected to start and how long it is expected to take
- What geo location their site is moving to, and the URL to access the new location
- They should close their files and not make edits during the move.
- File permissions and sharing will not change because of the move.
- What to expect from the user experience in a multi-geo environment
Be sure to send your sites' users an email when the move has successfully completed informing them that they can resume working on their sites.
Scheduling SharePoint site moves
You can schedule SharePoint site moves in advance (described later in this article). You can schedule moves as follows:
- You can schedule up to 4,000 moves at a time.
- As the moves begin, you can schedule more, with a maximum of 4,000 pending moves in the queue and any given time.
- The maximum size of a SharePoint site that can be moved is 2 terabytes (2 TB).
To schedule a SharePoint site geo move for a later time, include one of the following parameters when you start the move:
PreferredMoveBeginDate– The move will likely begin at this specified time.
PreferredMoveEndDate– The move will likely be completed by this specified time, on a best effort basis.
Time must be specified in Coordinated Universal Time (UTC) for both parameters.
Moving the site
SharePoint site geo move requires that you connect and perform the move from the SharePoint Admin URL in the geo location where the site is.
For example, if the site URL is
https://contosohealthcare.sharepoint.com/sites/Turbines, connect to the SharePoint Admin URL at
Connect-SPOService -Url https://contosohealthcare-admin.sharepoint.com
Validating the environment
We recommend that before scheduling any site move, you perform a validation to ensure that the site can be moved.
We do not support moving sites with:
- Business Connectivity Services
- InfoPath forms
- Information Rights Management (IRM) templates applied
To ensure all geo locations are compatible, run
Get-SPOGeoMoveCrossCompatibilityStatus. This will display all your geo locations and whether the environment is compatible with the destination geo location. If a geo location is incompatible, that means an update is in progress in that location. Try again in a few days.
To perform a validation-only check on your site, use
Start-SPOSiteContentMove with the
-ValidationOnly parameter to validate if the site is able to be moved. For example:
Start-SPOSiteContentMove -SourceSiteUrl <SourceSiteUrl> -ValidationOnly -DestinationDataLocation <DestinationLocation>
This will return Success if the site is ready to be moved or Fail if any of blocked conditions are present.
Start a SharePoint site geo move for a site with no associated Microsoft 365 group
By default, initial URL for the site will change to the URL of the destination geo location. For example:
For sites with no Microsoft 365 group association, you can also rename the site by using the
-DestinationUrl parameter. For example:
To start the site move, run:
Start-SPOSiteContentMove -SourceSiteUrl <siteURL> -DestinationDataLocation <DestinationDataLocation> -DestinationUrl <DestinationSiteURL>
Start a SharePoint site geo move for a Microsoft 365 group-connected site
To move a Microsoft 365 group-connected site, the Global Administrator or SharePoint Administrator must first change the Preferred Data Location (PDL) attribute for the Microsoft 365 group.
To set the PDL for a Microsoft 365 group:
Set-SPOUnifiedGroup -PreferredDataLocation <PDL> -GroupAlias <GroupAlias> Get-SPOUnifiedGroup -GroupAlias <GroupAlias>
Once you have updated the PDL, you can start the site move:
Start-SPOUnifiedGroupMove -GroupAlias <GroupAlias> -DestinationDataLocation <DestinationDataLocation>
Cancel a SharePoint site geo move
You can stop a SharePoint site geo move, provided the move is not in progress or completed by using the
Determining the status of a SharePoint site geo move
You can determine the status of a site move in our out of the geo that you are connected to by using the following cmdlets:
- Get-SPOSiteContentMoveState (non-Group-connected sites)
- Get-SPOUnifiedGroupMoveState (Group-connected sites)
-SourceSiteUrl parameter to specify the site for which you want to see move status.
The move statuses are described in the following table.
|Ready to Trigger||The move has not started.|
|Scheduled||The move is in queue but has not yet started.|
|InProgress (n/4)||The move is in progress in one of the following states: Validation (1/4), Back up (2/4), Restore (3/4), Cleanup (4/4).|
|Success||The move has completed successfully.|
|Failed||The move failed.|
You can also apply the
-Verbose option to see additional information about the move.
Site users should notice minimal disruption when their site is moved to a different geo location. Aside from a brief read-only state during the move, existing links and permissions will continue to work as expected once the move is completed.
While the move is in progress, the site is set to read-only. Once the move is completed, the user is directed to the new site in the new geo location when they click on bookmarks or other links to the site.
Users with permissions to site will continue to have access to the site during the move and after it's complete.
The sync app will automatically detect and seamlessly transfer syncing to the new site location once the site move is complete. The user does not need to sign in again or take any other action. (Version 17.3.6943.0625 or later of the sync app required.)
If a user updates a file while the move is in progress, the sync app will notify them that file uploads are pending while the move is underway.
When the SharePoint site geo move completes, the existing shared links for the files that were moved will automatically redirect to the new geo location.
Most Recently Used files in Office (MRU)
The MRU service is updated with the site url and its content URLs once the move completes. This applies to Word, Excel, and PowerPoint.
OneNote win32 client and UWP (Universal) App will automatically detect and seamlessly sync notebooks to the new site location once site move is complete. The user does not need to sign in again or take any other action. The only visible indicator to the user is notebook sync would fail when site move is in progress. This experience is available on the following OneNote client versions:
- OneNote win32 – Version 16.0.8326.2096 (and later)
- OneNote UWP – Version 16.0.8431.1006 (and later)
- OneNote Mobile App – Version 16.0.8431.1011 (and later)
Teams (applicable to Microsoft 365 group connected sites)
When the SharePoint site geo move completes, users will have access to their Microsoft 365 group site files on the Teams app. Additionally, files shared via Teams chat from their site prior to geo move will continue to work after move is complete.
SharePoint site geo move does not support moving Private Channels from one geo to another. Private channels remain in the original geo.
SharePoint Mobile App (iOS/Android)
The SharePoint Mobile App is cross geo compatible and able to detect the site's new geo location.
SharePoint 2013 workflows have to be republished after the site move. SharePoint 2010 workflows should continue to function normally.
If you are moving a site with apps, you must reinstantiate the app in the site's new geo location as the app and its connections may not be available in the destination geo location.
In most cases, Power Automate Flows will continue to work after a SharePoint site geo move. We recommend that you test them once the move has completed.
Power Apps needs to be recreated in the destination location.
Data movement between geo locations
SharePoint uses Azure Blob Storage for its content, while the metadata associated with sites and its files is stored within SharePoint. After the site is moved from its source geo location to its destination geo location, the service will also move its associated Blob Storage. Blob Storage moves complete in approximately 40 days. This will not have any impact to users interaction with the data.
You can check the Blob Storage move status using the Get-SPOCrossGeoMoveReport cmdlet.
Submit and view feedback for