AI · 14 November 2026
Microsoft 365 Copilot to enable Claude by default for UK tenants
Microsoft is set to make Anthropic's Claude a default model in Microsoft 365 Copilot for UK tenants, and administrators have until 9 December to review the settings, according to The Register.
What happened
Microsoft is set to enable Anthropic's Claude as an available model within Microsoft 365 Copilot for UK tenants by default, according to reporting by The Register. Tenant administrators have until 9 December to review the relevant access settings before the change takes effect for their organisations.
The reporting notes that Anthropic will process the relevant data in the United States. For UK organisations, that data location is the detail most likely to require attention from IT, legal and compliance teams as they decide whether to keep the default or adjust settings.
Why it matters
This is a clear example of how AI capability now reaches employees through platform defaults rather than deliberate adoption decisions. When a leading productivity suite adds a third-party model to its assistant, the question for organisations shifts from whether to use AI to how access, data handling and oversight are configured across the estate.
For digital transformation leaders, the story is also about operating model. Settings that govern which models staff can reach, and where their prompts and outputs are processed, become governance decisions with direct effects on employees' daily work. Organisations that treat these controls as an IT housekeeping task may find themselves approving capabilities their users are already using.
The Renascence take
Defaults are never neutral. Most readers will focus on the headline change, but the more important variable is the review window: a deadline of 9 December puts the burden on administrators to act before staff have experienced the new capability, or to accept it by inaction.
Opt-out defaults quietly decide what employees experience, and most people will never read the settings page that shaped their tools. Treat the review period as a service-design moment, not a compliance chore. Map which teams would actually use a second model, what they would type into it, and what they would expect to happen to that data. Then set the default deliberately, and tell staff what changed and why.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in AI
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


