# Copilot EUDB ≠ Foundry Data Zone ≠ Global

Datalegale — 24 August 2026.

Three commitments people collapse into “it runs in Europe”. Only the first is a Copilot tenant setting. The other two are Azure deployment types.

Source page: /assessments/azure-ai-foundry#foundry-split
Verified: Checked 24 August 2026 against Microsoft Learn Foundry deployment types and EUDB optional-capability transfers.

Cite as: Datalegale, Copilot EUDB ≠ Foundry Data Zone ≠ Global (August 2026).

| 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. |
| Foundry Data Zone EU | Any geography in Microsoft’s EU data zone (EU members; EFTA may be included) | Not the Copilot Flex Routing setting. Not “this one datacentre”. |
| Foundry Global Standard / Provisioned | Any Microsoft Foundry region worldwide | Not EUDB. Azure Policy can block this type. |
| Claude / Anthropic on Foundry (2026) | Anthropic-managed path; no EU data zone comparable to Azure OpenAI | Not “Hosted on Azure means EU zone”. Read the model card. |

## How to use this split

Write three sentences, not one. Copilot Flex Routing off ≠ Foundry Data Zone ≠ Global. A green Copilot score does not cover a Global model endpoint. If Foundry is forbidden on personal data, write that down and enforce it in Azure Policy.

This is not legal advice and not a model-card legal review.