6 min readBy Michael van Wijhe

Claude in Copilot switches on on 9 December: what should you decide?

Blue Hello Growth cover with the text Claude in Copilot, EU 9.12.2026, below it EU Data Boundary and Microsoft 365

In short

  • You can already switch Claude on in Microsoft 365 Copilot. In the EU it is off by default, because processing has so far happened outside the EU Data Boundary.
  • In early December, that processing moves inside the EU Data Boundary. On 9 December, Microsoft switches Claude on for every organisation in the EU and EFTA that has not made a choice yet, for all users.
  • If you want to decide who gets Claude, or that nobody does yet, set it before 9 December in the Microsoft 365 admin centre. A choice you have already saved stays in place.

Yes, Claude already works in Copilot. An admin can switch on Anthropic's models today, for everyone or for a group. But if you do that now, prompts and files are processed outside the EU Data Boundary until early December. The EU Data Boundary is Microsoft's commitment to process European customers' data inside the EU, and that is why Claude is off by default in the EU (Microsoft Learn).

That changes in December, and that is where 9 December comes from. In early December, processing of Claude in Copilot moves inside the EU Data Boundary. On 9 December, Microsoft then switches Claude on for every organisation that has not chosen anything (Message Center MC1546438). So the question is not whether Claude can be used, but who decides what happens at your organisation: you, or Microsoft's default.

What changes in December?

On 5 November, Microsoft announced that Claude models in Copilot will be processed inside the EU Data Boundary for customers in the EU and EFTA, including in Copilot Cowork (Microsoft). Message Center post MC1546438 of 10 November sets out how that works. There are two changes, and it helps to keep them apart:

  1. In early December, processing moves inside the EU Data Boundary for eligible organisations. If you already use Claude, you do not need to do anything: processing moves automatically.
  2. On 9 December, Microsoft switches Claude on for every organisation that has not saved a choice for Anthropic. All users then get access, in Copilot and in Copilot Studio.

One in-between option also disappears. If you had allowed Claude only in Copilot in the Microsoft 365 apps, such as Word and Excel, Microsoft retires that option on 9 December and the setting moves to all users (M365 Admin). An earlier choice for all users, no users or specific groups stays in place, and after 9 December you can still switch Claude off or limit it at any time.

Why is Claude off in the EU now?

Microsoft runs OpenAI's models in Copilot itself, and those already fall under the EU Data Boundary. Anthropic's models do not yet. According to Microsoft, Claude in Copilot, Researcher, Copilot Studio, Power Platform and Copilot in the Microsoft 365 apps is currently outside the EU Data Boundary and, where they apply, outside in-country processing commitments. That is why Claude is set to "No users" by default in the EU, EFTA and the UK (Microsoft Learn).

Claude sits in more places than you might expect. You see it in the Copilot app, with an indicator when Claude answers, in Researcher, and in Word, Excel and PowerPoint, where users can pick Claude themselves. In Copilot Studio, whoever builds an agent picks the model. And Copilot Cowork was built together with Anthropic. How to put it to work is in Copilot Cowork: getting Copilot to do real work.

Can you use it now?

Yes. An admin can switch Claude on today. Contractually, Anthropic is then a Microsoft subprocessor: Microsoft's Product Terms and Data Protection Addendum apply, as does Enterprise Data Protection, and the Customer Copyright Commitment also covers Claude in Copilot and Copilot Studio (Microsoft Learn).

The difference is where processing happens. Until early December, prompts and the files Claude reads with them are processed outside the EU. After that, it stays inside the EU Data Boundary. If you have agreed with clients, or in your own policy, that data is processed in the EU, waiting until December is the difference between allowed and not allowed.

Which choice fits your organisation?

There are four routes. Which one fits depends mostly on your data commitments and on how far along you are with Copilot.

Your situationWhat you do
You want Claude now, and processing outside the EU is acceptableSwitch it on now, for everyone or a group
You want Claude, but only with processing in the EUSet "No users" now and switch it on in early December
You want a trial firstLimit it to a pilot group before 9 December
You have no policy or DPIA for Claude yetSet "No users" before 9 December

What you should not do is nothing. Then Claude is on for everyone on 9 December, without anyone at your organisation having decided it. So record your choice, even if it is "not yet". A saved "No users" stays in place after 9 December.

Our advice for most organisations: pick a pilot group. Claude and OpenAI's models give different answers to the same question. With a small group you see whether that difference helps, and whether your helpdesk gets questions about which model did what.

How to set it up

You need the AI Administrator or Global Administrator role (Microsoft Learn).

  1. In the Microsoft 365 admin centre, go to Copilot › Settings › View all.
  2. Open AI providers operating as Microsoft subprocessors and select Anthropic.
  3. Choose who gets access: All users, Specific users and groups or No users.
  4. Click Save.

If you work with groups, create a security group for the pilot first. Rolling Claude out more widely is then a single change.

What else should you watch?

Models with data retention are not part of this. Claude Fable 5 and Claude Mythos 5 are models where Anthropic retains data. There, Anthropic is an independent processor and Anthropic's terms apply, not Microsoft's. Anthropic keeps most inputs and outputs for up to 30 days. These models are off by default and need a separate admin choice (Microsoft Learn). According to MC1546438, that setting is separate from the 9 December change.

The EU Data Boundary is not the same as your own country. Processing moves inside the EU, not necessarily into your country. Microsoft does offer in-country data residency for Copilot in a number of EU countries, but that is a different commitment (Holger Imbery). If it really has to stay in one country, ask Microsoft in writing which commitment applies to which service.

Update your documentation. A new model in Copilot belongs in your record of processing, and probably in your Copilot DPIA. Do it when you switch Claude on, or at the latest when processing moves into the EU. How to capture this in an AI policy is in Using AI safely: how to write an AI policy for your team.

When can you ignore this?

If you have already saved a choice for Anthropic, it stays in place. If you already use Claude, processing moves to the EU automatically. And if your Microsoft 365 organisation is not in the EU or EFTA, this change does not apply to you: there, Claude is usually on by default already. Everything else that changed this month in Copilot, ChatGPT, Claude and Gemini is on a timeline in AI news November 2026.

Sources

Newsletter

The AI news that matters, once a month

One email a month with the most important developments in AI and what they mean for your organisation. No noise.

You will receive the Hello Growth newsletter, about once a month. First you get an email to confirm your subscription. You can unsubscribe at any time with the link under every newsletter. Read how we handle your data.

Let us begin

Want this in your own organisation?

We build it, or we teach your team to. Either works.