Merge pull request #29353 from MicrosoftDocs/main

Ruchika-mittal01 · web-flow · commit f497daab2798 · 2025-09-03T04:12:23.000+05:30
OOB publish 09/02
diff --git a/microsoft-365/enterprise/TOC.yml b/microsoft-365/enterprise/TOC.yml
@@ -318,7 +318,7 @@ items:
               href: m365-dr-workload-spo.md
             - name: Microsoft Teams
               href: m365-dr-workload-teams.md
-            - name: Microsoft 365 Copilot
+            - name: Microsoft 365 Copilot and Copilot Chat
               href: m365-dr-workload-copilot.md
             - name: Microsoft Defender for Office P1
               href: m365-dr-workload-mdo-p1.md
diff --git a/microsoft-365/enterprise/advanced-data-residency.md b/microsoft-365/enterprise/advanced-data-residency.md
@@ -31,7 +31,7 @@ The following services are included in ADR. For more information, see:
 - [Exchange Online](m365-dr-workload-exo.md)
 - [SharePoint and OneDrive](m365-dr-workload-spo.md)
 - [Microsoft Teams](m365-dr-workload-teams.md)
-- [Microsoft 365 Copilot](m365-dr-workload-copilot.md)
+- [Microsoft 365 Copilot and Microsoft 365 Copilot Chat](m365-dr-workload-copilot.md)
 - [Microsoft Defender for Office P1 and Exchange Online Protection](m365-dr-workload-mdo-p1.md)
 - [Microsoft 365 web apps (formerly "Office for the Web")](m365-dr-workload-office-for-web.md)
 - [Viva Connections](m365-dr-workload-viva-connections.md)
@@ -52,7 +52,7 @@ The following services are included in ADR. For more information, see:
 
 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:
 
-- 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.
+- The _Tenant Default Geography_ must be one of the countries or regions included in the _Local Region Geography_: Australia, Austria, 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.
 - Customers must have licenses for one or more of the following products:
   - Microsoft 365 F1, F3, E3, or E5 (including SKUs without Microsoft Teams)
   - Office 365 F3, E1, E3, or E5 (including SKUs without Microsoft Teams)
@@ -132,7 +132,7 @@ The "Data location" section in the Microsoft 365 admin center displays the most
 
 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 Tenant Global Admin 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.
 
-Data moves are a back-end service operation with minimal impact to a customer's operations. For information related to specific services, Tenant Global Admins can refer to the "Migration" sections in the following Service 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), [Microsoft 365 web apps (formerly known as "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).
+Data moves are a back-end service operation with minimal impact to a customer's operations. For information related to specific services, Tenant Global Admins can refer to the "Migration" sections in the following Service 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 and Microsoft 365 Copilot Chat](m365-dr-workload-copilot.md#migration-and-user-experience), [Microsoft Defender for Office P1](m365-dr-workload-mdo-p1.md#migration), [Microsoft 365 web apps (formerly known as "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).
 
 ### During and After your Migration
 
diff --git a/microsoft-365/enterprise/m365-dr-commitments.md b/microsoft-365/enterprise/m365-dr-commitments.md
@@ -44,11 +44,11 @@ The following customer data is stored at rest in the _Local Region Geography_:
 
 - Microsoft Teams chat messages (including private messages, channel messages, meeting messages and images used in chats), and, for customers using Microsoft Stream (on SharePoint), meeting recordings
 
-## Microsoft 365 Copilot
+## Microsoft 365 Copilot and Microsoft 365 Copilot Chat
 
 The following customer data is stored at rest in the _Local Region Geography_:
 
-- Any stored content of interactions with Microsoft 365 Copilot to the extent not included in the preceding commitments.
+- Any stored content of interactions with Microsoft 365 Copilot and Microsoft 365 Copilot Chat to the extent not included in the preceding commitments.
 
 ## Microsoft Defender for Office P1
 
