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

Microsoft says Claude models in Microsoft Copilot will be processed inside the EU Data Boundary for organizations in the European Union and the European Free Trade Association by the end of 2026. Charles Lamanna, executive vice president, Copilot, Agents, and Platform, published that on the Microsoft Copilot blog on 5 November 2026. Microsoft Source EMEA repeated the commitment in German on 6 November and linked that English post as the original.

What Microsoft promised

The blog says EU and EFTA organizations will be able to use Claude across Copilot experiences, including Copilot Cowork, with processing inside the EU Data Boundary, in the region where their data is already stored. It says Claude models already power work in Chat, Copilot in Microsoft 365 apps, Copilot Cowork, and Copilot Code. It says Claude in Copilot is covered by Microsoft’s enterprise data protection, and that customer data is not used to train generative AI foundation models. The German page lists the same four surfaces and the same training limit.

The post names no day inside 2026. It says Microsoft will share more details closer to availability. It also says organizations that want finer control can store Microsoft 365 data at rest in their own country, in 10 countries in the EU and EFTA. That sentence is about Microsoft 365 data at rest. The boundary promise for Claude is the EU and EFTA region. The post does not say Claude processing will be limited to one country.

What admins do now

In the EU and EFTA, the blog says the Claude setting is disabled by default. An admin enables it for all users, or for selected users and groups, in the Microsoft 365 admin center. Organizations that already use Claude are told to take no action. Once the processing is available, it moves into the EU Data Boundary automatically. The German page says the same, including that those organizations need no further steps for the later switch.

Enabling the setting and moving the processing are two different moments. The blog says organizations that have not enabled Claude can turn it on at any time, with processing moving into the boundary once that processing is available.

The page Lamanna points to for details still describes the service as it stands. Claude models from Anthropic in Microsoft Online Services, dated 4 November 2026, said on 8 November that 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, where it applies, from in-country processing commitments. It says customers in the EU Data Boundary and in the United Kingdom have Claude disabled by default. The 5 November promise does not add the United Kingdom. Learn says the current opt-in is Copilot, then Settings, then AI providers operating as Microsoft subprocessors, and that it takes an AI Administrator or a Global Administrator.

The same Learn page keeps a separate switch for what it calls Anthropic models with Data Retention, with Claude Fable 5 and Claude Mythos 5 as examples, under Anthropic’s own terms. It also says some Fable-class models can be offered with Anthropic acting as a Microsoft subprocessor. The 5 November post does not say which of those classes are in the boundary commitment.

Regulated Copilot work, including Copilot for legal, still has to be matched to the commitment on the model that is enabled. The EU AI Office information requests to OpenAI and Anthropic ask about the providers, not this admin center toggle.

Why this matters

An EU or EFTA admin who turns Claude on is using the control Microsoft documents now, and the Learn page dated 4 November 2026 still called those deployments excluded from the EU Data Boundary when opened on 8 November. The 5 November blog places the processing move at the end of 2026 and says tenants that already enabled Claude move automatically once that processing is available, with no extra migration step named. Microsoft’s line that customer data is not used to train generative AI foundation models is the training commitment the blog states, and the blog states the region as a separate EU Data Boundary commitment with that end-of-2026 date. A processing record that needs the region has to carry the date, because the announcement describes a future move.