35 Claude in Microsoft Foundry is Now Generally Available

35.1 Overview

On June 29, 2026, Anthropic announced that Claude models were generally available in Microsoft Foundry on Azure, marking a milestone in the partnership between the two companies. After a successful preview period, enterprises could now deploy Claude in production through Microsoft’s AI platform, with the full weight of Azure’s authentication, billing, and governance infrastructure behind it.

The GA release addressed the needs of organizations that had standardized on the Microsoft stack — Azure Active Directory (Entra ID), Enterprise Agreements, Microsoft Purview, and Azure Monitor — and wanted to adopt Claude without introducing a separate vendor relationship or identity system. With this release, Claude could be governed, billed, and monitored using the same tools that managed every other Azure service.

The announcement was notable for offering two deployment options, giving customers flexibility in how they balanced Azure-native governance against full Claude Platform features.

35.2 What General Availability Means

The move from preview to general availability signified several things:

Aspect	Preview	General Availability
Support level	Best-effort	Enterprise SLA
Compliance	Limited	Full Azure compliance certifications
Scale	Capped	Production scale
Regions	Limited	US data zone (more to follow)
Billing	Standard Azure billing	Enterprise Agreement commitment integration

For enterprises, GA meant they could move Claude workloads from pilot to production with confidence. The Enterprise SLA provided uptime guarantees, and integration with Azure’s compliance certifications meant that regulated industries — healthcare, finance, government contractors — could adopt Claude under their existing compliance frameworks.

35.3 Two Deployment Options

The most strategically important aspect of the announcement was the introduction of two ways to run Claude through Microsoft Foundry, each optimized for different priorities.

35.3.1 Option 1: Claude Hosted on Azure

In this model, Claude ran within the Azure environment, with Azure serving as both the platform and the data processor. This option was designed for organizations that prioritized:

Azure-native governance: Full integration with Azure policies, Purview, and Monitor.
US data zone: Data residency within the United States data zone.
Single-vendor simplicity: Everything — compute, storage, AI — stays within Azure’s governance boundary.

graph LR
    A[Your Azure Tenant] -->|Entra ID Auth| B[Microsoft Foundry]
    B -->|Hosts| C[Claude on Azure]
    C -->|US Data Zone| D[(Azure Storage)]
    B -->|Azure Monitor| E[Logs & Metrics]
    B -->|EA Billing| F[Enterprise Agreement]

This was the option most organizations chose when data residency and Azure-native governance were non-negotiable.

35.3.2 Option 2: Claude Hosted on Anthropic

In this model — previously available as “Foundry Preview” — Claude ran on Anthropic’s infrastructure but was accessed through Microsoft Foundry with Azure authentication and billing. This option was designed for organizations that prioritized:

Full Platform features: Access to the complete Claude Platform feature set (Managed Agents, Skills, MCP connector, etc.).
Anthropic as data processor: For organizations whose data processing agreements were already in place with Anthropic.

Dimension	Hosted on Azure	Hosted on Anthropic
Infrastructure	Azure environment	Anthropic infrastructure
Data processor	Microsoft	Anthropic
Data zone	US data zone	Anthropic’s zones
Feature set	Claude models in Foundry	Full Claude Platform
Governance	Full Azure-native	Azure auth + billing, Anthropic Console for features
Best for	Data residency, Azure governance	Maximum features

Note

The two options were not mutually exclusive. An organization could use Claude hosted on Azure for workloads with strict data residency requirements, and Claude hosted on Anthropic for workloads that needed Managed Agents or Skills. Both were accessed through Foundry with Azure authentication.

35.4 Available Models

At GA, two models were available through Microsoft Foundry:

Claude Opus 4.8 — The most capable model, suitable for complex reasoning, code generation, and agentic workflows. Opus 4.8 represented the latest generation of Anthropic’s flagship model.
Claude Haiku 4.5 — The fast, efficient model for high-volume, latency-sensitive tasks.

The inclusion of Opus 4.8 was particularly significant, as it was the newest model in Anthropic’s lineup at the time. Microsoft Foundry customers got access to frontier capability alongside the governance and compliance of Azure.

35.5 Enterprise Agreement Integration

A critical feature for large enterprises was Enterprise Agreement (EA) commitment integration. Organizations that had signed multi-year Azure EAs — committing to a certain level of Azure spend in exchange for discounts — could now draw down those commitments with Claude usage.

This had immediate financial implications:

No new budget line: Claude spend came out of the existing Azure commitment, not a new vendor budget.
Discount application: EA discount rates applied to Claude usage, reducing effective cost.
Simplified procurement: No separate contract negotiation with Anthropic.

Tip

