Claude is now reachable through
Azure's standard route
Until recently, teams standardized on Azure needed a separate Anthropic contract and a separate invoice just to try Claude. General availability in Microsoft Foundry removes that friction. But Claude running on Azure is not feature-identical to Claude reached directly through Anthropic. Here's what changed, and what's still missing.
"Not available through Azure"
is now the old story
Microsoft Foundry (formerly Azure AI Foundry) now officially supports Anthropic's Claude models, reachable directly from an Azure environment. According to the Microsoft Azure Blog announcement, general availability landed on June 29, 2026. For companies standardized on Azure, the procedural wall — a separate Anthropic contract and a separate invoice just to use Claude — collapses into a single Azure Marketplace bill.
This builds on a partnership Microsoft, NVIDIA, and Anthropic struck in November 2025. Claude hosted on Azure runs on NVIDIA Blackwell Ultra-generation GPUs connected by InfiniBand networking — infrastructure-level integration, not just an API wrapper. Per Anthropic's own documentation, Claude on Azure spans four model lines — Claude Opus 5, Opus 4.8, Sonnet 5, and Haiku 4.5 — with two deployment options: Global Standard and US Data Zone Standard.
Claude on Foundry, by the numbers
The question isn't "can we deploy it" anymore.
It's "which way should we run it."
Hosted on Azure vs.
Hosted on Anthropic
Claude on Foundry comes in two hosting modes, and where inference actually runs differs between them.
| Hosted on Azure | Hosted on Anthropic |
|---|---|
| Inference runs on Azure infrastructure | Inference runs on Anthropic's own infrastructure |
| Only the latest Opus/Sonnet/Haiku models | Every Claude model available on Foundry |
| Global Standard or US Data Zone Standard | Global Standard only |
| Recommended for most workloads | For features or models not yet on Azure |
For deployments hosted on Azure, prompts and completions stay within Azure — only usage metadata and content flagged by Anthropic's safety systems ever reach Anthropic, per the documentation. For companies that chose Azure specifically for data residency, that distinction is the deciding factor.
Five agentic capabilities landed on Aug 17
About seven weeks after GA, the Microsoft Foundry Blog announced a shift from single calls to agents.
Structured Outputs
Responses can now follow a specified schema, making handoffs to downstream systems more reliable.
Web Search / Web Fetch
Claude can search the web and fetch pages itself, even on Azure-hosted deployments (with the caveats covered below).
MCP Connector & Tool Search
Claude can now connect to Model Context Protocol servers and search a large tool catalog for just the ones it needs.
Who this actually helps
Engineers
Authenticate with an API key or Microsoft Entra ID, and lay Foundry User or Cognitive Services User RBAC roles right on top of your existing Azure permission model — no separate Anthropic account management needed.
Procurement / IT
Claude spend rolls into your existing Azure bill through the Azure Marketplace. You can pilot it without a new vendor review — useful ammunition if procurement had been locked into GPT by default.
Business / PM
Usage shows up in the Azure Monitor, Log Analytics, and Cost Management tools you already use. No new observability stack to stand up, which makes the internal approval story simpler.
What to do about it now
Three concrete moves are worth making.
- Sonnet 5's promotional pricing ($2 input / $10 output per million tokens) runs only through August 31, 2026. If you're weighing a pilot on Azure, run the cost comparison this week rather than later.
- Decide between Hosted on Azure and Hosted on Anthropic based on your data-residency requirements first, then check the feature-gap list below before committing.
- If your team already has a direct Anthropic contract for the Claude API, switching to Foundry buys little. The value is concentrated among teams that specifically want to avoid adding a non-Azure vendor.
What's still missing
This isn't an unqualified win. Geography is one limit: per InfoQ's reporting from July 2026, European enterprises still could not deploy Claude through Microsoft Foundry at GA, due to data-residency requirements. As of this writing, no public timeline for EU infrastructure has been announced.
Feature gaps matter too. Anthropic's documentation states plainly that the Admin API, Compliance API, Message Batches API, and Claude Managed Agents are unsupported on Foundry under either hosting mode. Azure-hosted deployments specifically also lack code execution, Agent Skills, programmatic tool calling, Files API, and any web search/web fetch tool version newer than the original 2025 release. Requests using these features against an Azure-hosted deployment are designed to return a 400 error. If your workload depends on the full enterprise feature set, the direct Claude API or the Hosted-on-Anthropic option remains the safer choice — for now, treat "Claude via Azure" and "Claude via the direct API" as two related but distinct products.