Claude in Microsoft Foundry GA on Azure

Introduction

Microsoft has announced general availability for Claude in Microsoft Foundry, a notable update for organizations building enterprise AI on Azure. For IT leaders and platform teams, the significance is less about another model endpoint and more about getting a supported, governable, and billable path to production AI inside the Azure environment they already manage.

What’s new

Claude is now production-ready in Microsoft Foundry

Organizations can now access Anthropic Claude models through their existing Azure account. This reduces friction around procurement, account management, and platform onboarding.

Azure-native enterprise controls

Claude in Foundry supports the Azure controls enterprises expect, including:

• Microsoft Entra ID for authentication
• Azure RBAC for access control
• Existing governance and management policies
• Familiar Azure billing and usage tracking
• Global and US data zones for residency needs
• Zero data retention for sensitive workloads

Developer and agent capabilities

Developers can use Claude through the Messages API with features such as:

• Prompt caching
• Extended thinking
• Tool streaming

For agent-based solutions, Foundry Agent Service can use Claude as the reasoning engine for multi-step planning, tool use, and task execution across enterprise systems.

Simplified commercial model

Claude usage is billed in Claude Consumption Units (CCU) as a consolidated line item on the Azure bill. Microsoft also notes support for MACC drawdown, which may help organizations align AI consumption with existing Azure commitments.

Why this matters for IT administrators

For many enterprises, AI projects slow down because of governance, networking, security reviews, and purchasing complexity rather than model quality. This GA release addresses those blockers by letting teams use Claude within established Azure operating models.

Admins also gain more control over compliance-sensitive deployments through data zone options and zero-retention support. In addition, organizations can use Foundry services such as model routing, evaluation, and policy enforcement to improve cost efficiency and reduce risk before responses reach users.

Next steps

IT and platform teams should consider the following actions:

• Review whether Claude workloads fit existing Azure AI and governance policies
• Validate data residency and zero-retention requirements with security teams
• Assess Entra ID and RBAC access design for development teams
• Pilot Foundry Agent Service for internal agentic workflows
• Monitor CCU billing and MACC impact for cost planning

Claude in Microsoft Foundry GA gives Azure customers a more practical path from AI experimentation to enterprise-scale deployment, especially for coding assistants, research workflows, and business process agents.