Claude in Microsoft Foundry: Azure-hosted enterprise AI with dual hosting

Claude Opus 4.8 and Claude Haiku 4.5 are now generally available in Microsoft Foundry, giving Azure customers a way to deploy Anthropic's models with Azure-native governance, billing, and data controls. This integration targets enterprises that need to run AI workloads within existing compliance frameworks without setting up separate infrastructure.

What happened

Anthropic announced the general availability of its Claude family in Microsoft Foundry, hosted directly in Azure environments. Claude Opus 4.8 and Claude Haiku 4.5 are accessible via the Messages API, with full integration into existing Azure identity, billing, network, and governance systems. Two deployment modes exist: Azure-hosted (runs on Azure infrastructure with Azure authentication, governance, and a US data processing zone) and Hosted on Anthropic (Foundry Preview for features not yet available in Azure-hosted mode).

Billing is consolidated: Claude Consumption Units (CCUs) appear as a single line item on Azure invoices, and customers with a Microsoft Enterprise Agreement can use their Microsoft Azure Consumption Commitment (MACC). For regulated workloads, zero data retention can be enabled so Anthropic does not retain prompts or outputs once calls complete.

Inference is powered by Nvidia GB300 Blackwell Ultra GPUs with Nvidia Quantum-X800 InfiniBand networking, building on the strategic partnership announced in November 2025. The Foundry Agent Service enables Claude to act as a reasoning engine, coordinating multi-step planning, tool use, and automation across enterprise applications.

Why AI builders should care

For teams building AI products in regulated industries, this integration removes a common bottleneck: deploying models outside familiar cloud environments. You can run Claude within existing Azure governance, identity, and compliance stacks without additional procurement. The dual hosting option lets you choose between full Azure-native controls (including a US data processing zone) and Anthropic-hosted access for newer features.

Enterprise customers can leverage MACC and see consolidated billing for Claude usage, reducing administrative overhead. The zero data retention option directly addresses concerns for workloads handling sensitive data.

Practical implications

Access control is handled through Microsoft Entra ID and Azure RBAC, so you can apply existing governance policies. The Foundry Agent Service lets you build agentic workflows that coordinate multiple steps across enterprise apps, using Claude as the reasoning layer.

Billing consolidation means one line item for CCUs on your Azure invoice, with per-model detail still available inside Foundry. If you need the latest model capabilities before they land in the Azure-hosted option, the Hosted on Anthropic mode remains available as a preview.

Caveats

Exact feature availability may vary by region or deployment mode. The Hosted on Anthropic option may lack some features until capabilities are aligned between the two modes. Verify current regional support and data zone options in the official Microsoft Foundry documentation before committing to a deployment.

FAQs

What is Claude in Microsoft Foundry and how does Azure integration work?

Anthropic's Claude Opus 4.8 and Claude Haiku 4.5 are now generally available in Microsoft Foundry, allowing Azure customers to deploy these models with Azure-native identity, governance, billing, and data controls. Teams manage access via Microsoft Entra ID and Azure RBAC, and usage appears as a single Claude Consumption Unit line item on Azure invoices. Zero data retention can be enabled for high-sensitivity workloads, ensuring Anthropic does not retain prompts or outputs after calls.

What are the hosting options for Claude models in Foundry (Azure-hosted vs Hosted on Anthropic)?

Two deployment modes exist: Claude hosted on Azure and Hosted on Anthropic. The Azure-hosted option uses Azure authentication, governance, and a US data processing zone for data residency. The Hosted on Anthropic option (Foundry Preview) covers features not yet available in Azure-hosted deployments. Both modes are listed as separate model versions in Foundry, and Microsoft and Anthropic intend to align capabilities in the future.

How are access and governance handled (Entra ID, RBAC, data residency, and zero data retention)?

Access is managed through Microsoft Entra ID and Azure RBAC. Data residency options include global or US data processing zones. For high-sensitivity workloads, zero data retention can be enabled, meaning Anthropic does not retain prompts or outputs after API calls complete.

How is billing handled for Claude in Foundry (CCUs on Azure invoices)?

Claude Consumption Units (CCUs) appear as a single line item on Azure invoices. Customers with a Microsoft Enterprise Agreement can use their Microsoft Azure Consumption Commitment (MACC) toward Claude usage. Per-model usage detail remains visible within the Foundry platform.