# Inside or outside the EU Data Boundary

Datalegale — 24 August 2026.

Copilot vs Flex Routing vs Anthropic vs web grounding vs Foundry. “In” means Microsoft’s EU Data Boundary (or Azure EU Data Zone) applies to that path when the tenant is otherwise eligible. Not legal advice. Check the live Microsoft Learn article; catalogues move.

Source page: /assessments/eu-data-boundary#inside-outside
Verified: Rows checked 24 August 2026 against Microsoft Learn EU Data Boundary transfer lists and Flex routing (EU and EFTA).

Cite as: Datalegale, Inside or outside the EU Data Boundary (August 2026).

| 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 |
| Flex Routing on — LLM inferencing | No, at peak load | US, Canada or Australia during peak demand | Copilot → Settings → Flex routing |
| Anthropic models in Copilot | No — excluded | Enabled as a Copilot model / subprocessor | Copilot settings + Message Center |
| Web grounding / Bing search queries | No | Web search is on; generated queries go to Bing | Copilot → Settings → web search |
| Copilot Studio / Power Platform agents | Only if the environment geo is in the Boundary and Flex Routing is disallowed | Environment outside EU; or Power Platform Flex Routing allowed | Power Platform admin center environment region + flex checkbox |
| Multi-Geo tenant | Not in scope for Microsoft 365 EUDB | Purchase or use of Multi-Geo Capabilities | Organization profile. Do not cite EUDB language you are not entitled to |
| Azure AI Foundry — regional EU resource | Not Copilot EUDB. Azure residency of that region | The resource was not placed in an EU region | Azure portal → resource → Region |
| Foundry Data Zone EU | Azure EU Data Boundary / Data Zone — not Copilot settings | You picked Global instead, or the model has no EU zone | Deployment type on the model |
| Foundry Global Standard / Global Provisioned | No. Inferencing may run in any Foundry region | Deployment type labelled Global | Azure Policy can block Global deployments |
| Claude / Anthropic on Foundry | No European data zone comparable to Azure OpenAI (as of 2026) | Those models are used on EU personal data | Model card + Anthropic as independent processor |

## How to use this table

Paste the rows that apply to your tenant into the Copilot DPIA. A brochure sentence (“Copilot is an EUDB service”) is not a map. Flex Routing, Anthropic, web grounding, Multi-Geo and Foundry Global are separate rows.

This is not legal advice and not a Chapter V opinion.