Microsoft 365 Copilot Uses Content From Another Geography: Fix

When your Microsoft 365 Copilot returns answers that include data or documents from a region outside your tenant’s primary location, it disrupts work and raises data sovereignty concerns. This problem occurs when Copilot’s data residency configuration is missing or misapplied, causing it to fall back to a default geography for grounded responses. In this article, you will learn why Copilot pulls content from an unintended geography and how to lock it to your tenant’s designated region.

Why Copilot Returns Content From the Wrong Geography

Microsoft 365 Copilot grounds its responses on Microsoft Graph data, which includes documents, emails, and calendar events stored across your tenant. When your tenant uses Microsoft 365 Multi-Geo, each user can have a preferred data location. However, Copilot does not automatically respect that location unless you explicitly configure data residency for Copilot. Without this configuration, Copilot may query content from any geography where data exists, especially when the user’s preferred data location is not mapped to a Copilot-enabled region or when the Copilot service itself is provisioned in a default geography.

The root cause is the absence of a Copilot data residency policy in your tenant. By default, Copilot processes queries in the geography closest to the tenant’s home region. If your tenant has users in multiple geographies but no Copilot data residency policy, Copilot can pull content from any of those geographies. This happens because the Copilot service does not filter results by user location unless you enforce that rule through the admin center.

Another contributing factor is the way Copilot indexes content. Copilot indexes all Microsoft Graph data that is accessible to the user, regardless of its storage geography. If a user has permissions to documents stored in a different region, Copilot can retrieve those documents in its responses. To prevent this, you must restrict Copilot’s data sources to a specific geography.

Steps to Configure Copilot Data Residency for a Single Geography

Follow these steps to ensure Copilot only uses content from your tenant’s primary geography or a designated multi-geo region. You need Global Administrator or Copilot Administrator permissions to make these changes.

1. Open the Microsoft 365 admin center
   Go to admin.microsoft.com and sign in with your admin credentials. In the left navigation pane, select Settings then Org settings.
2. Locate the Copilot settings
   In the Org settings page, scroll down to Copilot and click it. If you do not see Copilot listed, your tenant may not have the required license. Verify that you have Copilot for Microsoft 365 licenses assigned to users.
3. Open the Data residency section
   Inside the Copilot settings pane, select the Data residency tab. This tab contains options for restricting Copilot processing and data storage to a specific geography.
4. Enable data residency for Copilot
   Toggle the switch labeled Restrict Copilot processing to selected geography to On. A dropdown menu appears listing available geographies. Choose the geography that matches your tenant’s primary data location, for example North America or Europe.
5. Confirm the change
   Click Save at the bottom of the pane. The admin center applies the setting within a few minutes. Copilot now uses only content stored in the selected geography for all users in the tenant.

If You Use Microsoft 365 Multi-Geo

If your tenant has users in multiple geographies, you can assign each user to a specific Copilot geography. Go to Settings > Org settings > Copilot > Data residency and select User-level geography assignment. Then use PowerShell to assign each user a preferred data location. Run the Set-MultiGeoUser cmdlet with the -PreferredDataLocation parameter. After assignment, Copilot respects the user’s geography and only retrieves content from that region.

If Copilot Still Uses Content From an Unwanted Geography

Copilot Returns Content From a Geography That Is Not in the Data Residency Policy

If you configured data residency but Copilot still returns content from a different region, check that the policy applies to all users. In the Data residency tab, verify that the toggle is On and that the correct geography is selected. Then, wait up to 24 hours for the change to propagate across all Copilot services. If the problem persists, remove and re-add the data residency policy by toggling the setting Off, saving, then toggling it On again.

Copilot Indexes Content From a Deleted Geography

When you remove a geography from your tenant, Copilot may still reference cached content from that region. To force a refresh, go to Settings > Org settings > Copilot > Data sources and click Refresh index. This triggers a full reindex of all Microsoft Graph data and removes references to content from the deleted geography. The reindex can take several hours depending on the size of your tenant.

Users with Cross-Geography Permissions Still See External Content

If a user has permissions to documents in another geography, Copilot can retrieve those documents even after you configure data residency. To block this, restrict the user’s SharePoint site permissions to only the geography you want them to access. Alternatively, use SharePoint admin center to set site-level data location policies that prevent cross-geography sharing.

Copilot Data Residency Options: Single Geography vs Multi-Geo

Item	Single Geography	Multi-Geo with User Assignment
Description	All Copilot processing and data retrieval restricted to one region	Each user assigned to a specific geography for Copilot processing
Setup location	Settings > Org settings > Copilot > Data residency	Settings > Org settings > Copilot > Data residency plus PowerShell
Best for	Tenants with all users in one region	Tenants with users spread across multiple regions
Propagation time	Up to 24 hours	Up to 48 hours after PowerShell assignment
User impact	All users see only content from the chosen geography	Each user sees only content from their assigned geography

You can now control which geography Copilot uses for content retrieval by applying a data residency policy in the Microsoft 365 admin center. If your tenant uses Multi-Geo, assign each user a preferred data location with PowerShell to enforce per-user boundaries. For tenants with a single geography, the toggle in the Data residency tab is sufficient. After making changes, allow up to 24 hours for full propagation and force a Copilot index refresh if you remove a geography entirely.