Microsoft and Anthropic announced that Claude models have reached general availability inside Microsoft Foundry, giving enterprises Azure-native billing, governance and procurement for Claude alongside OpenAI’s models. For IT and procurement teams that have spent months arguing over vendor contracts and cost centres, this looked like the milestone that would finally let them buy Claude the same way they buy the rest of their Azure estate. The catch surfaced almost immediately: the launch does not include a European data zone.
Sweden endpoint, not necessarily Swedish inference
Claude in Foundry currently ships in two deployment types, Global Standard and US Data Zone Standard. The Sweden region gives European customers a local endpoint address, but Global Standard deployments are explicitly designed to route inference wherever capacity allows, which in practice can mean the underlying request and response leave the EU even though the call originated there. That is the opposite of what a Data Zone deployment is meant to guarantee, and Foundry does not yet offer an EU Data Zone option for Claude at all.
Why this lands differently under GDPR and the AI Act
For organisations in banking, healthcare, insurance or the public sector, “the model runs somewhere in Microsoft’s global capacity pool” is not an answer a data protection officer can sign off on. Anthropic’s own documentation confirms that data residency guarantees apply to Claude on AWS Bedrock and Google Vertex AI, but not, at least for now, to Claude on Microsoft Foundry. That gap arrives just as the EU AI Act’s high-risk obligations move toward their August 2026 compliance deadline, which means the window for treating this as a minor technicality rather than a real architectural constraint is closing.
What to check before you deploy
If your organisation is planning to standardise on Claude through Microsoft Foundry, the sensible move is to map exactly where your prompts and outputs will physically be processed before committing to it in a regulated workflow, not after. That means confirming with your Azure account team whether an EU Data Zone for Claude has a committed date, checking whether Global Standard routing is acceptable under your own data processing agreements, and comparing it honestly against alternatives, including AWS Bedrock’s EU Inference Profile or contracting with Anthropic directly, both of which already offer EU-resident processing today.
If you need help working out whether Claude on Microsoft Foundry fits your compliance obligations, or want a data residency assessment before you commit budget to it, contact Excello Digital. We help European organisations turn AI vendor claims into architecture decisions they can actually defend to a regulator.