Microsoft will process Anthropic’s Claude models inside its EU Data Boundary by the end of 2026. For a bakery in Lyon or a plumber in Odense, that sounds like a compliance win. It is one – but only if you know which engine you are actually running.
FROM THE EDITORS
Think of Copilot as the car. It has seats, a dashboard, a boot for your files, and a set of keys your IT admin holds. The model – GPT or Claude – is the engine. Until now, European small firms that wanted the Claude engine had to accept that the engine bay sat outside the EU garage. Microsoft has now promised to move that engine inside the garage by the end of 2026. The car does not change. The garage does. And the garage, for a ten-person accountancy in Ghent, is the part that matters.
What Microsoft announced
On 5 November 2026, Microsoft said Claude models in Copilot will be processed within the EU Data Boundary for customers in the EU and EFTA by the end of 2026. The boundary is Microsoft’s commitment to store and process customer data for Microsoft 365 and other online services inside the EU and EFTA. Organisations already using Claude need do nothing; processing moves automatically. Organisations that have not enabled Claude can do so in the Microsoft 365 admin centre, under the setting “AI providers operating as Microsoft subprocessors”, for all users or selected groups. Today, in the EU and EFTA, Claude is switched off by default.
What it isn’t
Copilot is not becoming Claude. Claude is one model offered inside Copilot, alongside OpenAI’s GPT models. This is model choice, not a supplier switch. Microsoft remains the supplier; Anthropic is a Microsoft subprocessor, and for its standard models Microsoft’s Product Terms and Data Protection Addendum apply. The announcement is about where the processing happens, not who owns the relationship. For a small firm, that distinction is the whole ballgame: you are not signing a contract with Anthropic. You are asking Microsoft to keep Anthropic’s work inside the same boundary Microsoft already promises for your email and spreadsheets.
The fine print
The date is “end of 2026”. No exact day. Microsoft has not said which Claude models move first. Models in preview, and models labelled “with Data Retention”, may still run outside the boundary. For the retention models, Anthropic – not Microsoft – stores most inputs and outputs for up to 30 days, outside your Microsoft agreement. The UK is not covered. And “inside the boundary” does not automatically mean “GDPR solved”. A boundary commitment is a contractual promise about location, not a guarantee that every data-protection question is answered. Your DPIA still needs to name the processing chain.
What it means for a small business
Data residency. If you are a specialist firm handling client files – an accountant, a solicitor, a clinic – the question “where does the prompt go?” is not academic. Today, enabling Claude means prompts leave the boundary. After the move, Microsoft says they won’t. That is a genuine simplification for your records.
Lock-in and supplier choice. Our earlier piece on open models, Le Chonk Hands Europe the Keys, argued that European firms should care about choosing their supplier. This is the same trend inside Microsoft’s walls: the model becomes a choice, but the car, the garage and the keys stay Microsoft’s. That is convenient. It is not independence. A firm that wants to swap engines without swapping cars can now do so more safely inside the EU. A firm that wants to own the garage still needs to look elsewhere.
Who this matters to now – and later. Most small firms in the EU do not have a Copilot licence. For them, this is a signal, not an action item. The signal: Microsoft is treating EU data residency as a competitive feature, not an afterthought. The action item arrives when your first colleague asks to use Claude for a client memo and you have to answer whether that is allowed.
What to do this month
- Check the setting. Find “AI providers operating as Microsoft subprocessors” in the Microsoft 365 admin centre and see whether Claude is on, off, or limited to a group.
- Update your records. Add Anthropic to your GDPR record of processing and your DPIA. Note that processing is scheduled to move inside the boundary by the end of 2026, but is outside today.
- Pilot with a small group. If you want Claude, turn it on for a few people first. Choosing a model adds complexity; do not add it for everyone at once.
- Leave the retention models off for now. Keep the “with Data Retention” models switched off until Microsoft says where they are processed and on what terms.
The engine is moving into the garage. That is progress. But a car is not a workshop, and a garage is not a mechanic. Small firms still need to know who holds the keys – and what happens when the engine changes.
Sources
- Microsoft Copilot Blog, “Bringing Claude models in Microsoft Copilot into the EU Data Boundary”, 5 Nov 2026 — https://www.microsoft.com/en-us/copilot/blog/2026/11/05/bringing-claude-models-in-microsoft-copilot-into-the-eu-data-boundary/
- Microsoft Learn, “Anthropic models in Microsoft Online Services” — https://learn.microsoft.com/en-au/microsoft-365/copilot/connect-to-ai-subprocessor
- Microsoft Learn, “Copilot in Microsoft 365 apps with Anthropic models” — https://learn.microsoft.com/en-ie/microsoft-365/copilot/copilot-anthropic-apps
- Signal Digital, “Le Chonk Hands Europe the Keys” — https://signaldigital.net/2026/11/03/le-chonk-hands-europe-the-keys/
Leave a Reply