During and after your data move


Applies to: Office 365

Topic Last Modified: 2017-02-24

Data moves are a back-end operation with minimal impact to end-users. No action is required while Microsoft moves each service and associated data for your tenant to a new datacenter region. Data transfer and validation occur in the background in advance with minimal impact to users.

Moves occur at different times for each service. As a result, you'll see the described reduced functionality for each service at a different time.

Watch the Office 365 Message Center for confirmation when moves for each of Exchange Online, SharePoint Online, and Skype for Business are complete. As shown in the table below, it can take up to 24 months, after the end of the enrollment period, to complete all the requested data moves for all customers in a specific region. If you see any issues with your tenant after the move, contact Office 365 Support to get assistance.


Customers with billing address in

All moves completed by


October 31, 2018

Australia, New Zealand, Fiji

October 31, 2017


October 31, 2018


October 31, 2018

United Kingdom

To be determined

South Korea

To be determined

Because it takes time to move each user to the new datacenter region for a single tenant, some users will still be in the old datacenter region during the move, while others will be in the new datacenter region. This means that some features that involve accessing multiple mailboxes won't fully work during a period of the move process, which can last weeks. These features are described in the following sections.

When an individual mailbox moves crosses datacenter regions, the mailbox content is first pre-staged so that existing data is copied to the target region without affecting the mailbox. At the time of cutover to the target region, the mailbox in the source region is locked for a few minutes. During that time, email clients can't connect temporarily. Any additional changes are copied to the target region, and then the mailbox completes the move to the target region. There is no disruption to mail flow during the move.

Some users may need to restart Outlook Desktop after the mailbox is moved as described in Knowledge Base article 2591913.

A user with "Full Access" permission to shared mailboxes isn't affected during the move.

A user who needs to manage resource mailbox configurations via the Options page in Outlook Web Access can continue to do so during the move.

If the resource mailboxes are managed directly via Exchange cmdlets, the cmdlets Set-MailboxRegionalConfiguration and Set-MailboxCalendarConfiguration don’t work if the executing user and the resource mailbox are in different regions.

Free/Busy and calendar sharing aren't affected during the tenant move. User A with write permission to the calendar folder of Mailbox B can still manage Mailbox B's calendar folder using Outlook Desktop. However, during the move, if User A and Mailbox B aren't in the same region, User A can't edit Mailbox B's calendar in Outlook Web Access until both are moved to the target region.

Some users open a shared mail folder from another mailbox (that the user has read or write permissions to) in Outlook Web Access using the “Shared Folder” feature. The following table describes how access to shared folders works during a mailbox move.




User has mailbox folder permission to another mailbox

If User A and Mailbox B aren't in the same region during the tenant move, User A can't open Mailbox B's folder in Outlook Web Access if User A only has permission to a specific folder in Mailbox B.

To add a shared folder, right-click the user name in the left navigation panel and select Add shared folder.

User with full mailbox permission to another mailbox

If User A has "Full Access" permission to Mailbox B, then User A can click the shared folder in the left navigation panel in Outlook Web Access to open a window showing Mailbox B.

If the public folder mailbox is temporarily in a different datacenter region from the user trying to access it, the user can't access it.

The eDiscovery and auditing features in the Office 365 Security & Compliance Center support cross-region tenant moves. unlike the Exchange admin center (EAC), which doesn't support querying users who aren't yet moved once the tenant move has started. For more information about the Security & Compliance Center, see Office 365 Security & Compliance Center.

The following table shows you how to access eDiscovery and auditing via the EAC and the Security & Compliance Center.


 Exchange admin centerSecurity & Compliance Center


  1. Go to https://portal.office.com, and then click the Admin tile.

  2. Click Admin centers > Exchange.

  3. Select compliance management > in-place eDiscovery & hold.

  1. Go to https://portal.office.com, and then click the Admin tile.

  2. Click Admin centers > Security & Compliance.

  3. Select Search & investigation > eDiscovery.


  1. Go to https://portal.office.com, and then click the Admin tile.

  2. Click Admin centers > Exchange.

  3. Select compliance management > auditing.

  1. Go to https://portal.office.com, and then click the Admin tile.

  2. Click Admin centers > Security & Compliance.

  3. Select Search & investigation > Audit log search.

When a tenant is moving between regions, a migration batch may report errors on some users in the migration batch who are left behind in the source region. In this case, remove the existing migration batch to remove the underlying sync request. After the batch is fully cleaned up, create the batch again, which will start creating sync requests in the target region.

When SharePoint Online is moved, data for the following services is also moved:

  • One Drive for Business

  • Project Online

  • Project for Office 365

  • Office 365 Video services

  • Office Online

  • Office 365 ProPlus

  • Visio Pro for Office 365

After the completion of your SharePoint Online move, you may see the following effects:

  • Office 365 Video Services

    • The data move for video takes longer than the moves for the rest of your content in SharePoint Online.

    • After the SharePoint Online content is moved, there will be a time frame when videos aren’t able to be played.

    • We're removing the trans-coded copies from the previous datacenter and transcoding them again in the new datacenter.

  • Your search index is automatically re-crawled and the Office Graph is rebuilt. In most cases this will take 24 to 48 hours. During this period, you'll still be able to use search features, but the following features will have reduced functionality:

    • Search results and Search Web Parts: Items that haven't been re-crawled will not be shown.

    • Delve: Items that haven't been re-crawled will not be shown. Content will look different until the Office Graph has been rebuilt; however, this will improve as users interact with items across Office 365.

    • eDiscovery: Items that haven't been re-crawled will not be shown.

    • Data Loss Protection (DLP): Policies will not be enforced on items that haven't been re-crawled.

    • When search index crawling has finished, freshness and relevancy of the features listed above will be consistent with prior to your datacenter move.

All users will be signed out from the Skype for Business client software during cut-over. The automatic sign-in will reconnect users within two minutes.


Features that work during entire move Features that may be limited during a portion of the move
  • Instant messaging and voice calls

  • Users can add contacts, add contact groups, add meetings, set their location, and change "What's Happening Today".

  • Audio Conferencing Provider (ACP) settings are copied to the target datacenter region. If the ACP provider is present in the target datacenter, it will work. Otherwise, it will not.

  • Tenant Admin TRPS (Tenant Remote PowerShell) will not be available for administrators to create sessions.

  • Tenant administrator LAC will not be available for administrators to sign in and change user settings.


After the move
  • Meeting data (uploaded presentations, etc.) will not move and will need to be re-uploaded.

  • Older Lync clients, such as the Lync 2010 client and Lync for Mac 2011 client, are known to cache DNS information to the service causing sign-in issues. Clearing the DNS cache may be required if the user is not on the latest Skype for Business Windows client. Ask users to run the troubleshooting wizard and follow directions on how to clear the client cache. Lync for Mac client users should follow these instructions.

We only move customer data for Exchange Online, SharePoint Online, and Skype for Business. We do not move data for other services. There is no change or impact to you as a customer or user of these other services. The move process does not influence them, and the location of their customer data remains unchanged.