Is Claude in Microsoft 365 Copilot covered by the EU Data Boundary?

Not yet. Microsoft's Learn page, updated 4 November 2026, says Claude models in Microsoft Copilot, Researcher, Copilot Studio, Power Platform and Copilot in Microsoft 365 apps are currently excluded from the EU Data Boundary and, when applicable, from in-country processing commitments.

Microsoft says by the end of 2026, for organizations in the EU and EFTA, and that it will share more details closer to availability. No exact date is published.

Will Claude be switched on for us automatically?

No. Microsoft says the setting stays disabled by default in the EU and EFTA. Organizations that already use Claude in Copilot need to take no action: their processing moves into the EU Data Boundary automatically once it is available.

The 5 November announcement covers the EU and EFTA and does not mention the UK. On Microsoft's Learn page, UK tenants have Claude off by default, listed with the EU and EFTA as opt-in regions.

Does the change cover Copilot Cowork?

Yes. Microsoft names Copilot Cowork among the Copilot experiences where Claude models will be processed in the EU Data Boundary for the EU and EFTA.

Do we need to do anything if we already use Claude in Copilot?

Microsoft says no. For organizations already using Claude models in Copilot, processing moves into the EU Data Boundary automatically once it is available.

Who can turn Claude on in Microsoft 365 Copilot?

A member of the AI Administrator or Global Administrator role, in the Microsoft 365 admin center under Copilot settings, AI providers operating as Microsoft subprocessors. Access can be limited to selected users and Entra ID security groups.

Does this change Claude in Microsoft Foundry?

The announcement does not mention Foundry. Microsoft's Foundry page lists Data Zone Standard for Claude in the US data zone only.

Does "Europe" on Standard Compute mean the EU only?

Approved European endpoints are in the EU/EEA, the United Kingdom or Switzerland. Our EU gateway runs in Finland and your account data is stored in Frankfurt.

Does Standard Compute train on our data?

Standard Compute never trains on your prompts or outputs. With a region rule or zero retention turned on, every request goes only to providers that commit not to train on it.

Claude in Microsoft 365 Copilot and the EU Data Boundary

Last updated 9 November 2026

Claude models in Microsoft 365 Copilot are excluded from the EU Data Boundary today, and they are off by default for tenants in the EU, EFTA and the UK. On 5 November 2026 Microsoft announced that by the end of 2026, Claude in Copilot, Copilot Cowork included, will be processed in the EU Data Boundary for organizations in the EU and EFTA. The announcement does not mention the UK.

This page sets out what Microsoft has published, what it leaves open, and the options a company has until the change ships. Microsoft facts come from Microsoft's own blog and Learn pages, checked on 9 November 2026.

Create a company workspaceor write to contact@standardcompute.com

Deutsch Français Nederlands Español Italiano Svenska Norsk Dansk Suomi Polski

Short answers

Is Claude in Microsoft 365 Copilot covered by the EU Data Boundary?: Not yet. Microsoft's Learn page, updated 4 November 2026, says Claude models in Microsoft Copilot, Researcher, Copilot Studio, Power Platform and Copilot in Microsoft 365 apps are currently excluded from the EU Data Boundary and, when applicable, from in-country processing commitments.
When will it be?: Microsoft says by the end of 2026, for organizations in the EU and EFTA, and that it will share more details closer to availability. No exact date is published.
Will Claude be switched on for us automatically?: No. Microsoft says the setting stays disabled by default in the EU and EFTA. Organizations that already use Claude in Copilot need to take no action: their processing moves into the EU Data Boundary automatically once it is available.
What about the UK?: The 5 November announcement covers the EU and EFTA and does not mention the UK. On Microsoft's Learn page, UK tenants have Claude off by default, listed with the EU and EFTA as opt-in regions.

What Microsoft has published, and when

Claude in Microsoft 365 Copilot: Microsoft's published statements
Date	Microsoft page	What it says
3 April 2026	Microsoft page: Learn: Claude models in Microsoft Online Services	What it says: A new admin setting in the EU, EFTA and UK, Copilot in Microsoft 365 apps with Anthropic models, to make Anthropic the default model for Copilot in Microsoft 365 apps
4 November 2026 (page update)	Microsoft page: Learn: Claude models in Microsoft Online Services	What it says: Claude models in Copilot are currently excluded from the EU Data Boundary; EU, EFTA and UK tenants have them off by default
5 November 2026	Microsoft page: Copilot blog	What it says: By the end of 2026, Claude in Copilot, Copilot Cowork included, is processed in the EU Data Boundary for the EU and EFTA; off by default there; existing users move automatically

Sources are listed at the end of this page, checked on 9 November 2026. Microsoft says it will share more details closer to availability.

What the announcement leaves open

The UK. The post names the EU and EFTA only. UK tenants have Claude off by default today, and Microsoft has published nothing on when UK processing would change.

The exact date and the full list of products. The commitment is "by the end of 2026", and the post names Copilot experiences such as Copilot in Microsoft 365 apps and Copilot Cowork. Until Microsoft updates its Learn page, its current text, that Claude is excluded from the EU Data Boundary, is the statement a security reviewer will read.

