Microsoft will move Claude processing in Copilot inside its EU boundary by year-end
Existing users will move automatically once the change is available. Claude access remains off by default for EU and EFTA organizations.
Loading page…
Existing users will move automatically once the change is available. Claude access remains off by default for EU and EFTA organizations.
Listen to this story
Microsoft plans to extend its EU Data Boundary commitment to Claude workloads in Copilot by the end of 2026, covering processing as well as storage for EU and EFTA customers. Claude already serves Copilot Chat, Microsoft 365 apps, Copilot Cowork and Copilot Code, so this is a regional-handling change, not a new model launch. Existing users will move automatically once the change is available; organizations not yet using Claude can enable it now, but the processing move has no exact availability date and access remains administrator-controlled.
Claude access is disabled by default in the EU and EFTA; administrators can enable it for everyone or selected users and groups.
The EU Data Boundary covers the EU and EFTA; Microsoft separately offers in-country storage for Microsoft 365 data at rest in 10 countries.
Microsoft says Claude is already covered by enterprise data protection, including a commitment not to use customer data to train generative AI foundation models.
European organizations using Claude through Microsoft Copilot are set to gain a regional commitment covering where their AI requests are processed. Microsoft said on November 5 that it will bring those models inside its EU Data Boundary by the end of 2026, including for Copilot Cowork. The change is promised, not yet available.
Microsoft’s EU Data Boundary is its commitment to store and process data for Microsoft 365 and other online services within the European Union and European Free Trade Association, or EFTA. The planned extension brings Anthropic’s Claude models under that regional processing commitment for organizations in both groups.
The distinction is between keeping data in a region and carrying out the model’s work there. Microsoft says these customers’ data is already stored within the boundary. By year-end, Claude processing across Copilot experiences will take place there too. Claude will join other models, including Microsoft-operated models, already processing data within it.
This is not a first introduction of Claude to Copilot. Microsoft says Claude already powers work in Copilot Chat, Microsoft 365 apps, Copilot Cowork and Copilot Code. The announcement changes the regional commitment attached to that access, rather than introducing a new model or a new task for users.
Microsoft describes two routes into the change, depending on whether an organization already uses Claude. Neither requires customers to initiate the processing move themselves. Access to Claude, however, remains a separate administrator decision: its setting is disabled by default in the EU and EFTA.
Enabling Claude before the transition therefore does not bring the future regional processing commitment forward. Microsoft gives an end-of-2026 deadline, but no specific availability date. It says it will share more details closer to availability.
Microsoft says Claude models in Copilot already fall under its enterprise data protection. Customer data is not used to train generative AI foundation models, and administrators control who can use Claude. Those protections are distinct from the newly promised location of processing; they do not begin with the regional move.
For eligible Microsoft 365 customers in the EU and EFTA, the EU Data Boundary is included in contractual terms without a separate opt-in or additional purchase. That statement concerns the boundary commitment, not a new offer of free Claude access. Microsoft describes it as a company commitment that goes beyond current regulatory requirements.
Microsoft positions the extension as useful for regulated industries and public-sector organizations addressing compliance requirements. Its stated goal is to let European customers choose Claude without giving up the regional processing commitments they rely on elsewhere in Microsoft’s services.
Loading discussion...
Join the conversation
Explain how much processing location would influence your choice.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.