diff --git a/microsoft-365/enterprise/m365-dr-overview.md b/microsoft-365/enterprise/m365-dr-overview.md
@@ -40,15 +40,15 @@ In order to promote clarity in the capability descriptions on data residency fun
 |European Union (EU) |An international organization comprising 27 European countries. These countries are **Austria**, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, **Finland**, **France**, **Germany**, Greece, Hungary, **Ireland**, **Italy**, Latvia, Lithuania, Luxembourg, Malta, **Netherlands**, **Poland**, Portugal, Romania, Slovakia, Slovenia, **Spain**, and **Sweden**. <br/> <br/> **Note:** Microsoft 365 currently has data centers in the **bold** _European Union_ countries. |
 |European Union/EFTA |Data that is stored within the _European Union (EU)_ and/or the _European Free Trade Association (EFTA)_. |
 |European Union Data Boundary (EUDB) |_European Union Data Boundary_ commitment. For more information, please see [Microsoft EU Data Boundary Overview - Microsoft Trust Center](https://www.microsoft.com/trust-center/privacy/european-data-boundary-eudb). |
-|Future Local Region Geography |Future planned data center regions: Austria, Denmark, Greece, Kuwait, Saudi Arabia, Thailand |
+|Future Local Region Geography |Future planned data center regions: Denmark, Greece, Kuwait, Saudi Arabia, Thailand |
 |Geography |_Local Region Geography, Future Local Region Geography_, or _Macro Region Geography_ |
 |Legacy Move Program |This program, which is no longer active, was offered to _Tenants_ who had a valid _Default Geography_ which allowed the _Tenant_ to migrate existing data at rest into a _Local Region Geography_. |
-|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 |
+|Local Region Geography |Australia, Austria, 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 |
 |Macro Region Geography |Macro Region Geography 1 – Europe, Macro Region Geography 2 – Asia Pacific, Macro Region Geography 3 – Americas, Macro Region Geography 4 – European Union/EFTA |
 |Macro Region Geography 1 – Europe |Data centers in Austria, Finland, France, Germany, 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 – Europe or additional data centers located in their _Default Geography_ (i.e., Israel). <br/> <br/> **Note:** This term is referenced as “Europe” on the _Data Location Card_. |
 |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 data centers located in their _Default Geography_ (i.e., Taiwan). |
 |Macro Region Geography 3 – Americas |Data centers in Brazil, Canada, Chile, Mexico, and the United States (USA) <br/> <br/> **Note:** This term is referenced as “Americas” on the _Data Location Card_. |
-|Macro Region Geography 4 – European Union/EFTA |Data centers in in Austria, Finland, France, Germany, Ireland, Italy, Netherlands, Poland, Spain, Sweden, Norway, and Switzerland. <br/> <br/> **Note:** This term is referenced as “European Union/EFTA” on the _Data Location Card_. |
+|Macro Region Geography 4 – European Union/EFTA |Data centers in Austria, Finland, France, Germany, Ireland, Italy, Netherlands, Poland, Spain, Sweden, Norway, and Switzerland. <br/> <br/> **Note:** This term is referenced as “European Union/EFTA” on the _Data Location Card_. |
 |Microsoft Entra ID |Microsoft Entra ID is the new name for [Azure Active Directory](/entra/fundamentals/new-name). |
 |Microsoft 365 admin center Data Location |To see the _Primary Provisioned Geography_ for Exchange Online, SharePoint, OneDrive, and Microsoft Teams, refer to the Microsoft 365 admin center by navigating to **Admin > Settings > Org settings > Organization profile > Data location**. |
 |Microsoft 365 Core Services |Exchange Online, SharePoint and OneDrive, Microsoft Teams, Microsoft 365 Copilot |
@@ -122,7 +122,7 @@ There are three methods for ensuring that the _Tenant_ data location for a parti
 |Exchange Online |X<sup>1</sup> |X<sup>2</sup> |X<sup>3</sup> |
 | SharePoint / OneDrive |X<sup>1</sup> |X<sup>2</sup> |X<sup>3</sup> |
 | Microsoft Teams |X<sup>1</sup> |X<sup>2</sup> |X<sup>3</sup> |
-| Microsoft 365 Copilot |X<sup>1</sup> |X<sup>2</sup> |X<sup>3</sup> |
+| Microsoft 365 Copilot and Copilot Chat |X<sup>1</sup> |X<sup>2</sup> |X<sup>3</sup> |
 | Microsoft Defender for Office P1 |- |- |X<sup>3</sup> |
 | Microsoft 365 web apps (formerly known as "Office for the Web") |- |- |X<sup>3</sup> |
 | Viva Connections |- |- |X<sup>3</sup> |
@@ -140,6 +140,7 @@ There are three methods for ensuring that the _Tenant_ data location for a parti
 | Country/Region  | Exchange Online | SharePoint, OneDrive | Teams | Microsoft 365 Copilot | MDO P1 | Office for the web | Viva Connections | Purview |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- |
 | Australia | P-M-A | P-M-A | P-M-A | P-M-A | A | A | A | A |
+| Austria | M-A | M-A | M-A | M-A | A | A | A | A |
 | Brazil | P-M-A | P-M-A | P-M-A | P-M-A | A | A | A | A |
 | Canada | P-M-A | P-M-A | P-M-A | P-M-A | A | A | A | A |
 | Chile | M-A | M-A | M-A | M-A | A | A | A | A |
@@ -182,6 +183,7 @@ The following table displays the various _Geographies_ and the corresponding dat
 |Americas  |Brazil (Campinas, Rio), Canada (Quebec City, Toronto), Chile (Santiago), Mexico (Queretaro), United States (Boydton, Cheyenne, Chicago, Des Moines, Quincy, San Antonio, Santa Clara, San Jose)  |
 |Asia Pacific  |Australia (Sydney, Melbourne), India (Chennai, Mumbai, Pune), Japan (Osaka, Tokyo), South Korea (Busan, Seoul), New Zealand (Auckland), Taiwan (Taipei)  |
 |Australia  |Melbourne, Sydney  |
+|Austria  |Vienna  |
 |Brazil  |Campinas, Rio  |
 |Canada   |Quebec City, Toronto  |
 |Chile   |Santiago  |
diff --git a/microsoft-365/enterprise/m365-dr-product-terms-dr.md b/microsoft-365/enterprise/m365-dr-product-terms-dr.md
@@ -42,7 +42,7 @@ _Microsoft Privacy and Security Product Terms_ included with Microsoft's Cloud P
 
 The language at time of writing this article is:
 
-- **Office 365 Services** If Customer provisions its tenant in Australia, Brazil, Canada, the European Union, France, Germany, India, Japan, Norway, Qatar, South Africa, South Korea, Sweden, Switzerland, the United Kingdom, the United Arab Emirates, or the United States, Microsoft stores the following Customer Data at rest only within that Geo: (1) Exchange Online mailbox content (e-mail body, calendar entries, and the content of e-mail attachments), (2) SharePoint site content and the files stored within that site, (3) files uploaded to OneDrive, (4) Microsoft Teams chat messages (including private messages, channel messages, meeting messages and images used in chats), and for customers using Microsoft Stream (on SharePoint), meeting recordings, and (5) any stored content of interactions with Microsoft 365 Copilot to the extent not included in the preceding commitments.
+- **Office 365 Services** If Customer provisions its tenant in Australia, Brazil, Canada, the European Union, France, Germany, India, Japan, Norway, Qatar, South Africa, South Korea, Sweden, Switzerland, the United Kingdom, the United Arab Emirates, or the United States, Microsoft stores the following Customer Data at rest only within that Geo: (1) Exchange Online mailbox content (e-mail body, calendar entries, and the content of e-mail attachments), (2) SharePoint site content and the files stored within that site, (3) files uploaded to OneDrive, (4) Microsoft Teams chat messages (including private messages, channel messages, meeting messages and images used in chats), and for customers using Microsoft Stream (on SharePoint), meeting recordings, and (5) any stored content of interactions with Microsoft 365 Copilot or Microsoft 365 Copilot Chat to the extent not included in the preceding commitments.
 - For current language, refer to the [Privacy and Security Product Terms webpage](https://www.microsoft.com/licensing/terms/product/PrivacyandSecurityTerms/all) and view the section titled "Location of Customer Data at Rest for Core Online Services."
 
 For more data residency capabilities, refer to the [_Multi-Geo_ service](microsoft-365-multi-geo.md) and/or the [_Advanced Data Residency_ service](advanced-data-residency.md).
diff --git a/microsoft-365/enterprise/m365-dr-workload-copilot.md b/microsoft-365/enterprise/m365-dr-workload-copilot.md
@@ -1,6 +1,6 @@
 ---
-title: Data Residency for Microsoft 365 Copilot
-description: Learn about data residency for Microsoft 365 Copilot.
+title: Data Residency for Microsoft 365 Copilot and Copilot Chat
+description: Learn about data residency for Microsoft 365 Copilot and Copilot Chat.
 ms.author: v-fahasen
 author: fhasen-msft
 manager: v-nihmi
@@ -22,7 +22,7 @@ ms.collection:
 - magic-ai-copilot
 ---
 
-# Data Residency for Microsoft 365 Copilot
+# Data Residency for Microsoft 365 Copilot and Copilot Chat
 
 ## Overview
 
@@ -33,7 +33,9 @@ The following applications provide the ability to interact with Microsoft 365 Co
 
 The content of interactions and the related semantic index with Microsoft 365 Copilot are stored at rest in the relevant _Local Region Geography_.
 
-## Data Residency Commitments Available for Microsoft 365 Copilot
+[Microsoft 365 Copilot Chat](/copilot/overview) (formerly Microsoft Copilot for Entra account users) offers secure, AI chat that adds pay-as-you-go agents.
+
+## Data Residency Commitments Available for Microsoft 365 Copilot and Copilot Chat
 
 ### Product Terms
 
@@ -59,9 +61,9 @@ Required Conditions:
 
 **Commitment:**
 
-Refer to the [ADR Commitment page](m365-dr-commitments.md#microsoft-365-copilot) to understand the specific data at rest commitments for Microsoft 365 Copilot. Examples of the committed data include:
+Refer to the [ADR Commitment page](m365-dr-commitments.md#microsoft-365-copilot-and-microsoft-365-copilot-chat) to understand the specific data at rest commitments for Microsoft 365 Copilot. Examples of the committed data include:
 
-- "Content of Interactions" such as the user's prompt and Microsoft Copilot's response, including citations to any information used to ground Microsoft Copilot's response.
+- "Content of Interactions" such as the user's prompt and the response from Microsoft 365 Copilot or Microsoft 365 Copilot Chat, including citations to any information used to ground Microsoft 365 Copilot's response.
 
 ### Multi-Geo add-on
 
@@ -72,7 +74,7 @@ Required Conditions:
 1. Total purchased Multi-Geo units must be greater than 5% of the total eligible licenses in the _Tenant_.
 
 **Commitment:**
-Multi-Geo capabilities in Microsoft 365 Copilot enable content of interactions with Microsoft 365 Copilot to be stored at rest in a specified _Macro Region Geography_ or _Local Region Geography_ location. Microsoft 365 Copilot uses the Preferred Data Location (PDL) for users and groups to determine where to store data. If the PDL isn't set or is invalid, data is stored in the _Tenant's Primary Provisioned Geography_ location. The _Geography_ where the content of interactions with Microsoft 365 Copilot are stored is determined by the PDL of the user interacting with Microsoft 365 Copilot. This means that the storage of content of interactions for users in different regions will be based on their respective PDL configurations.
+Multi-Geo capabilities in Microsoft 365 Copilot and Microsoft 365 Copilot Chat enable content of interactions with Microsoft 365 Copilot and Microsoft 365 Copilot Chat to be stored at rest in a specified _Macro Region Geography_ or _Local Region Geography_ location. Both Microsoft 365 Copilot and Microsoft 365 Copilot Chat use the Preferred Data Location (PDL) for users and groups to determine where to store data. If the PDL isn't set or is invalid, data is stored in the _Tenant's Primary Provisioned Geography_ location. The _Geography_ where the content of interactions with Microsoft 365 Copilot and Microsoft 365 Copilot Chat are stored is determined by the PDL of the user interacting with Microsoft 365 Copilot or Microsoft 365 Copilot Chat, respectively. This means that the storage of content of interactions for users in different regions will be based on their respective PDL configurations.
 
 To find the current location of a user's content of interactions with Microsoft 365 Copilot by referencing the PDL configuration for that user. Refer to [Multi-Geo Testing](m365-multi-geo-user-testing.md).
 
@@ -82,7 +84,7 @@ To find the current location of a user's content of interactions with Microsoft
 Two people are working together on a Microsoft Word document. User A authored the document and stored it in the OneDrive for Business personal storage site, which is located in France. User B is in Canada and asks Microsoft 365 Copilot to rewrite a paragraph in the document. The paragraph User B submitted as the prompt, as well as the rewrite options Microsoft 365 Copilot provides (the "content of interactions" in this case) are stored in Canada; the original document remains in France, as does any rewrite the user accepts into that document.
 
 **Teams Meeting Experience**
-Microsoft Teams meeting recording video location is determined by the user PDL that starts the recording, or when meetings have an automatic recording policy, the location is determined by the meeting organiser. When users in other regions interact with Microsoft 365 Copilot in Teams, those user prompts and corresponding responses are stored in the location of the user that asks the Microsoft 365 Copilot questions.
+Microsoft Teams meeting recording video location is determined by the user PDL that starts the recording, or when meetings have an automatic recording policy, the location is determined by the meeting organizer. When users in other regions interact with Microsoft 365 Copilot in Teams, those user prompts and corresponding responses are stored in the location of the user that asks the Microsoft 365 Copilot questions.
 
 ### Migration and User Experience
 
diff --git a/microsoft-365/enterprise/microsoft-365-multi-geo.md b/microsoft-365/enterprise/microsoft-365-multi-geo.md
diff --git a/microsoft-365/enterprise/o365-data-locations.md b/microsoft-365/enterprise/o365-data-locations.md
