Claude in Copilot joins the EU Data Boundary, but not in NZ

What Microsoft announced

On 5 November 2026, Charles Lamanna, Microsoft's Executive Vice President for Copilot, Agents and Platform, announced on the Microsoft Copilot Blog that Anthropic's Claude models in Copilot will be processed inside the EU Data Boundary. Microsoft is targeting the end of 2026. The commitment covers eligible Microsoft 365 customers in the EU and EFTA, sits in their existing contract terms and needs no extra purchase. Organisations already using Claude in Copilot don't have to do anything, because their processing will move across automatically once the change goes live. Microsoft says it'll share more detail closer to release.

The change is a reversal of the current position. Microsoft's Learn page on Claude models in Microsoft Online Services, last updated on 4 November 2026, still says Claude models in Copilot, Researcher, Copilot Studio, Power Platform and the Microsoft 365 apps are "currently excluded from the EU Data Boundary, and when applicable, in-country processing commitments." The Copilot Cowork model guide also says tenants inside the EU Data Boundary can only use GPT models in Cowork today.

Where New Zealand and Australian tenants stand

The Microsoft announcement only covers Europe. The Copilot blog post doesn't mention any other region, and German outlet Borncity points out that UK tenants aren't covered either.

For local organisations, the more important detail is the default setting. Microsoft turns Claude on by default for most commercial cloud customers and leaves it off only in the EU, EFTA and the UK, according to the same Learn page. IDM reported that the Anthropic subprocessor toggle switched on for most commercial tenants from 7 January 2026. Unless an administrator has changed that setting, staff in a New Zealand or Australian tenant can send prompts and documents to Claude through Copilot today. Those requests fall outside any regional processing commitment.

Australian organisations lose a guarantee they'd otherwise have. Microsoft listed Australia among the first four countries to get in-country processing for Microsoft 365 Copilot by the end of 2025. Claude requests are excluded from that commitment, which IDM's analyst source summed up as "the moment a request routes to Claude, that guarantee falls away" (IDM).

New Zealand starts from a weaker position. The same Microsoft announcement named eleven more countries for in-country Copilot processing in 2026, and New Zealand isn't among them. Microsoft's Copilot data residency page lists the countries where Cowork prompts and responses are committed to storage at rest in the tenant's default geography. Australia is on that list and New Zealand isn't. A New Zealand tenant has no published in-country processing commitment for any Copilot model, so the Claude exclusion adds one more gap to an existing one. Microsoft hasn't published where Anthropic processes requests from New Zealand tenants.

Why the European move matters here

Microsoft has now shown that Claude processing can sit inside a regional boundary when customers in that region press for it. European tenants got Claude switched off by default and now a processing commitment. Tenants in this part of the world got Claude switched on by default and no commitment. Microsoft's reasons for the difference aren't stated. Even so, New Zealand and Australian buyers can now point to the European arrangement when they ask their Microsoft account team what's planned for this region.

There's a second category of model that deserves attention. Some advanced Claude models are offered as "Anthropic models with Data Retention". For those models, Anthropic acts as an independent processor under its own commercial terms, outside Microsoft's Product Terms and Data Protection Addendum, as the Learn page explains. Anthropic keeps most inputs and outputs for up to 30 days and can hold flagged content for up to two years. Those models are off by default everywhere and need a separate opt-in. Microsoft's announcement doesn't say whether they'll come inside the EU Data Boundary, a gap Data Studios also noted.

Some organisations have told clients, boards or regulators that their AI processing stays onshore or within a named jurisdiction. Those organisations need to check whether staff using Claude in Copilot are breaking that promise. Organisations without such promises still need an accurate record of which subprocessors handle their data, because privacy statements and client contracts depend on one. Claude currently powers a lot of Copilot features, including Researcher, agents in Excel and Word, and Cowork, so most tenants are likely using it more than their data maps show.

What to do now

• Open the Microsoft 365 admin centre, go to Copilot, then Settings, and review AI providers operating as Microsoft subprocessors. Record whether Anthropic is enabled and for whom. The Learn page sets out how to disable it or restrict it to Entra security groups.
• If you keep Claude enabled, limit it to groups whose work doesn't touch client-confidential, health or regulated data. Staff in those roles can keep using models covered by your existing commitments.
• Check whether anyone in your tenant has opted in to Anthropic models with Data Retention. If someone has, review Anthropic's commercial terms and data processing addendum as a separate supplier agreement.
• Update your data map and privacy impact assessment to show which Copilot features can route to Claude, and that those requests sit outside Microsoft's regional processing commitments.
• Ask your Microsoft account team or licensing partner, in writing, whether a processing commitment for Claude is planned for Australia or New Zealand and on what timeline. Microsoft has now committed to Europe, so the question is fair.
• For workloads that have to stay onshore under your control, consider running a model on hardware you manage. We cover the options on our private AI server page, and our AI consultancy work includes setting model governance across Microsoft 365.

Microsoft's year-end date is a target, and the company's Learn pages will show when the EU change actually goes live. Until Microsoft says something about this region, New Zealand organisations should treat Claude in Copilot as an offshore subprocessor and manage access with that in mind.