Models with separate terms. Microsoft lists some advanced models, such as Claude Fable 5, as Anthropic models with Data Retention: off by default everywhere, under Anthropic's own commercial terms and data processing addendum, where, in Microsoft's words, "Anthropic acts as an independent processor". The announcement does not mention these models.

In-country processing. The post describes processing within the EU Data Boundary. It does not say that Claude processing will happen in a particular country.

Claude in Microsoft Foundry is a separate route

Developers who call Claude through Microsoft Foundry are not covered by the Copilot announcement, which does not mention Foundry. Microsoft's Foundry page lists Claude on Global Standard deployments, and on Data Zone Standard in the US data zone only. It lists no EU Data Zone for Claude.

Foundry offers Claude in two versions, hosted on Azure or hosted on Anthropic's infrastructure outside Azure, billed through the Azure Marketplace. Microsoft says that Claude models Anthropic sells and operates are Non-Microsoft Products under its Product Terms.

Where Claude is processed, by route
Route	Processing, as published	Default for EU tenants
Microsoft 365 Copilot, today	Processing, as published: Outside the EU Data Boundary	Default for EU tenants: Off in the EU, EFTA and UK
Microsoft 365 Copilot, announced for the end of 2026	Processing, as published: Inside the EU Data Boundary for the EU and EFTA	Default for EU tenants: Off in the EU and EFTA
Microsoft Foundry	Processing, as published: Global Standard, or Data Zone Standard in the US; no EU Data Zone listed for Claude	Default for EU tenants: Your own deployment
Standard Compute with a Europe rule	Processing, as published: Approved European inference endpoints; EU gateway in Finland	Default for EU tenants: A rule you set for the company, a team or a key

Microsoft rows from Microsoft's Learn and blog pages, checked on 9 November 2026.

What a company can do before the change ships

Wait, with Claude off. EU and EFTA tenants that leave the setting off change nothing. Once processing moves, an admin can turn Claude on for everyone or for chosen groups.

Turn it on now for chosen groups. An AI Administrator or Global Administrator can enable Anthropic under AI providers operating as Microsoft subprocessors in the Microsoft 365 admin center, for all users or for selected users and Microsoft Entra ID security groups. Until the change ships, that processing is outside the EU Data Boundary, so record the decision in your data protection impact assessment and your records of processing.

Give developers and agents Claude through an API route with European processing. Copilot covers people working in Microsoft 365. Agents, internal tools, Claude Code and Claude Desktop reach Claude through an API, and that route has its own processing location and terms.

Claude with processing in Europe through Standard Compute

Standard Compute is one option for that API route. Set a Europe rule for your company, a team or a single key, and every request, including retries and fallbacks, is served only by approved European inference endpoints. If no European endpoint can serve it, the request is refused before your prompt is sent.

Claude Opus 5.5, Sonnet 5.5 and Haiku 5.5 are served in Europe by Google Vertex AI and Amazon Bedrock in Ireland. Our EU gateway terminates TLS and runs in Finland, and your account data is stored in Frankfurt.

Employees sign in to Claude Desktop and Claude Code with their Microsoft work account, through our EU gateway, so there are no API keys to hand out. Access follows your Microsoft Entra groups through SCIM provisioning.

Sign our Data Processing Agreement in the dashboard in minutes. It commits us to no training on your data, no retention of your content, and breach notification within 72 hours.

Standard Compute dashboard, Claude Microsoft sign-in setup: step 2 of 4, connecting Microsoft Entra provisioning with a tenant URL and a provisioning credential. — Setting up Claude sign-in with Microsoft work accounts in the Standard Compute dashboard. The company shown is example data.

Questions from IT, security and procurement

Does the change cover Copilot Cowork?: Yes. Microsoft names Copilot Cowork among the Copilot experiences where Claude models will be processed in the EU Data Boundary for the EU and EFTA.
Do we need to do anything if we already use Claude in Copilot?: Microsoft says no. For organizations already using Claude models in Copilot, processing moves into the EU Data Boundary automatically once it is available.
Who can turn Claude on in Microsoft 365 Copilot?: A member of the AI Administrator or Global Administrator role, in the Microsoft 365 admin center under Copilot settings, AI providers operating as Microsoft subprocessors. Access can be limited to selected users and Entra ID security groups.
Does this change Claude in Microsoft Foundry?: The announcement does not mention Foundry. Microsoft's Foundry page lists Data Zone Standard for Claude in the US data zone only.
Does "Europe" on Standard Compute mean the EU only?: Approved European endpoints are in the EU/EEA, the United Kingdom or Switzerland. Our EU gateway runs in Finland and your account data is stored in Frankfurt.
Does Standard Compute train on our data?: Standard Compute never trains on your prompts or outputs. With a region rule or zero retention turned on, every request goes only to providers that commit not to train on it.

Sources

Microsoft: bringing Claude models in Microsoft Copilot into the EU Data Boundary (5 November 2026), checked 2026-11-09
Microsoft Learn: Claude models from Anthropic in Microsoft Online Services (updated 4 November 2026), checked 2026-11-09
Microsoft Learn: Claude models in Microsoft Foundry, checked 2026-11-09

Create a company workspace, set a Europe rule and connect Microsoft Entra ID so your people sign in to Claude with their work accounts.

Create a company workspace