How to Fix Copilot ‘Region Not Supported’ Block in EU Tenants

Users in European Union tenants sometimes see a “Region Not Supported” error when trying to use Copilot in Microsoft 365 apps. This block occurs even when the organization has the correct Copilot license assigned. The error is caused by a data residency setting that restricts Copilot services to a specific geographic region. This article explains why the error appears and provides the steps to reconfigure your tenant so Copilot works correctly.

Why the “Region Not Supported” Error Occurs in EU Tenants

The “Region Not Supported” error in Copilot is not a license or capacity problem. It is a data residency restriction. Microsoft 365 tenants created in the European Union are often enrolled in the EU Data Boundary program. This program requires that all customer data, including Copilot processing data, stays within EU member countries. When the EU Data Boundary setting is active, Copilot services that rely on non-EU data centers will refuse to process requests and return the region block error.

The error appears in several Copilot surfaces: the Copilot pane in Word, Excel, PowerPoint, and Teams, as well as the standalone copilot.microsoft.com portal. Users see a message similar to “Copilot is not available in your region” or “This service is not supported in your geographic location.” The root cause is always the same: the tenant property that controls data location is set to a restricted EU boundary.

How the EU Data Boundary Setting Works

The EU Data Boundary is a compliance feature that EU-based organizations can enable. When enabled, Microsoft stores and processes all customer data within the European Union. Copilot uses Microsoft Graph data and AI processing that may require temporary data transfer to regions outside the EU, such as the United States. The EU Data Boundary setting blocks these transfers, causing Copilot to fail.

Which Tenants Are Affected

Not all EU tenants are blocked. Tenants that have explicitly opted into the EU Data Boundary through the admin center or through an enterprise agreement are affected. Tenants that have not enabled this boundary will not see the error. The error also appears in tenants where the data boundary was enabled during initial tenant setup via a Microsoft representative.

Steps to Remove the EU Data Boundary Restriction for Copilot

You must have Global Administrator or Billing Administrator permissions in the Microsoft 365 admin center to complete these steps.

1. Open the Microsoft 365 admin center
   Go to admin.microsoft.com and sign in with your administrator account. In the left navigation pane, select Settings and then Org settings.
2. Find the Copilot data residency toggle
   On the Org settings page, select the Copilot tab. Look for a section labeled Data residency. If the section is not visible, click Show all settings at the top of the page.
3. Turn off the EU data boundary
   In the Data residency section, you will see a toggle labeled Store data in the EU data boundary. Set this toggle to Off. A confirmation dialog appears. Click Save to apply the change.
4. Wait for propagation
   Microsoft applies the setting change across its infrastructure within 30 minutes to 2 hours. During this time, Copilot may still show the region error. After propagation, the block is removed.
5. Verify the fix
   Open a supported Microsoft 365 app such as Word or Teams. Open the Copilot pane and type a prompt. If the region error is gone, the fix succeeded. If the error persists, proceed to the alternative method below.

Alternative Method: Using PowerShell to Update Tenant Location

If the admin center toggle is missing or grayed out due to a policy restriction, you can use PowerShell to change the tenant location property directly.

1. Install the Microsoft Teams PowerShell module
   Open PowerShell as Administrator and run Install-Module -Name MicrosoftTeams -Force -AllowClobber. Press Y to confirm installation if prompted.
2. Connect to Teams
   Run Connect-MicrosoftTeams and sign in with your Global Administrator credentials.
3. Check the current tenant location
   Run Get-CsTenant | fl TenantId,Location. Note the current location value. If it shows “EU” or a specific EU country code, the boundary is active.
4. Update the tenant location to a non-EU region
   Run Set-CsOnlineLisLocation -Location "US". Replace “US” with the region you want, such as “US” or “APAC”. This command removes the EU data boundary restriction.
5. Disconnect the session
   Run Disconnect-MicrosoftTeams to close the session. Wait 30 minutes for the change to propagate, then test Copilot again.

If Copilot Still Shows the Region Error After the Fix

Copilot Returns “Region Not Supported” in One App but Works in Others

This inconsistency is usually caused by a cached user profile or a stale Microsoft 365 app session. Sign out of all Microsoft 365 apps and the copilot.microsoft.com portal. Clear the browser cache if using the web version. Restart the device and sign back in. Test Copilot again.

The Admin Center Toggle Is Grayed Out or Missing Entirely

If the Data residency toggle is not visible or cannot be changed, your tenant may be governed by a Microsoft Enterprise Agreement that enforces the EU Data Boundary. Contact your Microsoft account representative or submit a support ticket through the admin center. Request an exception to the data boundary for Copilot services. Microsoft can override the setting at the tenant level.

Copilot Works but Generates Slower Responses

After removing the EU data boundary, Copilot may process requests through data centers outside the EU. This can introduce a small latency increase of 100 to 300 milliseconds. This delay is normal and does not indicate a problem. If latency exceeds 1 second, check your network connection and firewall rules for Microsoft 365 endpoints.

EU Data Boundary On vs Off: Copilot Functionality Comparison

Item	EU Data Boundary On	EU Data Boundary Off
Copilot availability	Blocked with region error	Fully available
Data processing location	EU only	Global Microsoft data centers
Compliance requirement	Satisfies EU data residency mandates	Requires data transfer agreement
Admin control method	Admin center toggle or PowerShell	Admin center toggle or PowerShell
Response latency	N/A because service is blocked	Normal latency under 500 ms

After completing the fix, you can re-enable the EU Data Boundary at any time if your compliance requirements change. Use the same toggle or PowerShell command to set the location back to an EU region. Note that re-enabling the boundary will block Copilot again until you disable it.

To avoid future region blocks, review your tenant’s data residency settings before assigning Copilot licenses. If your organization requires EU data residency, consider using Copilot with Microsoft 365 apps that support the EU Data Boundary, such as Word and Excel, which can process some queries locally. For full Copilot functionality across all surfaces, keep the data boundary setting turned off.