How to Check Microsoft 365 Copilot Data Residency for a Tenant

Microsoft 365 Copilot processes and stores user prompts, responses, and grounded data within a specific geographic boundary defined by your tenant’s data residency policy. Many organizations must verify this location to meet compliance requirements under GDPR, local data protection laws, or internal security standards. The data residency setting controls where Copilot stores your chat history and indexed content from Microsoft Graph. This article explains how to check the current data residency for Copilot in your Microsoft 365 tenant using the admin center and PowerShell.

What Data Residency Means for Microsoft 365 Copilot

Data residency defines the geographic location where Microsoft stores and processes your tenant’s Copilot data. This includes user prompts, Copilot responses, grounded search results from Microsoft Graph, and the index of your organization’s content. Microsoft commits to storing this data within a specific Azure region that matches the tenant’s default data location, such as the European Union, United Kingdom, United States, or Australia.

The residency setting applies to Copilot for Microsoft 365, Copilot in Microsoft Teams, Copilot in Word, Excel, PowerPoint, Outlook, and Copilot in the Microsoft 365 app. It does not affect data stored in SharePoint, OneDrive, or Exchange Online, which have their own residency policies. The Copilot data residency policy is configured at the tenant level and cannot be changed per user or per workload.

Microsoft determines the default data residency region based on the country selected during tenant creation. If your organization signed up through a Microsoft volume licensing program or a Cloud Solution Provider, the region may differ. You can verify the current region using the Microsoft 365 admin center or PowerShell.

Steps to Check Copilot Data Residency in the Microsoft 365 Admin Center

The admin center provides a graphical interface to view the Copilot data residency setting. You need either the Global Administrator or the Compliance Administrator role to access this page.

1. Open the Microsoft 365 admin center
   Go to https://admin.microsoft.com and sign in with an account that has Global Administrator or Compliance Administrator privileges.
2. Navigate to Org settings
   In the left navigation pane, select Settings then Org settings. This page lists all tenant-level service settings.
3. Open the Copilot settings page
   Scroll down and click the Copilot tab. If you do not see the Copilot tab, your tenant may not have Copilot licensed or the setting may be hidden by a custom role. In that case, use the PowerShell method below.
4. Locate the Data Residency section
   On the Copilot settings page, scroll to the Data residency section. The page displays the current region name, such as European Union, United Kingdom, United States, or Australia. The region is read-only in this view; you cannot modify it here.
5. Verify the region matches your compliance needs
   Compare the displayed region with your organization’s data residency requirements. If the region is incorrect, you must contact Microsoft Support to request a change. Microsoft does not allow self-service region changes for Copilot data residency.

Steps to Check Copilot Data Residency Using PowerShell

PowerShell provides an alternative method for tenants that lack admin center access or for automated auditing. You need the Teams PowerShell module and the Global Administrator role.

1. Install the Teams PowerShell module
   Open PowerShell as an administrator and run Install-Module -Name MicrosoftTeams -Force -AllowClobber. If you already have the module, update it with Update-Module -Name MicrosoftTeams.
2. Connect to Microsoft Teams
   Run Connect-MicrosoftTeams and sign in with a Global Administrator account. The session remains active for up to 90 minutes.
3. Retrieve the tenant federation configuration
   Run Get-CsTenantFederationConfiguration | Select-Object DataResidency. The output shows the DataResidency property with a region code such as EU, GB, US, or AU.
4. Interpret the region code
   Map the code to a geographic region: EU means European Union, GB means United Kingdom, US means United States, AU means Australia. If the value is empty or shows a different code, contact Microsoft Support for clarification.
5. Disconnect the session
   Run Disconnect-MicrosoftTeams to end the session. Closing the PowerShell window also disconnects automatically.

Common Issues When Checking Copilot Data Residency

The Copilot tab is missing in the admin center

If you do not see the Copilot tab under Org settings, your tenant may not have Copilot licenses assigned. Verify that at least one user has a Copilot for Microsoft 365 license. Also confirm that your admin role includes the Copilot Settings permission. Global Administrator and Compliance Administrator roles have this permission by default. Custom roles may lack it.

PowerShell returns an empty DataResidency value

An empty DataResidency property indicates that the tenant is using the default region assigned at creation. For most tenants outside the European Union, the default is the United States. If you need confirmation, run Get-CsTenant | Select-Object CountryOrRegion to see the country associated with your tenant. Microsoft uses this country to determine the default data residency region.

The region shown does not match the tenant’s billing country

Data residency for Copilot is based on the Azure Active Directory tenant location, not the billing address. If your billing country is Canada but your tenant was created in the United States, Copilot data residency will show the United States. To change the region, you must submit a support request to Microsoft. Include your tenant ID, the current region, and the desired region. Microsoft evaluates requests on a case-by-case basis and may require a new tenant creation if the region change is not supported.

Copilot Data Residency Regions: Default vs Available

Item	Default Region	Available Regions
European Union tenants	EU (European Union)	EU only
United Kingdom tenants	GB (United Kingdom)	GB only
United States tenants	US (United States)	US only
Australia tenants	AU (Australia)	AU only
All other countries	US (United States)	US only

Microsoft does not offer a self-service region selection for Copilot data residency. The region is locked to the tenant’s initial geographic assignment. If your organization moves its primary operations to a different region, you must create a new tenant and migrate data to change the Copilot data residency region.

For tenants with multi-geo configurations, Copilot data residency follows the tenant’s default location, not the satellite geography locations. Users in satellite geographies still have their Copilot data stored in the tenant’s default region. This design ensures consistent compliance boundaries for the Copilot service.

You can now verify your tenant’s Copilot data residency using either the admin center or PowerShell. If the region does not meet your compliance needs, contact Microsoft Support to request a change. As an advanced step, automate the PowerShell check with a scheduled script that emails the DataResidency value to your compliance team weekly.