Skip to content
Claude moves from outside to inside the EU Data Boundary by the end of 2026 Two boxes. The left box, labeled inside the EU Data Boundary, already holds Microsoft's own models and a dashed placeholder chip for Claude models marked incoming. The right box, labeled outside the EU Data Boundary today, holds a solid chip for Claude models with the note EU, EFTA, and UK are off by default. A dashed arrow runs from the right box to the left box, labeled by the end of 2026, showing the committed but not yet shipped move. Claude is crossing the EU Data Boundary Announced Nov 5, 2026. Not live yet. Outside the boundary, today Claude models EU, EFTA, and UK: off by default Opt in today and processing still runs outside the EU Data Boundary No fixed ship date Inside the EU Data Boundary Microsoft's own models Claude models (incoming) Already-enabled tenants migrate automatically, no admin action by the end of 2026
Guideintermediate

Claude in Microsoft 365 Copilot and the EU Data Boundary: what actually changed

Published November 6, 2026 · by

The short version

Microsoft says Claude models in Copilot are moving inside the EU Data Boundary. We pulled the Nov 5, 2026 announcement and the admin docs to find what already works, what is still outside the boundary, and the exact setting EU and EFTA admins need to flip.

Table of Contents

Claude in Microsoft 365 Copilot and the EU Data Boundary: what actually changed

Microsoft told European Copilot admins on November 5 that Claude models are moving inside the EU Data Boundary. One day earlier, the Microsoft Learn page that governs the actual setting still read: Claude models "are currently excluded from the EU Data Boundary." Both statements are true, and the overlap between them should worry anyone about to write "resolved" next to this line item in a risk register.

What the EU Data Boundary actually is

The EU Data Boundary is a Microsoft contractual commitment, not a regulation. For eligible Microsoft 365 customers in the EU and the European Free Trade Association, it's baked into the contract terms at no added cost: Customer Data and pseudonymized personal data for in-scope services get stored and processed inside the EU and EFTA. Organizations that want tighter control can layer in-country data residency on top, available today in 10 EU/EFTA countries.

Claude was never part of that commitment. Anthropic joined Microsoft as a formal subprocessor on January 7, 2026, which is the event that made Claude a default model option across Copilot Chat, Copilot in Word, Excel, and PowerPoint, Copilot Studio, and Researcher. That subprocessor move came with an explicit carve-out: per the connect-to-ai-subprocessor documentation (last updated November 4, 2026), Claude models "are currently excluded from the EU Data Boundary, and when applicable, in-country processing commitments." Customers in the EU, the EFTA, and the UK get the Anthropic toggle set to Off by default, specifically because of that gap.

What the November 5 announcement commits to, and what it doesn't

Charles Lamanna, Microsoft's EVP for Copilot, Agents, and Platform, published the change under his own name on the Microsoft 365 blog. Strip the framing. By the end of 2026, organizations in the EU and the EFTA will be able to run Claude models across Copilot experiences, including Copilot Cowork, with processing inside the EU Data Boundary. Tenants that already have Claude enabled won't need to do anything; once the capability ships, their traffic moves into the boundary automatically. Tenants that haven't opted in yet can still flip the switch today, with the same automatic migration once it's available.

What it isn't: a shipped feature. The post gives no date firmer than "by the end of 2026" and closes with "we'll share more details as we get closer to availability." If your DPIA update is waiting on a specific go-live date, you don't have one yet. You have a public commitment from a named Microsoft executive, which is worth more than a rumor, but it's still a line on a roadmap.

The setting you'd actually touch

If an EU or EFTA tenant wants Claude available today, ahead of the boundary move, the path is documented and narrow. You need the AI Administrator or Global Administrator role. From there:

  1. Microsoft 365 admin center -> Copilot -> Settings -> View all.
  2. Select AI providers operating as Microsoft subprocessors.
  3. Under Available subprocessors for your organization, select Anthropic, then Save.
  4. Under Choose who can access Anthropic models for Copilot and generative AI experiences, assign users or groups, then Save.

That's the entire admin lift. Claude runs under Microsoft's own Product Terms and Data Protection Addendum once it's enabled this way, so there's no separate Anthropic contract to negotiate. Microsoft's enterprise data protection terms apply on top: customer data isn't used to train Anthropic's foundation models, and admins scope access by user or group rather than flipping it on for the whole tenant at once.

One wrinkle the docs call out directly: if your organization opted into Claude earlier under Anthropic's old, separate commercial terms (the pre-subprocessor arrangement), that opt-in doesn't carry over. The toggle defaults back to Off for EU, EFTA, and UK tenants, and you opt in again through the admin center path above.

Today versus the committed end state

Claude defaultProcessing location if you opt in todayAfter the EU Data Boundary coverage ships
Commercial, outside EU/EFTA/UKOnStandard Microsoft/Anthropic processingNo change, not the subject of this announcement
EU and EFTAOffOutside the EU Data BoundaryMoves inside the boundary automatically, per the Nov 5 post
UKOffOutside the EU Data BoundaryNot named in the Nov 5 commitment

Source: Microsoft 365 blog, Nov 5, 2026 and connect-to-ai-subprocessor docs, updated Nov 4, 2026.

The UK row is the one worth sitting with. UK tenants sit in the same "off by default, excluded from in-country commitments" bucket as EU and EFTA tenants today, for the same reason: Anthropic's processing happens outside Microsoft's regional guarantees. But the November 5 post names only "the European Union (EU) and the European Free Trade Association (EFTA)." It says nothing about the UK joining the boundary. A UK compliance team reading the headline and assuming inclusion would be reading past what Microsoft actually wrote.

A second wrinkle sits one layer down. Certain newer Anthropic models, flagged in the docs as "Anthropic models with Data Retention," run under Anthropic's own separate commercial terms and data processing agreement rather than Microsoft's standard DPA, and they need their own opt-in regardless of what the base Claude toggle is set to. Nothing in the November 5 post suggests that class of model moves inside the boundary on the same timeline, or at all.

What an EU or EFTA Copilot admin should actually do this week

Don't write "Claude is EU Data Boundary compliant" into a risk register yet. It isn't, not today, and the gap between the announcement and the docs update (one calendar day, and the docs still say excluded) is a reminder that Microsoft's own compliance pages lag its press cycle. Write instead: "Microsoft has committed, by end of 2026, to moving Claude processing inside the EU Data Boundary for already-enabled and newly-enabled tenants; current processing for EU/EFTA tenants that opt in sits outside the boundary; UK is not part of this specific commitment."

If your organization has a real use case for Claude in Copilot and your data-residency posture can tolerate processing outside the EU for a few more months, opt in now through the admin center path above; you'll be migrated automatically once the capability ships, with no second configuration pass. If residency inside the EU Data Boundary is a hard requirement today, leave the toggle off and revisit it when Microsoft names an actual date, not a quarter. Either way, check the connect-to-ai-subprocessor page yourself before the next audit; it's the one document in this chain that Microsoft actually keeps current, usually within a day of any real change.