Advanced Data Residency in Microsoft 365
Overview of Advanced Data Residency
The Microsoft 365 Advanced Data Residency add-on ("ADR") provides eligible customers with expanded coverage of Microsoft 365 workloads and Customer Data, committed data residency for local country/region datacenter regions, and prioritized tenant migration services. With Advanced Data Residency, enterprise customers can best address their data residency compliance and tenant location requirements.
The following workloads are included in ADR. For more information, see:
- Exchange Online
- SharePoint Online and OneDrive for Business
- Microsoft Teams
- Microsoft Defender for Office P1 and Exchange Online Protection
- Office for the Web
- Viva Connections
- Viva Topics
- Microsoft Purview
Licensing and Purchase
The Advanced Data Residency ("ADR") add-on is intended for Microsoft 365 enterprise customers who have comprehensive data residency requirements. To be eligible to purchase ADR, customers must meet the following pre-requisites:
- The Tenant Default Geography must be one of the countries/regions included in the Local Region Geography (Australia, Brazil, Canada, France, Germany, India, Japan, Poland, Qatar, South Korea, Norway, South Africa, Sweden, Switzerland, United Arab Emirates, and United Kingdom).
- Customers must have licensed one or more of the following products:
- Microsoft 365 F1, F3, E3, or E5
- Office 365 F3, E1, E3, or E5
- Exchange Online Plan 1 or Plan 2
- OneDrive for Business Plan 1 or Plan 2
- SharePoint Online Plan 1 or Plan 2
- M365 Business Basic, Standard or Premium
Geographic availability will be updated as available.
Customers must cover 100% of paid seats in the tenant above with ADR add-on license for tenant to receive data residency for ADR workloads. See the table below for an example. See the table below for an example.
|ADR-related SKU||Available Seats||Allocated Seats||ADR Required Seats|
|Office 365 E3||200||125||200|
|Microsoft 365 F1||1420||1100||1420|
|Exchange Online Plan 2||25||22||25|
1: If you have 1645 seats purchased for ADR then you have a data residency commitment for your Local Region Geography. If you have less than 1645 seats then you do NOT have a data residency commitment and your tenant is subject to being moved out of the Local Region Geography.
Customers who have purchased Multi-Geo seats for their tenant do not have to also pay for ADR for the same seats. This is to avoid “double licensing” a single seat for two different data residency programs. For example, if a customer would normally require 15,000 ADR seats to satisfy the program requirements, but they also have 4,000 Multi-Geo seats, then they are only required to purchase 11,000 ADR seats as the two programs combined would cover the normal ADR program requirement of 100% user coverage.
To find out how many ADR seats you need go to Tenant Admin Center - Billing - Your Products within your tenant and add up the total Purchase Quantity for all ADR-eligible SKUs to get the proper total of ADR seats required.
Tenants with a mix of Commercial and Education subscriptions:
When a customer has a mix of commercial and education license types including both Commercial/Public Sector (for example, E3, E5) and Education (for example, A1, A3, etc.) licenses in their subscription, the following applies:
Customers have rights to purchase full ADR add-on for only the paid portion of Microsoft 365 SKUs and are not obligated to cover free subscription types. However, they must cover the paid education seats with ADR (Microsoft 365 A3/A5, Office 365 A3/A5 student or faculty).
ADR for Education products is only available to Volume Licensing / EES (Microsoft Enrollment for Education Solutions) customers; contact your Microsoft account representative for details on how to obtain an ADR Education related SKU.
Data Migration Management
If all of a customer's tenant data covered by the Advanced Data Residency feature isn't already stored at rest within their eligible Local Region Geography, then a data migration to the Local Region Geography will be required. If customer tenant data covered by the Advanced Data Residency feature is already stored at rest within their eligible Local Region Geography, then no data migration to the Local Region Geography will be required.
Starting Data Migration
After a customer has received their Advanced Data Residency licenses, the customer will need to signal that they are ready to schedule data migration, if one is necessary. To signal your tenant is ready for its data migration, the customer administrator will visit the Data Location section of the Microsoft 365 Admin Console within the Settings -> Org Settings -> Organization Profile area. From here the customer administrator will be able to see the current location of their data-at-rest and what Local Region Geography their customer data will be migrated to, Please Note: Data migration will not be scheduled until the customer administrator has executed this task. Further, the migration expectation discussed elsewhere in this documentation won't start being tracked until this task has been executed by the customer administrator.
Once the customer signal is received, they'll be provided with their opt-in date and the target date of completion.
In addition to a notification posted to the Message Center upon completion, the Data Location section in the Microsoft 365 Admin Console will also be updated as each workload requiring a data migration is complete.
Microsoft will use reasonable efforts to try to complete an Advanced Data Residency add-on customer migration within twelve (12) months from the time the customer administrator has signaled they're ready for migration. However, Microsoft may not be able to complete the migration within this timeframe for all customers. For example, larger or more complex customers or situations outside of Microsoft's control may require additional time to complete the migration. Advanced Data Residency add-on customers also receive prioritized migration services for their tenants over the legacy Move Program migration option. These migration expectations also apply to all ADR EDU customers as well. Customers utilizing the legacy Move Program for a data migration who don't have the Advanced Data Residency feature, will instead follow Legacy Move Program Migration Expectations.
Data moves are a back-end service operation with minimal impact to end-users. We adhere to the Microsoft Online Services Service Level Agreement (SLA) for availability so there's nothing that customers need to prepare for or to monitor during the move. Notification of any service maintenance is done if needed.
During and After your Migration
Data moves are a back-end operation with minimal if any impact to end users. No action is required while Microsoft moves each service and associated customer data for your tenant to the applicable geography.
Moves occur at different times for each service. As a result, you'll see the described below on reduced functionality for each service happen at different times.
Watch the Microsoft 365 Message Center for confirmation when moves for each workload service is complete.
Impact on End Users and Workloads
Data moves are a back-end service operation with minimal impact to end-users. Features that can be impacted are listed on the During and after your data move page. We adhere to the Microsoft Online Services Service Level Agreement (SLA) for availability so there's nothing that customers need to prepare for or to monitor during the move. Notification of any service maintenance is done if needed.
Because of the complex nature of the hundreds of services (both standard and customizable) that are available within the many workloads that customers sign up for and use within a typical E3 or E5 license, the migration of customer data from one data center to another could cause minor disruption and/or temporary unavailability of certain services customers use. See the migration sections of each workload in the Workload Data Residency Capabilities section for more information.
For customers requiring a data migration, they may monitor the Message Center for updates to be provided as each workload completes its data migration. The Data Location section in the Microsoft 365 Admin Console may also be referenced to see if a workload has completed its migration. Due to the nature of how migrations work, there's no granular status provided to indicate just how close to completion a migration may be.