UK Microsoft 365 administrators who have not decided on Anthropic’s Claude models may soon find that Microsoft has made one for them. On Dec. 9, Claude access will be switched on by default in qualifying UK Copilot tenants.
Microsoft’s change affects who can use Claude through Copilot, not a mandatory replacement of the AI model behind every Copilot response. It also removes a narrower setting that allowed Claude only in Microsoft 365 apps, expanding that permission to all users unless administrators act.
For UK MSPs, resellers, and enterprise IT partners, the deadline creates immediate work reviewing tenant configurations, discussing data-processing requirements with clients, and explaining which employees will gain access.
Microsoft will change two UK Copilot access settings
According to Microsoft’s Nov. 10 Message Center notice, MC1546435, UK organizations that have never selected an Anthropic subprocessor setting will have Claude models enabled for all users on Dec. 9, 2026. The company will also retire the option limiting Claude to Copilot features within Microsoft 365 apps.
The outcome depends on how a tenant is configured today:
| Current Anthropic setting | What happens Dec. 9 |
| No selection recorded | Claude access becomes available to all users |
| Claude allowed only in Microsoft 365 apps | Setting is retired; access changes to All users |
| No users, or specific users and groups | Existing choice remains in effect |
| All users | Existing access continues |
Administrators can still change these choices after Dec. 9. However, customers who do not want access expanded automatically should update their settings before the switch.
The change makes Claude available across supported Copilot experiences, including Copilot Studio, but does not mean every Copilot interaction will use Claude. Microsoft’s technical documentation explains that some experiences let users select a model, while Copilot Studio creators choose models when building agents. Anthropic models with separate data-retention terms remain subject to an additional opt-in.
The UK’s data-processing position differs from the EU’s
The location matters as much as the default. Microsoft has announced that Claude processing for eligible EU and European Free Trade Association customers will move into its EU Data Boundary by the end of 2026. UK tenants are outside that arrangement.
The Register reported that relevant Claude processing for UK Copilot tenants takes place in the United States. Microsoft says its enterprise data protection, Product Terms, and Data Protection Addendum cover Claude operated as a Microsoft subprocessor, subject to documented exceptions. The company also says customer data used within these protected Copilot experiences is not used to train foundation models.
Processing outside the UK does not automatically make a service noncompliant. The UK’s Information Commissioner’s Office explains that the UK-US data privacy framework extension permits certain transfers to eligible US organizations; other appropriate safeguards may be relevant. Partners should confirm the applicable transfer mechanism and contractual commitments rather than assume the EU Data Boundary covers UK clients.
For an MSP supporting customers in London and Dublin, for example, two tenants may receive a similar December access change while their regional processing commitments differ. The right configuration depends on each customer’s contracts, data classification, and approval process. UK channel partners have already been navigating Copilot data-residency and AI-governance concerns during deployments.
What UK MSPs and resellers should do before Dec. 9
For MSPs administering multiple Microsoft 365 tenants, the default change creates a practical customer-management task. An unchanged default can broaden employee access before a customer’s security or compliance teams have reviewed the provider.
Partners should prioritize three checks:
- Audit tenant selections: In the Microsoft 365 admin center, go to Copilot > Settings > View all > AI providers operating as Microsoft subprocessors > Anthropic.
Select No users to disable access or Specific users and groups for a controlled rollout, then save. The change requires an AI Administrator or Global Administrator role.
- Review customer data commitments: Confirm where Claude processing occurs, which workloads and data types are approved, and whether existing transfer assessments or supplier reviews need updating.
Pay particular attention to clients with UK-only processing requirements or tighter sector-specific controls.
- Prepare users and support teams: Tell clients whether their access will change, document their approval, and brief helpdesks on model selection and new Copilot capabilities.
For agents built in Copilot Studio, check which approved users can build or run experiences that rely on Claude.
The tenant reviews also create a concrete service opportunity. Partners can offer tenant-by-tenant assessments, restricted pilots, policy updates, and ongoing monitoring rather than treating Claude as another license to resell. The broader shift toward governed Microsoft AI deployments makes those services relevant beyond the December change.
The deadline is an access-control decision, not a requirement for every organization to adopt Claude. UK partners that can document who may use it, where data is processed, and what the customer approved will be better prepared for Dec. 9 than those who leave existing settings unchecked.
Also read: Managing Microsoft Copilot for your clients? Learn how to plan deployments, address data security concerns, and improve adoption with our practical Microsoft Copilot guide for MSPs.