Does Copilot leave the EU?
Pick one. Five to eight minutes. Score before any email.
Reviewed by Datalegale · last source check 24 August 2026Score before any emailNot legal advice
Flex Routing
Copilot Flex Routing: Can Inferencing Leave the EU?
Data sovereignty
Is Microsoft 365 Copilot in the EU Data Boundary?
Purview & DLP
Copilot Oversharing: SharePoint, Labels and DLP
GDPR file
Is Microsoft’s Copilot DPIA Template Enough?
Identity & rollout
Safe Copilot Rollout: Identity Before Broad Access
Beyond Copilot
Copilot EUDB ≠ Foundry Data Zone ≠ Global
Executive pack
Microsoft 365 Copilot Readiness Assessment (EU)
Flex Routing · 4 min
Copilot Flex Routing: Can Inferencing Leave the EU?
Data sovereignty · 5 min
Is Microsoft 365 Copilot in the EU Data Boundary?
Purview & DLP · 4 min
Copilot Oversharing: SharePoint, Labels and DLP
GDPR file · 5 min
Is Microsoft’s Copilot DPIA Template Enough?
Identity & rollout · 4 min
Safe Copilot Rollout: Identity Before Broad Access
Beyond Copilot · 6 min
Copilot EUDB ≠ Foundry Data Zone ≠ Global
Executive pack · 8 min
Microsoft 365 Copilot Readiness Assessment (EU)
What leaves Europe
Comparison table
Does Copilot stay inside the EU Data Boundary?
Eligible Microsoft 365 Copilot is an EU Data Boundary service. That sentence is true and incomplete. Flex Routing inferencing, Anthropic models, web grounding, Multi-Geo and Foundry Global are not the same row. Data at rest is not the same as inferencing.
Inside or outside the EU Data Boundary Path In the EU Data Boundary? Leaves or excluded when What to check Microsoft 365 Copilot (eligible tenant, Flex Routing off) Yes — listed EUDB service You are not eligible (e.g. Multi-Geo), or you enable an excluded model / web grounding Org profile; Copilot is an EUDB workload Copilot Chat (work, commercial, eligible) Yes, same catalogue Same exceptions as Copilot Enterprise data protection / DPA applies to work identity Data at rest (prompts stored, Graph content) Yes, stays in the Boundary Limited pseudonymized operational data may be stored outside Do not confuse storage geo with inferencing geo Three-way split
If Copilot is in the EU Data Boundary, is Azure AI Foundry too?
No. Copilot EU Data Boundary, Foundry Data Zone EU and Foundry Global are three commitments. Copilot tenant settings do not govern Foundry. A green Copilot score does not cover a Global model endpoint.
Copilot EUDB ≠ Foundry Data Zone ≠ Global Path Where prompts infer What it is not Copilot, Flex Routing off EU Data Boundary (eligible tenants) Not a Foundry deployment type. Does not govern Azure resources. Copilot, Flex Routing on US, Canada or Australia at peak load Not Foundry Global. Different toggle, different product. Foundry regional EU resource That Azure region, unless the model card says otherwise Not Copilot EUDB. Resource region is a choice in Azure.
Common questions
Does Copilot Flex Routing leave the EU?
Inferencing can. Data at rest does not, except limited pseudonymized operational data. Prompts, responses and grounding data may be processed in the United States, Canada or Australia when Flex Routing is on and EU capacity is tight.
If Copilot is in the EU Data Boundary, is Azure AI Foundry too?
No. Copilot settings do not govern Foundry. Foundry follows resource region and deployment type.
Is Microsoft’s Copilot DPIA template enough for Article 35?
No. The template does not know your Flex Routing value, oversharing picture, or whether DLP lists Copilot as a location. Those are tenant rows.