# Microsoft will switch on Anthropic’s Claude by default for UK Copilot tenants on December 9 > Source: > Published: 2026-11-10 11:47:30+00:00 # Microsoft will switch on Anthropic’s Claude by default for UK Copilot tenants on December 9 Microsoft official logo (public domain, Wikimedia Commons) — CryptoBriefing brand treatment UK administrators who don't pick a setting will find Claude enabled, with data processed in the US and outside the EU Data Boundary [Microsoft](https://cryptobriefing.com/markets/microsoft/) is about to flip a switch for UK businesses using Copilot. Starting December 9, [Anthropic](https://cryptobriefing.com/markets/anthropic/)’s Claude models will be enabled by default for UK Microsoft 365 Copilot tenants whose administrators have not already chosen a setting. Administrators can still turn it off. But silence counts as consent here, which makes December 9 a compliance deadline as much as a product update. ## What changes on December 9 The mechanics are simple. If a UK tenant’s admin has never touched the Claude setting, access will be on when the date arrives. Opting out remains possible at any time. Microsoft says administrators keep the ability to restrict access to these models whenever they choose, both before and after the switch. The bigger catch is where the data goes. Anthropic processes data in the US, and the Claude models do not fall under Microsoft’s EU Data Boundary commitments. Put more plainly: a prompt typed into Copilot by an employee in Manchester could be handled by servers across the Atlantic. For some organizations, that is a non-issue. For others, it touches the exact rules their legal teams spend all year worrying about. There is a second change that is easier to miss. Microsoft is retiring the existing limited-scope access setting on the same date. Tenants that previously granted Claude access to only part of their organization will see those selections converted to broader access for all users, unless admins step in first. A careful pilot for one department could quietly become a company-wide rollout overnight. That detail matters because it affects the admins who were paying attention. The organizations most likely to have used a limited setting are the ones that wanted tight control in the first place. ### AI, tech, and the markets they move—in one daily briefing. Daily. Free. Join 34,000+ readers across crypto, finance, and policy. ## How UK tenants got here Claude first showed up in Microsoft 365 Copilot in September 2025. It started in two applications before spreading more widely across the product. The December change is part of a broader Microsoft push to widen model choice across Copilot services. That list includes Chat, Researcher, Power Platform, and others. Microsoft frames the move as expanding options while keeping its data protection, security, and compliance standards intact. The company’s position is that customers get more models without giving up control. The UK shift also brings British tenants in line with how Copilot already behaves in most other commercial regions. Default-on Claude access is the norm in those markets. The notable exceptions are the EU and EFTA. Tenants in those regions are not being moved to the same default behavior, which leaves the UK on the other side of that line. ## What this means for UK organizations The immediate stakeholders are IT administrators and compliance officers. Their job between now and December 9 is to decide, on purpose, whether US-based processing fits their obligations. Admins have a short checklist. First, confirm whether a Claude setting has already been chosen for the tenant. Second, check whether the limited-scope option was in use. If it was, the retirement of that setting means existing permissions could expand to everyone unless they are changed before the deadline. Third, loop in legal and procurement. Whether US processing is acceptable is rarely a purely technical question. The split between the UK and the EU and EFTA is worth watching. It shows Microsoft drawing different default lines for different regulatory regions, and organizations operating across those borders may end up managing different Copilot behaviors for different offices. For multinational firms, that could mean a UK subsidiary with Claude switched on while a continental sister company stays on the narrower setup. None of this stops a UK organization from saying no. Microsoft has kept the off switch in administrators’ hands, and the company maintains its compliance commitments are unchanged. But the burden has shifted. Before December 9, Claude was something a UK admin had to choose to allow. After it, keeping Claude out is the decision that requires action, and the retirement of the limited-scope setting means even partial approvals need a second look before the date arrives. **Disclosure:** This article was edited by Diego Almada Lopez. For more information on how we create and review content, see our [Editorial Policy](https://cryptobriefing.com/editorial-policy/).