Writing

Claude in Copilot Crosses the EU Data Boundary — in a Promise, Not in Production

5 min read

A glass-walled server corridor at dusk, with a rocky northern coastline reflected in the glass
The boundary is a place, not a slogan. Claude in Copilot is promised inside it by the end of 2026. It is not there yet. Illustration.

On 5 November 2026, Charles Lamanna published a short post on the Microsoft Copilot blog. The promise is specific. By the end of 2026, organisations in the EU and EFTA will be able to use Anthropic’s Claude models across Copilot, including Copilot Cowork, with processing inside the EU Data Boundary, in the same region where their Microsoft 365 data is already stored. Norway is in EFTA, so a Norwegian tenant is in the scope of that sentence.

I read it the morning after, because I spend the rest of this month standing in front of Norwegian organisations and answering a version of the same question: can we use a stronger model without the prompt leaving the boundary we already pay Microsoft for? The honest answer on 7 November is still no, not yet. The post is a commitment with a deadline, not a switch that flipped on Wednesday.

What Microsoft actually said

Three sentences in the post do the work. The rest is context.

  • The move is due by the end of 2026. There is no day, and no list of which Claude models move. Microsoft says it will share more details closer to availability.
  • Organisations that already use Claude do nothing. Once the processing is available, it moves into the boundary automatically.
  • Organisations that have not enabled Claude can turn it on at any time, and processing moves into the EU Data Boundary once that processing is available. The setting is disabled by default in the EU and EFTA. An admin enables it for everyone, or for selected users and groups, in the Microsoft 365 admin center.

Read the third point twice. Turning Claude on today is not the same thing as Claude running inside the boundary today. Microsoft’s own wording separates the admin toggle from the residency change. If your procurement pack says “Claude is processed in the EU Data Boundary,” you are describing a future state. Date the sentence, or do not write it.

The post also restates the protections that already apply when Claude is used in Copilot: Microsoft’s enterprise data protection, customer data not used to train foundation models, and admin control over who can use the models. Those are real, and they are not a substitute for the residency question. A Norwegian public body, a clinic and a nonprofit do not treat “we will not train on it” and “it is processed in this region” as the same control. They are different lines in the record of processing.

What I will not infer

Microsoft says in-country data residency, data at rest in the customer’s own country, is available in ten countries in the EU and EFTA. The post does not name them. I will not tell a Norwegian customer that Norway is one of the ten because a round number sounds convenient. If in-country residency matters to you, look it up against your tenant, not against a blog summary.

I also will not treat “EU Data Boundary” as a law. It is Microsoft’s own commitment, written into the contract for eligible Microsoft 365 customers in the EU and EFTA, with no extra purchase. It goes beyond what the GDPR requires of a processor, and it is still a vendor commitment. The EU AI Act is a different document, with its own dates. Mixing the two in a board slide is how projects get approved on the wrong basis.

What changes for a tenant I actually configure

For the organisations I work with, the practical sequence does not move.

First, the tenant has to be fit for an agent at all. SharePoint permissions that were “good enough” for a shared drive are not good enough for a Copilot agent that answers from those libraries. Entra ID groups, and Intune where the devices are managed, are the boring half of every Copilot project I have seen succeed. The model does not fix a library that the intern and the board can both read.

Second, someone owns the agent. A nonprofit that turns on Copilot for the whole staff and hopes the grant writer appears has bought a search box. The useful version is smaller: one library, one task, one person who checks the draft against the source before it leaves the building. That is the shape of the grant session I am giving at Microsoft Oslo on 20 November, and it does not depend on which model sits underneath.

Third, when the Claude processing does move, the admin decision is still a decision. Default off is the correct default. Enable it for the people whose work justifies the model, write down why, and do not announce “we are on Claude in Europe” until Microsoft has said the processing has moved, not until Microsoft has said it will.

The question to ask a supplier this month

If a partner tells you that Claude in Copilot is already inside the EU Data Boundary, ask them to point at the sentence. The sentence that exists, written by the EVP who runs Copilot, is dated 5 November 2026 and says “by the end of 2026” and “once available.”

That is a good announcement. It is the one European customers have been waiting for, because model choice without a residency exception is the only model choice a regulated buyer can actually take. It is not a status page. Treat it as a date you can plan against, and keep the current architecture honest until the date arrives.

The post is here: Bringing Claude models in Microsoft Copilot into the EU Data Boundary. The admin setting is documented on Microsoft Learn.

Portrait of Håkon Berntsen

Written by

Håkon Berntsen

CTO and co-founder of Skjld Labs AS. Builds production AI agents, Microsoft 365 systems and the courses around them, from Sandefjord.

About LinkedIn GitHub