Copilot’s Claude: EU processing planned by year-end

The News, Explained

Microsoft announced on November 5 that Claude processing in Copilot for organizations in the European Union (EU) and European Free Trade Association (EFTA) will move into the EU Data Boundary by the end of 2026. Copilot is Microsoft’s work AI service, while Claude is Anthropic’s AI model family. The plan includes Copilot Cowork, and existing users are due to move automatically once the change becomes available. Source

The EU Data Boundary defines Microsoft’s regional commitments for storing and processing data. It covers EU and EFTA countries, with limited circumstances allowing transfers outside that area. Understanding the commitment therefore requires reading its covered services, data and exceptions together. Source

Current access and the future migration have different conditions. Microsoft’s help documentation currently excludes Claude from EU Data Boundary and applicable in-country processing commitments. Claude access defaults to off in the EU and EFTA. Administrators can enable it now, while the regional processing move takes effect when it becomes available. Source Source

An AI Administrator or Global Administrator can open the AI-provider controls under Copilot settings in the Microsoft 365 admin center, select Anthropic and choose users or groups. These provider controls determine which AI people in the organization can use. Restricting access to specific users or groups applies that access to features or agents relying on the provider. Source

Models labeled “Anthropic models with Data Retention” have separate conditions. Anthropic retains data as an independent processor, and separate terms and explicit administrator enablement apply. The general provider setting and the additional permission for these retention models need separate consideration when assessing contractual and access conditions. Source

OYOPICK’s Take

Combining regional processing commitments with model choice could help organizations that need both an AI suited to their work and compliance with internal data-processing policies. We see value in addressing those requirements together. Whether the plan delivers that value depends on the promised migration becoming available by year-end.

Consider an organization that makes European processing a condition of adoption. It needs to assess current permission to use Claude separately from completion of the migration. A selected-user setting narrows who can use a provider; processing location remains a separate service condition. Keeping those questions distinct gives reviewers a clearer way to assess who may use the model and where the data is processed. Source Source