For organizations with significant unused EA commitments, adding Claude workloads was a way to utilize committed spend that might otherwise expire unused — effectively making Claude “free” against already-committed dollars.

35.6 Azure Governance Integration

35.6.1 Authentication via Entra ID

Claude in Foundry used Microsoft Entra ID (formerly Azure Active Directory) for authentication. This meant:

SSO integration: Users signed in with their corporate Entra ID credentials.
Conditional access: Existing conditional access policies (device compliance, location, MFA requirements) applied automatically.
Group-based access: Access to Claude could be granted or revoked through Entra ID group membership.

// Example: Granting Claude access via Entra ID group
{
  "group": "claude-users",
  "members": ["user@contoso.com", "dev-team@contoso.com"],
  "role": "Claude.User",
  "conditions": {
    "requireMFA": true,
    "allowedLocations": ["US"]
  }
}

35.6.2 Monitoring and Compliance

Claude usage in Foundry integrated with Azure’s monitoring and compliance stack:

Azure Monitor: Metrics and logs for Claude API calls.
Microsoft Purview: Data classification and lineage tracking.
Azure Policy: Governance rules applied to Claude resources.
Azure Cost Management: Spend tracking and budget alerts.

This integration meant that an organization’s existing cloud governance team could manage Claude using the same dashboards, policies, and processes they used for every other Azure service — no new tooling to learn.

35.7 US Data Zone

The GA release included availability in the US data zone, addressing data residency requirements for organizations that needed to ensure their data remained within the United States. This was particularly important for:

Government contractors subject to ITAR or similar regulations.
Financial institutions with data residency requirements.
Healthcare organizations with HIPAA compliance obligations.

Anthropic indicated that additional data zones would be added over time, with European and Asia-Pacific regions on the roadmap.

35.8 Use Cases and Adoption Patterns

35.8.1 Enterprise Knowledge Work

The most common initial use case was knowledge work — using Claude through Microsoft 365 Copilot scenarios, internal applications built on Foundry, or direct API integration into enterprise systems.

For example, a financial services firm might build an internal application that used Claude Opus 4.8 to analyze earnings reports, summarize regulatory filings, and draft client communications — all authenticated through Entra ID and governed by Azure policies.

35.8.2 Code Generation for .NET Shops

Organizations with large .NET codebases found Claude particularly valuable for:

Generating boilerplate C# code.
Writing unit tests for legacy frameworks.
Documenting APIs.
Migrating between .NET versions.

35.8.3 Document Processing

With the Files API, organizations could upload large documents — contracts, research papers, technical specifications — and have Claude extract, summarize, and analyze them, with all processing governed by Azure’s compliance framework.

35.9 Comparison with Other Deployment Options

Microsoft Foundry joined the list of cloud platforms through which Claude was available:

Platform	Operator	Data Processor	Unique Advantage
Microsoft Foundry (Azure-hosted)	Microsoft	Microsoft	Azure-native governance, US data zone
Microsoft Foundry (Anthropic-hosted)	Anthropic	Anthropic	Full Platform features + Azure billing
Claude Platform on AWS	Anthropic	Anthropic	Full features, AWS IAM/billing
Amazon Bedrock	AWS	AWS	Region-level data residency
Claude API (direct)	Anthropic	Anthropic	Maximum flexibility

35.10 Migration from Foundry Preview

For organizations that had been using Claude during the Foundry Preview period, the transition to GA was seamless. Existing applications continued to work, and the upgrade primarily unlocked:

Enterprise SLA support.
Production-scale capacity.
Full compliance certifications.
Enterprise Agreement commitment integration.

35.11 Key Takeaways

Claude is now production-ready in Microsoft Foundry. GA status brings enterprise SLAs, full compliance certifications, and production scale.
Two deployment options offer flexibility. Hosted on Azure (Azure-native, US data zone) vs. hosted on Anthropic (full Platform features). Both use Azure authentication and billing.
Opus 4.8 and Haiku 4.5 are available at launch. Frontier capability and fast efficiency, covering the full spectrum of use cases.
Enterprise Agreement commitments apply. Claude spend draws down existing Azure EA commitments, simplifying procurement and applying discount rates.
Entra ID integration is the governance backbone. SSO, conditional access, group-based permissions, and MFA all apply automatically to Claude access.
US data zone addresses residency requirements. Additional regions are on the roadmap.
Azure-native monitoring and compliance. Azure Monitor, Purview, Azure Policy, and Cost Management all integrate with Claude usage.
The two options are complementary, not exclusive. Organizations can use Azure-hosted for residency-sensitive workloads and Anthropic-hosted for feature-rich workloads simultaneously.
Foundry GA is the right default for Microsoft-centric organizations that want to adopt Claude within their existing Azure governance and procurement framework.