Claude in Microsoft Copilot joins the EU Data Boundary by end of 2026

Microsoft said on November 5, 2026 that Anthropic's Claude models used inside Microsoft Copilot will be processed within the EU Data Boundary by the end of 2026. Organizations in the European Union and the European Free Trade Association will then be able to use Claude across Copilot experiences, including Copilot Cowork, with processing kept inside the same boundary where their Microsoft 365 data is already stored. The announcement was published on the Microsoft Copilot Blog by Charles Lamanna, Executive Vice President for Copilot, Agents and Platform, and it ends a gap that has forced European administrators to choose between Anthropic's models and Microsoft's regional processing commitments.

The change closes an exception that Microsoft documents today in plain terms. Its administrator documentation for Claude in Microsoft Online Services, last updated on November 4, 2026, states that Claude models deployed in Microsoft Copilot, Researcher, Copilot Studio, Power Platform and Copilot in Microsoft 365 apps are "currently excluded from the EU Data Boundary" and, where applicable, from in-country processing commitments. That exclusion is the reason Claude is switched off by default for tenants in the EU, EFTA and the United Kingdom, while most commercial customers elsewhere have it switched on.

Microsoft has not given a precise date beyond "by the end of 2026" and says it will share more details closer to availability. For organizations that already use Claude in Copilot, the company says no action is required: processing will move into the EU Data Boundary automatically once the change is live.

··········

⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣

CLAUDE IN MICROSOFT COPILOT AND THE EU DATA BOUNDARY: WHAT MICROSOFT ANNOUNCED.

The EU Data Boundary is Microsoft's commitment to store and process Customer Data and personal data for its enterprise online services, including Microsoft 365, Azure, Dynamics 365 and Power Platform, inside the EU and EFTA, subject to limited documented exceptions. The boundary covers the 27 EU member states plus the four EFTA countries: Iceland, Liechtenstein, Norway and Switzerland. For eligible Microsoft 365 customers in those countries it is part of the contractual terms, so it requires no opt-in and no additional purchase.

According to the November 5 post, Claude models already power several Copilot surfaces: Copilot Chat, Copilot in the Microsoft 365 apps, Copilot Cowork and Copilot Code. Once the change takes effect, Claude will sit alongside the other models, including Microsoft-operated models, that already process data inside the boundary. Microsoft also restates that Claude in Copilot is covered by its enterprise data protection, that customer data is not used to train generative AI foundation models, and that administrators decide who can use the models.

The announcement also points customers that need tighter control to Microsoft's in-country data residency offering, which lets organizations store Microsoft 365 data at rest in their own country and is available in 10 EU and EFTA countries. Microsoft's post does not say whether Claude processing will also fall under in-country processing commitments, which the current documentation lists as a separate exclusion.

··········

HOW CLAUDE IS PROCESSED IN MICROSOFT COPILOT TODAY FOR EU AND EFTA TENANTS.

Under the current arrangement, Anthropic operates as a Microsoft subprocessor. Microsoft's documentation says the Microsoft Product Terms and the Microsoft Data Protection Addendum apply to Claude used through Microsoft's enterprise online services, that Anthropic works under Microsoft oversight through contractual safeguards, and that the Microsoft Customer Copyright Commitment covers Claude in products such as Microsoft Copilot and Copilot Studio. The contractual protection is in place, yet the processing location has been outside the EU Data Boundary.

That location is spelled out in the Microsoft 365 apps documentation as well. When Anthropic models are used in Copilot experiences in Word, Excel and PowerPoint, Microsoft states that "processing occurs outside the Microsoft EU Data Boundary." This applies even to the dedicated setting that Microsoft introduced on April 3, 2026 for EU, EFTA and UK customers to make Anthropic the default model for Copilot in those three apps. That setting is on by default for tenants in those regions created after March 25, 2026, while older tenants were told to check the Message Center for their default.

Copilot Cowork shows the practical effect most clearly. Microsoft's Cowork FAQ says the agent can use Claude models "for most reasoning, drafting, and tool-using work," and its model picker lists Claude Opus, Claude Sonnet and Claude Fable alongside GPT and Grok models. The same FAQ states that "if your organization is within the EU Data Boundary, only GPT models are supported." For a European organization that keeps strict EU processing in place today, Cowork therefore runs on a narrower set of models than the one offered to customers in the United States.

··········

CLAUDE IN COPILOT BEFORE AND AFTER THE EU DATA BOUNDARY CHANGE.

The table below compares the situation documented by Microsoft today with the situation Microsoft describes for the end of 2026. The "after" column only contains what the November 5 announcement states; items Microsoft has not addressed are marked as such.

........

Item	Today (EU and EFTA tenants)	After the change (by end of 2026)
Processing location for Claude in Copilot	Outside the EU Data Boundary	Inside the EU Data Boundary
Default setting for Claude	Off ("No users")	Off by default
Tenants already using Claude	Processing outside the boundary	Moved inside automatically, no action
Copilot Cowork on Claude	Only GPT models under the boundary	Claude available within the boundary
Contract terms	Product Terms and DPA, Anthropic as subprocessor	Enterprise data protection, no training on data
In-country processing commitments	Claude excluded	Not addressed in the announcement
Exact availability date	Not applicable	Not announced, details to follow

........

The first row is the substantive change. Contract terms, data protection and default settings stay as they are; the location where Claude requests are processed is what moves, and that is the property many European compliance teams require before approving a new AI provider for regulated or sensitive work.

··········

[[ADPLUS_300x250_1]]

