Microsoft announced on November 5, 2026 that Claude models from Anthropic will process inside the EU Data Boundary by the end of 2026 for Microsoft Copilot customers in the European Union (EU) and European Free Trade Association (EFTA). Organizations will be able to use Claude across Copilot experiences, including Copilot Cowork.
Today, Microsoft’s documentation lists Claude models in Copilot as excluded from the boundary, and customers in the EU and EFTA have them disabled by default.
Charles Lamanna, executive vice president of Copilot, Agents, and Platform at Microsoft, wrote that customers will no longer have to choose between access to Claude and the regional data-processing commitments they rely on.
What Moves Inside the Boundary
The EU Data Boundary is Microsoft’s commitment to store and process customer data and personal data for its enterprise online services, including Azure, Dynamics 365, Power Platform, and Microsoft 365, inside EU and EFTA countries. Eligible Microsoft 365 customers in those countries get the boundary as part of their contractual terms, Microsoft says, with no opt-in or additional purchase.
Microsoft’s data residency comparison notes that the boundary carries processing commitments, while its other residency offerings mainly cover stored data at rest. The Claude commitment sits on the processing side: Microsoft says processing for the models will happen inside the boundary, where customer data is already stored.
Administrators can enable Claude for all users or for selected users and groups in the Microsoft 365 admin center, where Microsoft keeps it disabled by default in the EU and EFTA. Organizations already using Claude need to take no action, and those that have not enabled it can do so at any time. In each case, processing moves into the boundary once available.
Claude’s Place in Microsoft’s Data Commitments
Claude already powers Copilot Chat and Copilot in Microsoft 365 apps, and it reaches customers through layers of Microsoft commitments, each with its own scope. Anthropic has onboarded as a Microsoft subprocessor, so Microsoft’s Product Terms and Data Protection Addendum apply to Claude models in its online services. Models labeled “Anthropic models with Data Retention” are the exception, off by default and governed by Anthropic’s terms.
Enterprise data protection covers Claude in Copilot, and Microsoft states that customer data is not used to train generative AI foundation models. Processing inside the EU Data Boundary adds a regional commitment to those protections. Other leading models, including Microsoft-operated ones, already process data inside the boundary, and Claude joins them. Microsoft positions the move as help for regulated industries and the public sector as they scale AI.
The boundary’s reach follows tenant setup. Tenants with Multi-Geo Capabilities, a paid add-on that stores data across several geographies, fall outside it even when they sit in the EU or EFTA. Organizations that want data at rest held in one country can use in-country data residency, which Microsoft offers in 10 countries in the EU and EFTA.
What This Means for ERP Insiders
Data location joins model selection. Microsoft is attaching a regional processing commitment to a model from an outside provider. Where a model runs sits alongside capability and cost among the terms European buyers weigh when choosing one.
Platform vendors absorb outside models into their compliance terms. Claude reaches Copilot customers as a Microsoft subprocessor under Microsoft’s data protection terms, and the boundary extends that arrangement. Microsoft presents the result as consistent security, compliance, and governance across the model providers in Copilot.
Tenant setup determines boundary coverage. The boundary applies by sign-up location and excludes tenants that store data across several geographies, an add-on Microsoft positions for multinational organizations that control data location by user. Multinational organizations using it for that purpose sit outside the commitment.
