Microsoft Copilot processes data for users in the European Union and European Free Trade Association countries under specific data residency rules. Many business users need to know whether their prompts, files, and generated content remain inside the EU Data Boundary. The EU Data Boundary is a set of data storage and processing commitments that Microsoft applies to its core online services, and Copilot inherits some but not all of these protections. This article explains which Copilot data stays in the EU region, which data may leave the boundary, and how to verify your tenant configuration.
Key Takeaways: Copilot Data Residency in the EU Data Boundary
- Microsoft 365 admin center > Settings > Org settings > Copilot > Data residency: Controls whether Copilot stores prompts and responses in the EU Data Boundary.
- Azure OpenAI Service endpoint selection: Prompts sent to Azure OpenAI endpoints outside the EU region are not covered by the EU Data Boundary.
- Copilot chat history export via Microsoft Purview: Use the Content Search tool to verify that your tenant data is stored in EU datacenters.
What the EU Data Boundary Covers for Copilot
The EU Data Boundary is Microsoft’s commitment to store and process customer data for core online services within the European Union and EFTA countries. For Microsoft 365, this boundary covers Exchange Online, SharePoint Online, OneDrive for Business, Teams, and other core services. Copilot, which runs on top of these services, inherits the data residency protections of the underlying Microsoft 365 services for certain data categories.
Data That Stays in the EU Data Boundary
The following Copilot-related data remains in the EU Data Boundary when your tenant is configured for EU data residency:
- Prompts and responses in Microsoft 365 Copilot: When you use Copilot in Word, Excel, PowerPoint, Outlook, or Teams, your prompts and the generated content are stored in the same region as your tenant data. If your tenant is in an EU datacenter, these items stay there.
- Chat history in Copilot for Microsoft 365: The chat history feature stores your conversation threads in Exchange Online mailboxes. If your mailbox is in the EU region, the history stays there.
- Grounding data from Microsoft Graph: Copilot retrieves context from your emails, documents, meetings, and other Microsoft 365 content. Because that content is already stored in your tenant’s region, the grounding process does not move it outside the boundary.
- File metadata and references: When Copilot references a file in SharePoint or OneDrive, the file metadata and access tokens remain in the tenant region.
Data That May Leave the EU Data Boundary
Not all Copilot data is covered by the EU Data Boundary. The following categories may be processed or stored outside the EU region:
- Azure OpenAI service inference calls: Copilot in Microsoft 365 uses Azure OpenAI Service to generate responses. If your tenant is not configured to use EU-based Azure OpenAI endpoints, the inference call may be routed to a datacenter in another region. Microsoft states that for tenants with EU Data Boundary enabled, the default Azure OpenAI endpoint is in the EU region, but you must verify this setting.
- Bing Search integration: When Copilot uses Bing Search to ground responses with live web data, the search query is sent to Bing’s global service, which may process the query outside the EU. The search result is returned to Copilot, but the query itself is not covered by the EU Data Boundary.
- Copilot in Windows: The Copilot experience in Windows 11 and Windows 10 uses a separate service endpoint. Microsoft has not committed to storing Windows Copilot prompts and responses within the EU Data Boundary. This data may be processed in the United States or other regions.
- Plugin and connector data: Third-party plugins and custom connectors in Copilot for Microsoft 365 may send data to external services. The EU Data Boundary does not apply to data sent to third-party endpoints.
How to Verify and Enforce EU Data Boundary for Copilot
To ensure Copilot data stays in the EU region, you must verify two configurations: your Microsoft 365 tenant data residency setting and the Azure OpenAI endpoint assignment.
Check Tenant Data Residency
- Open the Microsoft 365 admin center
Sign in with a Global Admin or Billing Admin account. Go to Settings > Org settings > Organization profile. - Review the Data location section
Look for the entry labeled Data location. It shows the region where your core customer data is stored. For the EU Data Boundary, this must list a European country such as France, Germany, Ireland, Netherlands, or Switzerland. - Check the Copilot data residency setting
In the admin center, navigate to Settings > Org settings > Copilot. Look for a setting called Data residency or Store data in EU Data Boundary. If this toggle exists, turn it on. Not all tenants see this option yet; it is being rolled out gradually.
Verify Azure OpenAI Endpoint Region
- Open the Azure portal
Sign in to portal.azure.com with an account that has Contributor or Owner access to the Azure subscription linked to your Microsoft 365 tenant. - Find the Azure OpenAI resource
Search for Azure OpenAI in the top search bar. Select the resource that is associated with your Copilot deployment. The resource name usually contains your tenant name or a standard prefix like copilot-. - Check the region
On the resource overview page, look at the Location field. It must show a European region such as France Central, Germany West Central, North Europe (Ireland), or West Europe (Netherlands). If it shows a non-EU region, you must deploy a new Azure OpenAI resource in an EU region and reconfigure Copilot to use it.
Reconfigure Copilot to Use an EU Azure OpenAI Endpoint
- Create a new Azure OpenAI resource in an EU region
In the Azure portal, click Create a resource, search for Azure OpenAI, and select a region such as France Central or North Europe. Complete the creation wizard. - Deploy the GPT model
In the new Azure OpenAI resource, go to Model deployments and deploy the same GPT model version that Copilot requires. Contact Microsoft Support for the exact model name if needed. - Update the Copilot service endpoint
Open a support ticket with Microsoft and request that your Copilot for Microsoft 365 tenant be pointed to the new Azure OpenAI endpoint. Provide the resource ID and region. Microsoft will update the backend configuration.
Common Misconceptions and Edge Cases
Copilot in Windows Is Not Covered by the EU Data Boundary
The Copilot sidebar in Windows 11 and Windows 10 uses a separate service that is not part of the Microsoft 365 EU Data Boundary. Prompts typed into the Windows Copilot pane are sent to Bing and Microsoft’s consumer AI services. These prompts may be processed in the United States or other regions. To limit data exposure, do not enter sensitive business data into Windows Copilot. Use only Copilot for Microsoft 365 for work-related tasks.
Bing Chat and Copilot in Edge Are Not Covered
When you use Copilot in the Microsoft Edge sidebar or the Bing Chat web interface, the same consumer service applies. These experiences are not part of the EU Data Boundary. Microsoft has not published a data residency commitment for Bing Chat or Edge Copilot for enterprise users. Treat these interfaces as non-compliant with EU data residency requirements.
Third-Party Plugins and Connectors
If your organization uses Power Platform connectors, third-party plugins like Jira or Salesforce connectors, or custom Copilot extensions, the data sent to those external services is not protected by the EU Data Boundary. You must review the data processing agreements of each third-party service separately. Microsoft recommends using only Microsoft-owned connectors for data that must stay in the EU region.
Export and Audit Logs
Microsoft Purview audit logs for Copilot activity are stored in the same region as your tenant. You can verify this by running a Content Search in the Microsoft Purview compliance portal. Search for Copilot interaction records and check the Location column in the results. If the location shows a non-EU region, contact Microsoft Support to request a data relocation.
| Item | Copilot for Microsoft 365 (EU Tenant) | Copilot in Windows / Bing Chat |
|---|---|---|
| Data residency commitment | Yes, when tenant is in EU region and Azure OpenAI endpoint is EU-based | No, consumer service with no regional boundary |
| Prompts and responses storage | Stored in tenant region (Exchange Online or SharePoint) | Stored in Microsoft consumer services, typically in the United States |
| Grounding data access | Uses Microsoft Graph data from tenant region | Uses Bing Search index and public web data |
| Plugin data protection | Not covered if third-party endpoints are used | Not covered |
| Admin control | Yes, via Microsoft 365 admin center and Azure portal | No admin control |
You can now verify your tenant’s data residency setting and Azure OpenAI endpoint region to ensure Copilot for Microsoft 365 stays within the EU Data Boundary. Next, check your Copilot in Windows usage policy and restrict employee access to the consumer Copilot if needed. As a concrete next step, open the Microsoft 365 admin center today and confirm that the Data location field shows an EU country.