Claude on Microsoft Foundry Is GA — But It Fails EU Data Residency: What Developers Need to Know

If you're building on Claude and your org is anywhere near a European customer, a compliance officer, or a GDPR audit, there's a gap in the Microsoft Foundry rollout that's easy to miss until it blocks your deployment. Claude reached general availability on Microsoft Foundry on June 29, 2026 — Anthropic and Microsoft called it a production-ready path into the Azure ecosystem, complete with the Messages API, prompt caching, extended thinking, and tool streaming. Two months later, the technical GA is real, but the compliance story is not. There is no EU data zone for Claude on Foundry, and for regulated European enterprises, that single missing checkbox makes the "generally available" label misleading.

This matters beyond one platform. If you're prepping for the Claude Certified Architect (CCA) exam, deployment topology and data residency are exactly the kind of judgment calls the certification tests — not just "can this model call a tool," but "where does this model's data actually live, and does that satisfy the regulation my client is under." This piece breaks down what's actually available, where the gap is, and what to deploy instead if EU residency is a hard requirement.

What "GA on Microsoft Foundry" Actually Means

Claude's arrival on Microsoft Foundry (formerly Azure AI Foundry) gives enterprise Azure customers a way to run Claude models — Opus, Sonnet, and Haiku — without leaving their existing Azure billing, IAM, and governance stack. That's the core value proposition: your security team doesn't have to onboard a new vendor relationship with Anthropic directly, your billing stays consolidated under your Microsoft Enterprise Agreement, and Foundry Agent Service can use Claude as the reasoning engine behind multi-step agents built on Microsoft's orchestration layer.

Two deployment options exist inside Foundry:

• Hosted on Azure — Claude runs on Microsoft's own infrastructure, specifically NVIDIA Blackwell Ultra systems connected via InfiniBand, part of the broader Microsoft–NVIDIA–Anthropic infrastructure partnership announced in late 2025. This is the option that's now GA.
• Hosted on Anthropic infrastructure — Foundry routes requests to Anthropic's own servers. This option remains in preview.

For US-based teams, or teams without strict data-locality requirements, the Azure-hosted option is a legitimate production path today. Claude Sonnet 5 followed Opus and Haiku into GA on Foundry shortly after the initial announcement, so the model lineup is current.

The Gap: No EU Data Zone

Here's where it breaks down. Anthropic's own documentation is explicit that its formal data residency guarantees apply to Amazon Bedrock and Google Cloud Vertex AI — not to Microsoft Foundry. Practically, that means:

• There is no EU-region hosting option for Claude on Foundry. Requests can't be geographically pinned to stay inside EU borders the way they can on Bedrock's Frankfurt or Vertex AI's EU regions.
• Anthropic operates as the data processor for Foundry-hosted inference regardless of which hosting option you pick, and Anthropic is a US company — meaning the US CLOUD Act applies to that data regardless of where the Azure region physically sits.
• Practitioners in banking and healthcare have reported treating the Foundry offering as unapproved for production workloads involving personal data, financial records, or health information — which is most of what regulated European enterprises actually want to build.
• Capacity for Foundry-hosted Claude models still has to be requested through a form and approved, which is an unusual bottleneck for something billed as a finished GA product.

If your organization handles EU personal data under GDPR, or operates under sector-specific EU regulation (finance, health, public sector), Claude on Foundry is not currently a compliant option — no matter how solid the technical integration is.

Where to Deploy Claude for EU Data Residency Today

If data residency is a hard requirement, two paths currently work:

AWS Bedrock, EU regions. Anthropic's residency guarantees explicitly cover Bedrock, and AWS offers multiple EU regions for Claude — Frankfurt (eu-central-1), Ireland (eu-west-1), and Paris (eu-west-3). Requests and data stay pinned to the region you select, which is the guarantee EU compliance teams actually need to sign off on. Google Cloud Vertex AI, EU regions. Same story — Vertex AI's EU regions carry the same formal residency backing that Bedrock does, making it the second confirmed compliant path.

Both routes mean giving up the "everything stays inside my Azure tenant" convenience that made Foundry attractive in the first place. For a team already deep in AWS or GCP, that's a non-issue. For a team that's Azure-native end to end, it means running a second cloud relationship just for the parts of your Claude workload that touch EU personal data — which is exactly the kind of architectural tradeoff worth mapping out before you commit a project plan to Foundry.

Why This Happened: Reading Between the Lines

It's worth understanding why a company as compliance-conscious as Anthropic would ship a GA product with this gap, rather than assuming it's an oversight. A few structural reasons line up:

