Claude Is Now Generally Available in Microsoft Foundry

As of June 29, 2026, Anthropic’s Claude models are generally available in Microsoft Foundry, hosted on Azure. For teams already standardized on Microsoft, this removes a common point of friction. You no longer have to choose between using a frontier model and keeping your identity, billing, and governance inside the environment you already run.

We covered Claude arriving inside Microsoft Copilot for end users. This is the other half of the story: Claude as a first class option for the developers and platform teams building on Azure.

What you actually get

Claude runs through the Messages API with prompt caching and extended thinking, which are the capabilities that matter for coding, agentic work, and careful reasoning over long or complex inputs. The lineup available at launch included Claude Opus 4.8 and Claude Haiku 4.5, and newer models such as Claude Opus 5 have since been added to the Foundry catalog. Recent updates also brought structured outputs, web search, web fetch, an MCP connector, and tool search to Claude on Azure.

Two deployment options, one decision

Foundry gives you a choice about where inference runs, and it is worth making deliberately:

• Hosted on Azure, with a US data zone for teams that have data residency requirements. This is the option to reach for when governance and residency drive the decision.
• Hosted on Anthropic, when you want the full set of API features or a model that is not yet on Azure.

Pick per workload rather than once for everything. A regulated workload and an internal developer tool do not need the same answer.

Billing and governance stay where they are

This is the part that makes adoption easy to approve. Claude usage shows up on a single consolidated Azure invoice, and for customers with a Microsoft Enterprise Agreement it can draw down an existing Azure commitment. The models sit inside your Azure identity, networking, and governance controls, so the boundary your security team already reviewed still applies. No new vendor to onboard, no separate bill to reconcile.

How to adopt it well

The rollout advice is the same one we give for any model change: start with a small pilot and a short list of real tasks, not demos. Compare Claude against the models you already use on the work your teams actually do, write down where each one wins, and turn that into simple guidance for your people. Confirm the data path and residency choice before you widen access, and put budgets and monitoring on it from day one.

Claude in Foundry is a genuine upgrade for teams on the Microsoft stack, but the value comes from using it deliberately. At Maxim Cloud Solutions we help businesses pilot Claude in Foundry, set the guardrails, and fit it into the governance you already have. Talk to an expert about adding Claude to your Azure environment.