You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-365/enterprise/advanced-data-residency.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,23 +46,20 @@ The following workloads are included in ADR. For more information, see:
46
46
> [!NOTE]
47
47
> *The Microsoft Purview services list mentioned above includes all services covered as part of the Advanced Data Residency commitment as of November 2024. Additional Microsoft Purview services are not currently supported.
48
48
49
-
> [!NOTE]
50
-
> Viva Topics has been retired as of February 22, 2025. Therefore, Viva Topics is no longer a supported workload in ADR. For more details, please visit [aka.ms/TopicsFebSupport](https://aka.ms/TopicsFebSupport).
51
-
52
49
## Licensing and Purchase
53
50
54
51
### Eligibility
55
52
56
53
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 prerequisites:
57
54
58
-
- The _Tenant__Default Geography_ must be one of the countries or regions included in the _Local Region Geography_: Australia, Brazil, Canada, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mexico, New Zealand, Norway, Poland, Qatar, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, United Arab Emirates, and United Kingdom.
55
+
- The _Tenant__Default Geography_ must be one of the countries or regions included in the _Local Region Geography_: Australia, Brazil, Canada, Chile, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mexico, New Zealand, Norway, Poland, Qatar, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, United Arab Emirates, and United Kingdom.
59
56
- Customers must have licenses for one or more of the following products:
60
57
- Microsoft 365 F1, F3, E3, or E5 (including SKUs without Microsoft Teams)
61
58
- Office 365 F3, E1, E3, or E5 (including SKUs without Microsoft Teams)
62
59
- Exchange Online Plan 1 or Plan 2
63
60
- OneDrive Plan 1 or Plan 2
64
61
- SharePoint Plan 1 or Plan 2
65
-
- Microsoft 365 Business Basic, Standard or Premium (including SKUs without Microsoft Teams)
62
+
- Microsoft 365 Business Basic, Standard, or Premium (including SKUs without Microsoft Teams)
66
63
- Microsoft Teams Enterprise, EEA, or Essentials
67
64
68
65
Geographic availability is updated as available.
@@ -84,7 +81,7 @@ To find out how many ADR licenses, you need go to the Microsoft 365 admin center
84
81
85
82
### Tenants with a mix of Commercial and Education subscriptions
86
83
87
-
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:
84
+
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) licenses in their subscription, the following applies:
88
85
89
86
- Customers have rights to purchase full ADR add-on for only the paid portion of Microsoft 365 SKUs and aren't obligated to cover free subscription types. However, they must cover the paid education licenses with ADR (Microsoft 365 A3/A5, Office 365 A3/A5 student or faculty).
90
87
@@ -123,13 +120,13 @@ The "Data location" section in the Microsoft 365 admin center (referenced in the
123
120
124
121
Microsoft adheres to the [Microsoft Online Services Service Level Agreement (SLA)](https://go.microsoft.com/fwlink/p/?LinkId=523897) for service availability and uses reasonable efforts to complete an Advanced Data Residency add-on customer data migration within 12 months from the time the customer administrator selects the option to initiate migration. However, large, complex customers, and situations outside of Microsoft's control, may require more time for migration to complete.
125
122
126
-
Data moves are a back-end service operation with minimal impact to a customer's operations. For information related to specific workloads, customer administrators can refer to the “Migration” sections in the following Workload Data Residency Capabilities pages: [Exchange Online](m365-dr-workload-exo.md#migration), [SharePoint and OneDrive](m365-dr-workload-spo.md#migration-with-advanced-data-residency), [Microsoft Teams](m365-dr-workload-teams.md#migration), [Microsoft 365 Copilot](m365-dr-workload-copilot.md#migration-and-user-experience), [Microsoft Defender for Office P1](m365-dr-workload-mdo-p1.md#migration), [Office for the Web](m365-dr-workload-office-for-web.md#migration), [Viva Connections](m365-dr-workload-viva-connections.md#migration), [Microsoft Purview](m365-dr-workload-purview.md#migration), and [Other Services](m365-dr-workload-other.md).
123
+
Data moves are a back-end service operation with minimal impact to a customer's operations. For information related to specific workloads, customer administrators can refer to the "Migration" sections in the following Workload Data Residency Capabilities pages: [Exchange Online](m365-dr-workload-exo.md#migration), [SharePoint and OneDrive](m365-dr-workload-spo.md#migration-with-advanced-data-residency), [Microsoft Teams](m365-dr-workload-teams.md#migration), [Microsoft 365 Copilot](m365-dr-workload-copilot.md#migration-and-user-experience), [Microsoft Defender for Office P1](m365-dr-workload-mdo-p1.md#migration), [Office for the Web](m365-dr-workload-office-for-web.md#migration), [Viva Connections](m365-dr-workload-viva-connections.md#migration), [Microsoft Purview](m365-dr-workload-purview.md#migration), and [Other Services](m365-dr-workload-other.md).
127
124
128
125
### During and After your Migration
129
126
130
127
No action is needed from the customer while Microsoft moves each ADR workload and associated customer tenant data to the customer's eligible _Local Region Geography_.
131
128
132
-
Customer administrators can visit the Message center or “Data location” section within the Microsoft 365 admin center throughout the migration process to review any migration notices and see when each workload service completes migration. From the Microsoft 365 admin center, customer administrators can access the Message center by navigating to **Health > Message center** and the "Data location" section by navigating to **Settings > Org settings > Organization profile > Data location**.
129
+
Customer administrators can visit the Message center or "Data location" section within the Microsoft 365 admin center throughout the migration process to review any migration notices and see when each workload service completes migration. From the Microsoft 365 admin center, customer administrators can access the Message center by navigating to **Health > Message center** and the "Data location" section by navigating to **Settings > Org settings > Organization profile > Data location**.
133
130
134
131
The following screenshots are examples of the Microsoft 365 admin center Data location view that an ADR customer can expect to see during and after their migration.
135
132
@@ -153,7 +150,7 @@ Given the complex nature of services included in an E3 or E5 license, the migrat
153
150
154
151
Microsoft does not provide a granular status to indicate progress toward migration completion for individual customer scenarios.
155
152
156
-
Customer administrators can stay informed of migration updates through Message center notifications and by reviewing the “Data location” section within the Microsoft 365 admin center to see when a workload completes migration to their _Local Region Geography_. From the Microsoft 365 admin center, customer administrators can access the Message center by navigating to **Health > Message center** and the "Data location" section by navigating to **Settings > Org settings > Organization profile > Data location**.
153
+
Customer administrators can stay informed of migration updates through Message center notifications and by reviewing the "Data location" section within the Microsoft 365 admin center to see when a workload completes migration to their _Local Region Geography_. From the Microsoft 365 admin center, customer administrators can access the Message center by navigating to **Health > Message center** and the "Data location" section by navigating to **Settings > Org settings > Organization profile > Data location**.
157
154
158
155
For more information on Migration, customer administrators can refer to the following pages:
Copy file name to clipboardExpand all lines: microsoft-365/enterprise/m365-dr-overview.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,8 @@ In order to promote clarity in the capability descriptions on data residency fun
33
33
|Macro Region Geography 1 - EMEA |Data centers in Austria, Finland, France, Ireland, Italy, Netherlands, Poland, Spain, Sweden <br/> <br/> **Note:** For tenants with a default geography of Israel; data can be stored in Macro Region Geography 1 – EMEA or additional datacenters located in their default geography (i.e., Israel). |
34
34
|Macro Region Geography 2 - Asia Pacific |Data centers in Australia, Hong Kong Special Administrative Region, Indonesia, Japan, Malaysia, New Zealand, Singapore, South Korea <br/> <br/> **Note:** For tenants with a default geography of Taiwan; data can be stored in Macro Region Geography 2 – Asia Pacific or additional datacenters located in their default geography (i.e., Taiwan). |
35
35
|Macro Region Geography 3 - Americas |Data centers in Brazil, Chile, Mexico, United States |
36
-
|Local Region Geography |Australia, Brazil, Canada, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mexico, New Zealand, Norway, Poland, Qatar, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, United Arab Emirates, United Kingdom |
37
-
|Future Local Region Geography | Future planned data center regions: Austria, Chile, Denmark, Greece, Saudi Arabia |
36
+
|Local Region Geography |Australia, Brazil, Canada, Chile, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mexico, New Zealand, Norway, Poland, Qatar, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, United Arab Emirates, United Kingdom |
37
+
|Future Local Region Geography | Future planned data center regions: Austria, Denmark, Greece, Saudi Arabia |
38
38
|Geography |_Local Region Geography, Future Local Region Geography_, or _Macro Region Geography_|
39
39
|Satellite Geography |If a customer subscribes to the Multi Geo service, then they can set policy at a user level to store customer data in other Geographies outside of the _Tenant__Primary Provisioned Geography_|
40
40
|Microsoft Entra ID |Microsoft Entra ID is the new name for [Azure Active Directory](/entra/fundamentals/new-name)|
@@ -100,10 +100,8 @@ There are three methods for ensuring that the _Tenant_ data location for a parti
100
100
1. Product Terms: Exchange Online, SharePoint, OneDrive, Microsoft Teams and Microsoft 365 Copilot provisioned in Australia, Brazil, Canada, France, Germany, India, Japan, Qatar, South Korea, Norway, South Africa, Sweden, Switzerland, United Arab Emirates, United Kingdom, European Union and the United States have a commitment for customer data residency expressed in the [Product Terms](https://www.microsoft.com/licensing/terms/product/PrivacyandSecurityTerms/all). For more information, see the [Product Terms Data Residency page](m365-dr-product-terms-dr.md).
101
101
1._Multi Geo_ subscription: allows customers to assign data location for Exchange Online, SharePoint, OneDrive, Microsoft Teams and Microsoft 365 Copilot to any supported _Geography_. For more information, see [Multi Geo Data Residency](microsoft-365-multi-geo.md).
102
102
1._Advanced Data Residency_ subscription provides data residency commitments for an expanded set of Microsoft 365 services in any _Local Region Geography_. For more information, see the [Advanced Data Residency page](advanced-data-residency.md).
103
-
#### **Table 2: Available Data Residency by Workload**
104
103
105
-
> [!NOTE]
106
-
> Viva Topics has been retired as of February 22, 2025. Therefore, Viva Topics is no longer a supported workload in ADR. For more details, please visit [aka.ms/TopicsFebSupport](https://aka.ms/TopicsFebSupport).
104
+
#### **Table 2: Available Data Residency by Workload**
107
105
108
106
| Service Name | Product Terms | Multi-Geo | ADR |
109
107
|:-----|:-----|:-----|:-----|
@@ -130,6 +128,7 @@ There are three methods for ensuring that the _Tenant_ data location for a parti
130
128
| Australia | P-M-A | P-M-A | P-M-A | P-M-A | A | A | A | A |
131
129
| Brazil | P-M-A | P-M-A | P-M-A | P-M-A | A | A | A | A |
132
130
| Canada | P-M-A | P-M-A | P-M-A | P-M-A | A | A | A | A |
131
+
| Chile | M-A | M-A | M-A | M-A | A | A | A | A |
133
132
| European Union | P-M | P-M | P-M | P-M | - | - | - | - |
134
133
| France | P-M-A | P-M-A | P-M-A | P-M-A | A | A | A | A |
135
134
| Germany | P-M-A | P-M-A | P-M-A | P-M-A | A | A | A | A |
@@ -169,6 +168,7 @@ The following Regional Geographies can store data at rest.
169
168
|Australia |Sydney, Melbourne |
170
169
|Brazil |Rio, Campinas |
171
170
|Canada |Quebec City, Toronto |
171
+
|Chile |Santiago |
172
172
|European Union |Austria (Vienna), Finland (Helsinki), France (Paris, Marseille), Ireland (Dublin), Italy (Milan), Netherlands (Amsterdam), Poland (Warsaw), Spain (Madrid), Sweden (Gävle, Sandviken, Staffanstorp) |
Copy file name to clipboardExpand all lines: microsoft-365/enterprise/o365-data-locations.md
+2-9Lines changed: 2 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,16 +28,9 @@ description: "Determine where your Microsoft 365 customer data is stored worldwi
28
28
This article helps you to understand how you can determine current data residency and data residency commitments.
29
29
30
30
> [!NOTE]
31
-
> Viva Topics has been retired as of February 22, 2025. Therefore, Viva Topics is no longer a supported workload in ADR. For more details, please visit [aka.ms/TopicsFebSupport](https://aka.ms/TopicsFebSupport).
32
-
33
-
> [!NOTE]
34
-
> The **New Zealand** local data center region launched on December 1, 2024. If your organization requires the migration of your Microsoft 365 customer data to New Zealand, and data residency commitments for New Zealand, see [Advanced Data Residency](advanced-data-residency.md).
35
-
36
-
> [!NOTE]
37
-
> The **Taiwan** local data center region launched on November 1, 2024. If your organization requires the migration of your Microsoft 365 customer data to Taiwan, and data residency commitments for Taiwan, see [Advanced Data Residency](advanced-data-residency.md).
38
-
31
+
> The **Indonesia**, **Malaysia**, and **Chile** local data center regions launched in June 2025. See [Advanced Data Residency](advanced-data-residency.md) if your organization requires the migration of your Microsoft 365 customer data to Indonesia, Malaysia, or Chile and data residency commitments for these countries.
39
32
> [!NOTE]
40
-
> For tenants in Australia, Brazil, Canada, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mexico, New Zealand, Norway, Poland, Qatar, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, United Arab Emirates, and United Kingdom, more workloads are available for data residency commitments. For more information, see [Advanced Data Residency](advanced-data-residency.md).
33
+
> For tenants in Australia, Brazil, Canada, Chile, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mexico, New Zealand, Norway, Poland, Qatar, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, United Arab Emirates, and United Kingdom, more workloads are available for data residency commitments. For more information, see [Advanced Data Residency](advanced-data-residency.md).
41
34
42
35
See the following links to understand how you can determine current data residency and data residency commitments.
0 commit comments