Microsoft will move Anthropic’s Claude models in Copilot into its EU Data Boundary by the end of 2026, closing a regional-processing gap that has kept some European organizations from enabling the models.
The November 5 announcement covers eligible customers in the European Union and European Free Trade Association. Microsoft says Claude processing will move inside the boundary automatically for organizations already using it, with no separate purchase or opt-in for the regional commitment. The company has not given a more precise rollout date.
That timing matters. Microsoft’s current product documentation still classifies Claude models in Copilot, Researcher, Copilot Studio, Power Platform and Microsoft 365 apps as outside the EU Data Boundary. Administrators should therefore treat the change as a year-end commitment, not evidence that every Claude request is regionally processed today.
What Microsoft is changing
The new Microsoft commitment covers Claude across Copilot experiences, including Copilot Cowork. Once the rollout reaches an eligible tenant, prompts and other customer data sent to Claude should be processed within the EU Data Boundary, where Microsoft says the related customer data is already stored.
Claude already operates as a Microsoft subprocessor in these products. That puts its use under Microsoft’s Product Terms and Data Protection Addendum rather than requiring every customer to contract directly with Anthropic. Microsoft also applies its enterprise data protection rules: prompts, responses and Microsoft Graph data are not used to train the foundation models, and tenant administrators choose who can use Claude.
Organizations that have already enabled Claude should not need to change a setting when regional processing becomes available. For new deployments, Claude remains disabled by default in EU and EFTA tenants. An AI Administrator or Global Administrator can enable it for everyone or restrict access to selected users and Microsoft Entra ID groups.
The announcement does not include the UK
Microsoft’s present Claude controls group the EU, EFTA and United Kingdom together because all three currently have the models disabled by default and outside relevant regional commitments. The November 5 announcement, however, promises EU Data Boundary processing only for the EU and EFTA.
That boundary covers the 27 EU member states plus Iceland, Liechtenstein, Norway and Switzerland. Microsoft did not extend the new commitment to UK tenants or announce a separate UK processing date. Organizations operating across both regions should not assume that one year-end change resolves both sets of residency requirements.
Storage, processing and data access are different controls
The change is primarily about where inference processing occurs. Microsoft 365 already stores Copilot interaction history, including prompts, responses and citations used for grounding, according to the same contractual commitments that apply to an organization’s other Microsoft 365 content. Moving Claude inference into the boundary aligns the processing location with that storage commitment.
It does not reduce what Copilot can retrieve. Copilot can ground an answer in documents, email, calendars, chats, meetings and contacts available through Microsoft Graph. Microsoft says the service respects each user’s existing permissions, but an overly broad SharePoint site, Teams workspace or shared file remains overly broad when an AI assistant can search it quickly. Data residency does not repair access governance.
The EU Data Boundary also is not an absolute promise that every operational identifier stays in-region. Microsoft’s boundary exceptions documentation says approved AI subprocessors may process or store a pseudonymized user ID or session identifier outside the boundary for troubleshooting, security and debugging. It says prompts, responses and other customer data remain inside unless product documentation discloses otherwise.
Tenants that allow Microsoft’s flex-routing option have another exception to review: during peak demand, Copilot prompts, responses and grounding data may be processed in the United States, Canada or Australia. An organization that requires strict regional inference should verify that routing choice separately rather than treating the Claude migration as a blanket answer.
Two Microsoft 365 controls can affect Claude access
Microsoft currently documents a global control for “AI providers operating as Microsoft subprocessors” and a narrower setting for Anthropic models in Word, Excel and PowerPoint. The app-specific setting does not govern Claude use elsewhere in Copilot, and the global provider setting can override whether the narrower control is available.
For the global control, administrators go to Microsoft 365 admin center > Copilot > Settings > View all > AI providers operating as Microsoft subprocessors. They can then enable Anthropic and scope it to all users or selected groups. Microsoft’s current Claude administration guide notes that these assignments apply across Copilot and Copilot Studio experiences.
The separate Microsoft 365 apps control governs whether Claude can be the default model for supported experiences in Word, Excel and PowerPoint. Tenant creation date can affect its initial state, so administrators should inspect the live setting and Message Center rather than rely on a remembered default.
What administrators should do before the migration
- Record the current state. Export or screenshot the Anthropic provider setting, app-specific control, assigned users and groups, and any separate model options. This creates a defensible before-and-after record.
- Map the affected experiences. Identify whether users access Claude through Copilot Chat, Microsoft 365 apps, Cowork, Researcher, Copilot Studio, Power Platform or another product. Do not assume one control covers every route.
- Check tenant geography. Confirm that the tenant qualifies under the EU or EFTA commitment. Treat UK workloads separately until Microsoft publishes a UK-specific change.
- Wait for rollout evidence. Watch Microsoft 365 Message Center and the Claude product documentation for a tenant-specific date. The present documentation still says Claude is outside the boundary.
- Review routing and subprocessors. Check whether flex routing is enabled, document the Anthropic subprocessor relationship and record any permitted operational-data transfers.
- Re-audit permissions. Use SharePoint and Teams access reviews, sensitivity labels and Microsoft Purview controls to find content that users can access but should not expose to broad Copilot retrieval.
- Update compliance records. Revise data-flow maps, processor inventories, risk assessments and data-protection impact assessments only after the processing change is active for the tenant.
- Run a controlled validation. Start with a limited group, test the required Copilot experiences, confirm audit and retention behavior, and preserve the Microsoft notice or service documentation that establishes the effective boundary.
Why the year-end switch matters
Microsoft has offered Claude inside its governed Copilot environment while warning European customers that Anthropic processing sat outside the EU boundary. That left security and compliance teams choosing between a preferred model and a regional-processing commitment already applied to other parts of Microsoft 365.
The year-end change removes that specific tradeoff for eligible EU and EFTA tenants. It does not remove the need to control who can invoke Claude, which organizational data Copilot can retrieve, how agents and connectors handle data, or which documented transfers remain permitted. Those are separate architecture and governance decisions, and they remain in the administrator’s hands.