Bedrock and Vertex had a head start. Anthropic's partnerships with AWS and Google predate the Microsoft integration by years — Claude has been available on Bedrock since 2023 and on Vertex AI shortly after. Data residency infrastructure (regional inference endpoints, region-locked storage for logs and caching) was built out over that time. Foundry is the newest of the three hyperscaler integrations, and EU region support is a heavier lift than it looks: it requires Anthropic to stand up and certify inference infrastructure inside EU borders specifically for the Azure integration, separate from the residency work already done for Bedrock and Vertex. The Microsoft–NVIDIA–Anthropic infrastructure deal is US-first. The Blackwell Ultra clusters powering the Azure-hosted option were announced as part of a partnership rooted in US data center buildout. EU-region capacity on that same infrastructure stack is a separate, later phase of the rollout — not something that ships automatically alongside the US GA. "GA" in cloud marketplaces often means "the integration works," not "every region is covered." This isn't unique to Anthropic. Plenty of models and services go GA on a hyperscaler with a subset of regions live and others following on a staggered timeline. The problem here is one of expectations: enterprise buyers reasonably assume GA means "ready to build a compliant production system," and for a meaningful slice of the Foundry audience — European finance, healthcare, and public sector — that assumption doesn't hold yet.

Bedrock vs. Vertex AI vs. Foundry: A Quick Comparison

If you're choosing a hosting path today, here's how the three stack up on the dimension that matters most for this decision:

None of this means Foundry is a bad product — for a US-based SaaS company with no EU personal data in its pipeline, Azure-native billing and governance for Claude is a genuine convenience. The issue is scope: know exactly which workloads that convenience is safe for before you commit an architecture to it.

What to Watch For Next

Anthropic hasn't published a public timeline for EU data zone support on Foundry, but the pattern from its Bedrock and Vertex rollouts suggests residency support tends to follow model GA by a matter of months rather than years once hyperscaler demand justifies it. If your team is blocked on this specifically, the practical move is to build your Bedrock or Vertex integration now — using an abstraction layer (LangChain, LiteLLM, or a thin internal wrapper around the Messages API) so that adding Foundry as an EU-compliant third option later is a config change, not a rewrite.

How to Decide: A Practical Checklist

Before you pick a hosting path for a Claude deployment, walk through this:

Does any part of the data flowing through this app touch EU personal data, health data, or financial records? If yes, Foundry is off the table until Anthropic ships an EU data zone there.

Is your org already committed to Azure for billing and governance, with no EU data in scope? Foundry (Azure-hosted option) is a reasonable, production-ready choice.

Do you need a single compliant path that works globally, including the EU? Standardize on Bedrock or Vertex AI rather than splitting your deployment strategy by region — it's simpler to audit one integration than three.

Are you evaluating Foundry for a POC only, with production TBD? Fine to prototype there now, but flag the residency gap explicitly in your architecture doc so it doesn't surprise a compliance reviewer six months later.

The pattern worth internalizing: "generally available" describes engineering readiness, not regulatory readiness. Those two facts can diverge, and the Foundry rollout is a clean example of why architects need to check both independently rather than assuming a GA label means "safe to build on everywhere."

Key Takeaways

• Claude reached GA on Microsoft Foundry (Azure-hosted option) on June 29, 2026, with Sonnet 5 following shortly after.
• There is no EU data zone for Claude on Foundry — Anthropic's residency guarantees only formally cover Bedrock and Vertex AI.
• Foundry-hosted Claude inference is processed by Anthropic as a US company, subject to the US CLOUD Act, regardless of Azure region.
• European teams handling regulated data should deploy via AWS Bedrock (Frankfurt, Ireland, or Paris) or Google Cloud Vertex AI EU regions instead.
• Treat "GA" and "compliant for my jurisdiction" as two separate questions when architecting any Claude deployment — this is a real-world case study, not a hypothetical.

Next Steps

Deployment topology, compliance tradeoffs, and multi-cloud architecture decisions like this one are core material on the Claude Certified Architect (CCA) exam. If you're studying for it, AI for Anything's practice test bank includes scenario-based questions on exactly this kind of infrastructure judgment call — not just API syntax. Check out the free sample quiz to see where your gaps are before exam day.

Sources:

• Claude in Microsoft Foundry is now generally available — Claude/Anthropic
• Claude in Microsoft Foundry is now generally available — Microsoft Azure Blog
• Claude Sonnet 5 Is Now Generally Available in Microsoft Foundry — Microsoft Community Hub
• Claude Reaches GA on Microsoft Foundry: European Enterprises Cannot Deploy It — InfoQ
• Claude AI on Azure Fails to Meet EU Data Residency Needs — Windows News