Opus 4.8 and Haiku 4.5 are generally available through Microsoft's Azure model catalog, with Microsoft Entra ID sign in, a US data zone, and Microsoft Azure Consumption Commitment (MACC) eligible billing.
Anthropic's Claude Opus 4.8 and Claude Haiku 4.5 are now generally available inside Microsoft Foundry, the model catalog Microsoft runs inside Azure. For enterprises already standardized on Azure, the announcement is less about a new model and more about procurement consolidation. Claude inference now runs through the same sign-in, role-based access controls, network boundaries, and billing line that an Azure customer already manages for the rest of their Azure estate. Anthropic framed the launch the same way in its own post.
The configuration stack is concrete. Foundry-hosted Claude runs on Azure infrastructure and is reachable through the Anthropic Messages API, with two data-residency options: a global Azure data zone or a US-only data zone. Identity and access go through Microsoft Entra ID, the identity service that gates most enterprise Microsoft 365 and Azure workloads, and existing Azure role-based access policies carry over. For regulated workloads, Anthropic offers a zero data retention mode: prompts and outputs are not retained after the call completes, and Anthropic acts as data processor for Foundry-hosted traffic.
The billing hook is the part enterprise procurement teams will want to test. Claude usage on Foundry shows up as Claude Consumption Units (CCUs) on the Azure invoice, and customers with a Microsoft Enterprise Agreement can apply Microsoft Azure Consumption Commitment (MACC) credit toward that line, as documented on Microsoft Learn. An organization that has already committed Azure spend can now spend part of that commitment on Claude without opening a separate contract with Anthropic. The specific commitment-tier rates and any volume terms live in the Microsoft Learn and Azure documentation rather than in the announcement itself, and those details are worth confirming with a Microsoft account team before assuming dollar thresholds.
This is not Claude's first appearance on a hyperscaler. Anthropic has long been available on AWS Bedrock, and the direct Anthropic API has existed independently. What changes this week is the Azure-native control plane: a buyer who already routes data through Entra, governs it with Azure Policy, and bills it through a Microsoft Enterprise Agreement can now do the same with Claude inference. For capabilities not yet on the Azure-hosted path, a hosted on Anthropic option remains available, separate from the Azure-native governance hooks.
The most useful question for a regulated-workload buyer is narrower than the news cycle suggests: does the combination of US data zone, zero data retention, Entra provisioning, and MACC billing actually map onto a deployment path that compliance, security, and procurement can sign off on this quarter? If yes, the procurement friction that previously pushed Claude outside the Azure stack is largely removed. If a specific capability is not yet on the Azure-hosted path, the buyer still has the alternative option, but it does not carry the same Azure-native governance hooks.
Watch next: which Anthropic capabilities show up on the Azure-hosted path versus remaining on the alternative, and whether the MACC terms as documented match the procurement commitment an enterprise has already signed.