WHAT CHANGES FOR MICROSOFT 365 ADMINS IN THE EU AND EFTA.

Administrators fall into two groups. Tenants that already enabled Claude, having accepted processing outside the EU Data Boundary, need to do nothing: Microsoft says their processing will move into the boundary automatically. Tenants that kept Claude disabled can turn it on at any time, but until the change is live, enabling it still means Claude requests are processed outside the boundary.

The control sits in the Microsoft 365 admin center and requires the AI Administrator or Global Administrator role. Microsoft's documented path is Copilot, then Settings, then View all, then "AI providers operating as Microsoft subprocessors." There, an administrator selects Anthropic under "Available subprocessors for your organization," saves, and then chooses which users or groups can access Anthropic models for Copilot and generative AI experiences. Access can be scoped to specific users or Microsoft Entra ID security groups, and Microsoft says those assignments are enforced across Microsoft Copilot and Copilot Studio. Copilot Studio and Power Platform also need a separate allowance in the Power Platform admin center once Anthropic is enabled in the Microsoft 365 admin center.

Two older configurations deserve a check before the change arrives. Microsoft decommissioned the separate Anthropic independent processor setting on May 1, 2026, so tenants that relied on it lose access unless Anthropic is enabled as a Microsoft subprocessor. EU, EFTA and UK organizations that had opted in under Anthropic's own commercial terms and data protection addendum were told they must opt in again, with the toggle set to Off by default. Eligibility also depends on how the tenant was set up: Microsoft 365 customers are in scope of the EU Data Boundary when their sign-up location is in the EU or EFTA, and customers that bought Multi-Geo Capabilities are not in scope even when their tenant country is in the EU or EFTA.

Licensing does not change with this announcement. Readers comparing Copilot plans can find the seat and plan structure in our guide to Microsoft Copilot pricing tiers and Microsoft 365 plans, and the model line-up in our overview of the models available in Microsoft Copilot.

··········

CLAUDE AVAILABILITY IN MICROSOFT COPILOT BY REGION AND CLOUD.

The announcement covers the EU and EFTA only. The current regional defaults documented by Microsoft are summarized below, with the announced change shown where it applies.

........

Region or cloud	Claude default today	Effect of the November 5 announcement
Commercial cloud outside EU, EFTA and UK	On for most customers	None
EU and EFTA	Off, admin opt-in	Processing moves inside EU Data Boundary
United Kingdom	Off, admin opt-in	Not mentioned
GCC, non-federal customers	Available via setting since July 22, 2026	None
GCC federal, GCC High, DoD, sovereign clouds	Not available	None

........

The United Kingdom is the most visible gap. UK tenants share the EU and EFTA default of Claude switched off, but the UK is outside the EU Data Boundary and the November 5 post does not mention it, so UK organizations have no announced change to plan around.

··········

⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁤

CLAUDE DATA-RETENTION MODELS AND OTHER POINTS THE ANNOUNCEMENT LEAVES OPEN.

Microsoft distinguishes standard Claude models from "Anthropic models with Data Retention," and the distinction is relevant for European buyers. Data-retention models are off by default for every tenant, require an explicit opt-in, and run under Anthropic's own commercial terms and data protection addendum with Anthropic acting as an independent processor. Microsoft's documentation says Anthropic stores most inputs and outputs for these models for up to 30 days, may keep content flagged by its trust and safety classifiers for up to two years and classification scores for up to seven years, and does not use retained data for training without express permission. The Copilot Cowork FAQ names Claude Fable as a model that requires data retention, and the admin documentation adds that eligibility varies: for some organizations Fable 5.1 is available with Anthropic as a subprocessor and no retained content, while other Fable-class models may be offered only under the data-retention terms.

The November 5 announcement speaks of "Claude models" without separating these categories, and it does not say whether data-retention models will be processed inside the EU Data Boundary. Given that their data is stored by Anthropic outside the Microsoft Customer Agreement, European compliance teams should not assume they are covered until Microsoft documents it. The announcement also leaves open whether Claude will be covered by in-country processing commitments, whether the Copilot Studio and Power Platform routes move at the same moment as Copilot Chat and Cowork, and which specific day before the end of 2026 the change takes effect. Questions about what Copilot itself can read inside a tenant are separate from the processing location; our explainer on Copilot permissions and privacy across Microsoft 365 covers that side.

··········

CLAUDE IN MICROSOFT COPILOT AND THE EU DATA BOUNDARY: CONFIRMED FACTS AND OPEN QUESTIONS.

The confirmed part is specific. Microsoft has committed that, by the end of 2026, Claude models used in Copilot experiences, Copilot Cowork included, will be processed within the EU Data Boundary for organizations in the EU and EFTA; existing users move automatically; the Claude setting remains off by default in those regions and is enabled per user or group in the Microsoft 365 admin center; and Claude remains under Microsoft's enterprise data protection with no training on customer data. Until the change is live, Microsoft's own documentation continues to describe Claude in Copilot, Researcher, Copilot Studio, Power Platform and the Word, Excel and PowerPoint integrations as excluded from the boundary.

The open part is equally specific: the exact date, the treatment of data-retention models such as Claude Fable, the status of in-country processing commitments, the sequencing for Copilot Studio and Power Platform, and the absence of any change for UK tenants. For EU and EFTA organizations that held back Claude for data-location reasons, the practical step now is to decide which users and groups should receive access, so the setting can be switched on once Microsoft confirms that processing has moved inside the boundary.

··········

FOLLOW US FOR MORE.

·····

DATA STUDIOS

·····

datastudios.org