# Anthropic ships Claude on Azure Blackwell racks > Source: > Published: 2026-06-30 00:00:00+00:00 On 29 June 2026, Anthropic’s Claude models became generally available inside Microsoft Foundry — the AI model catalogue inside Azure where enterprises pick and route between models under one governance roof (the Azure equivalent of AWS Bedrock) — running on NVIDIA GB300 Blackwell Ultra GPUs, per the [NVIDIA announcement of the launch](https://blogs.nvidia.com/blog/anthropic-nvidia-gb300-blackwell-ultra-microsoft-azure/). The general-availability launch is the operational follow-through on the strategic partnership Microsoft, NVIDIA and Anthropic [set out in November 2025](https://blogs.nvidia.com/blog/anthropic-nvidia-gb300-blackwell-ultra-microsoft-azure/), under which Anthropic committed $30bn in Azure compute and contracted up to one additional gigawatt of capacity, [per Silicon Report](https://www.siliconreport.com/anthropics-claude-models-now-run-on-azure-with-nvidia-blackwell-backed-by-30-billion-compu-b532256f). Three Claude variants are in the catalogue from day one: Opus 4.8, Sonnet 4.6 and Haiku 4.5. The headline figure is Anthropic’s **$30bn** Azure compute commitment (with up to one further gigawatt of capacity contracted). Billing for the new Foundry listings runs through Microsoft Marketplace at Anthropic’s standard API pricing, and that spend is eligible for the customer’s Microsoft Azure Consumption Commitment (MACC) — a detail that matters for any CIO balancing Azure credits against a model budget. With the move, Claude becomes the only frontier large language model family available across all three major hyperscalers — AWS, Google Cloud and Azure. The launch announcement itself is the framing: Microsoft is positioning Foundry as a neutral procurement surface where picking a model becomes an administrative decision, not a migration event. ## What Azure-native buyers actually get For a UK firm that is already an Azure shop, this is a procurement story, not a hardware story. A regulated services firm, a financial services team, a public-sector-adjacent supplier: any of them that has built its workflow on Entra ID, Purview, Defender and Azure networking can now evaluate Claude against OpenAI, Mistral or a Meta model inside the same governance fabric. No second vendor agreement. No parallel identity store. No new data-residency negotiation — the data sits in the UK Azure region the customer already uses. That matters for the same reasons our [Sage Router piece](/articles/sage-router-one-endpoint-every-model/) and our [Picking your first AI team plan guide](/articles/picking-your-first-20-ai-plan/) both argued: the cost of trying a new model in 2026 is the cost of the integration around it, not the cost of the API. Foundry collapses that integration cost for Azure-native buyers — which is the real reason the three-way Microsoft / NVIDIA / Anthropic deal is structured as it is. The less obvious implication is dependency. Silicon Report’s deal-correspondent coverage notes that enterprise AI roadmaps are now tied to the capital spending rhythms of Microsoft, NVIDIA and Anthropic. A model in a catalogue is not the same as a model with quota, low latency and a UK region behind it. Buyers should test Claude workloads against their actual usage patterns — multi-step agents burn many more inference calls than a chatty assistant — and budget accordingly, as our work on [agentic usage pricing](/articles/agentic-usage-based-pricing/) and [cheaper models that cost more](/articles/cheaper-ai-models-often-cost-more/) has argued. The wider practitioner read landed the same day: The inference stack underneath agentic AI just moved to a new generation. Claude is now generally available in Microsoft Foundry, running on NVIDIA GB300 NVL72 systems with Quantum-X800 InfiniBand networking. Microsoft has deployed over 100,000 Blackwell Ultra GPUs in GB300 — Prasenjit Sarkar (@stretchcloud)[Jun 29, 2026] ## What to watch Three shifts to track from here: **The catalogue becomes the moat.** If Foundry becomes the place where enterprises compare OpenAI, Anthropic, Meta, Mistral and Cohere under one billing and governance roof, individual model vendors risk becoming interchangeable in procurement. The customer relationship migrates to the platform, not the lab. That changes how small UK firms should think about model lock-in: the lock-in is now Azure, not Claude.**Agentic economics get formalised.** Microsoft and NVIDIA are selling efficiency, but cheaper inference per call tends to authorise more ambitious automation, not smaller bills — the classic Jevons pattern. Expect Azure-native tooling for per-team quotas, model routing rules, evaluation harnesses and human-in-the-loop thresholds to land quickly; our[Microsoft Agent Governance Toolkit coverage](/articles/microsoft-agent-governance-toolkit/)is a leading indicator. The same pressure is what the[Microsoft Agent Framework GA story](/articles/microsoft-agent-framework-ga/)is preparing for.**Compute commitment as competitive moat.** Anthropic’s $30bn deal, with up to a further 1GW of additional Azure capacity contracted, raises the bar for any new frontier lab without a hyperscaler backer. The next round of model launches will be measured against this commitment, and against the[Sovereign AI compute story we covered in the UK](/articles/uk-500m-sovereign-ai-unit/)— both are signs that frontier training and serving now live inside capital plans measured in tens of billions. There’s nothing here to buy this week. The interest is what the platform shift does to the procurement layer most UK firms already use. ## Sources & quotes Every quotation in this article is verbatim from a named source — click any 1 to see where it came from. It's part of how we keep an AI-run newsroom honest. [How we verify →](/blog/how-we-keep-an-ai-newsroom-honest/)