Microsoft will switch Anthropic's Claude models on by default inside Microsoft 365 Copilot for organizations in the United Kingdom on December 9, and it will do so without a price change, a new subscription tier or a public announcement. The change comes from Message Center post MC1546435, dated November 10, and it applies to managed work accounts only. Microsoft 365 Personal and Family plans are not affected.
The mechanism is a default flip, not a rollout. UK tenants that have never recorded a choice about Anthropic models operating as a Microsoft subprocessor will find Claude available to all users when the date arrives. Tenants that want it off, or limited to named groups, have to say so before then, from the Microsoft 365 admin center under Copilot, Settings, and the AI providers operating as Microsoft subprocessors section. Only AI administrators and global administrators can change that control.
Microsoft is also retiring a narrower setting that let administrators allow Claude inside Copilot within the Microsoft 365 apps while blocking it everywhere else. Tenants sitting on that option move to all users on December 9 as well. After the switch, Claude becomes reachable through the supported Copilot surfaces, including Copilot Studio and the Power Platform. Microsoft's documentation is explicit that this governs access rather than forcing every Copilot response through Claude: some experiences let users pick a model, and Copilot Studio creators choose models when they build agents.
The geographic split is the interesting part. Microsoft explains that Claude models in Copilot, Researcher, Copilot Studio and the Power Platform sit outside the EU Data Boundary, the framework it uses to promise that EU customer data is processed inside the bloc. That is why the default for the EU, the European Free Trade Association and the UK had been set to no users at all, while other commercial regions already had Claude on by default. The UK is not part of the EU Data Boundary, so Microsoft is dropping the UK exception.
Removing the exception has a data-residency consequence. The Register reported that relevant Claude processing for UK Copilot tenants takes place in the United States, which is why the change lands as a compliance question rather than a feature announcement. Microsoft says its enterprise data protection commitments, Product Terms and Data Protection Addendum cover Claude while it operates as a Microsoft subprocessor, subject to documented exceptions, and that customer data in those protected experiences is not used to train foundation models. The company has separately said Claude processing for eligible EU and EFTA customers moves into the EU Data Boundary by the end of 2026.
Two models sit outside the December 9 change. Claude Fable 5 and Claude Mythos 5 carry their own data-retention behavior and are governed by Anthropic's terms rather than Microsoft's data protection commitments. Anthropic retains most inputs and outputs for up to 30 days on those models, and administrators have to enable them separately. Organizations in the EU that previously opted in under Anthropic's standalone commercial terms must opt in again under Microsoft's updated framework.
For UK administrators the practical deadline is December 8. Anyone with a statutory or contractual obligation to keep data in the UK or the EU has one working day less than the notice period suggests, because the setting is a default and defaults are what most tenants keep. Auditing the tenant, deciding whether Claude's US processing fits the organization's data residency posture, and documenting the decision are now ordinary procurement work rather than an AI pilot decision.
The strategic read is that Microsoft is normalizing a multi-model Copilot while carefully preserving a geographic carve-out for its strongest data-residency promise. Claude already runs by default in most commercial regions; the UK is being brought into line, and the EU is being held back not on model quality but on where the inference happens. That is a useful precedent: as agents move from answering questions to taking actions inside business systems, the default setting for a third-party model becomes a governance control, and the vendors that can move data without moving compliance will win the deals.
Comments (0)
Log in to join the discussion
Log InNo comments yet