- Azure Expansion: Microsoft plans to deploy AMD’s Helios rack-scale AI system on Azure and broaden AMD’s infrastructure role.
- Helios Stack: Helios combines MI455X accelerators, EPYC Venice processors, Pensando networking and Radeon Open Compute software in one coordinated rack.
- Azure Services: Azure also plans HDv2 for data pipelines, HXv2 for chip design and ND MI455X v7 for AI inference.
- Deployment Limits: Financial terms, deployment capacity, scale-up networking and independent benchmarks remain unavailable ahead of planned second-half 2026 shipments.
Microsoft and AMD have expanded their Azure partnership across accelerators, processors, networking and software.
Microsoft plans to deploy AMD’S Helios rack-scale AI supercomputing platform on Azure and expand its Azure AI and HPC infrastructure, broadening AMD’s role across accelerators, processors, networking and software.
For Azure customers, the expansion creates another integrated option for running trained AI models and related services, although Microsoft and AMD did not disclose financial terms or deployment capacity. Futurum Group’s estimate would put Nvidia’s GPU market share at more than 95% and AMD’s at about 4.5%. One large cloud customer does not erase that competitive gap, but it gives AMD a prominent environment in which to test a complete system.
What Microsoft Is Adding to Azure
Helios integrates MI455X, Venice, Pensando and ROCm in one rack-scale platform. A rack-scale system coordinates processors, accelerators, networking and software as one unit instead of treating each component as a separate server purchase.
MI455X accelerators provide the AI compute, EPYC Venice CPUs handle general processing, Pensando manages network traffic, and Radeon Open Compute (ROCm) supplies AMD’s accelerator software layer. Memory, processor scheduling, network traffic and software must work together before Azure can offer dependable model inference.
Helios targets 260 TB/s and 43 TB/s for data movement within racks and between racks, respectively. The first figure covers communication among accelerators in one system, while the second covers traffic across multiple racks.
Azure also plans three AMD-powered offerings with different jobs. HDv2 virtual machines (VM) target agentic AI and data pipelines, HXv2 VMs target chip design, and ND MI455X v7 will use Helios to execute trained AI models. Azure Foundry Managed Compute adds a managed route to AMD-powered infrastructure, subject to Microsoft’s rollout schedule and AMD’s shipment plan.
HDv2 includes nearly 500 physical EPYC cores, 4 TB of memory, 32 TB of local NVMe storage and 400 Gb Azure Boost networking. HXv2 includes 176 EPYC cores running above 5 GHz, 50% more addressable cache per core than HX, nearly 2 TB or 4 TB of memory, and 800 Gb InfiniBand. Those configurations distinguish CPU-heavy services from the Helios inference system and give chip-design workloads a separate high-frequency option.
AMD’s Pensando data processing units (DPUs) offload networking and storage work from central processing units. Moving connection handling away from the main processors leaves more CPU capacity for customer workloads. Microsoft already uses Azure Boost’s DPU architecture since 2024; the planned AMD integration extends that established offload mechanism instead of adding another accelerator alone.
The Competitive Test Still Lacks Deployment Proof
Microsoft also expands Azure AI infrastructure work with Nvidia, making the AMD plan an addition to a multi-supplier strategy rather than a replacement. Nvidia’s Compute Unified Device Architecture (CUDA) gives developers an established software ecosystem around its accelerators. Counterpoint Research analyst Neil Shah attributes Nvidia’s larger and materially more advanced ecosystem to CUDA.
Scarce AI capacity can generate hardware demand without demonstrating a performance advantage. Futurum Group analyst and CEO Daniel Newman sees AMD’s gains as potentially reflecting either technological superiority or capacity constraints that ensure available hardware finds customers.
Helios enters a rack-system contest in which AMD must establish accelerator capability and a dependable software and networking package. Microsoft’s purchase gives AMD a prominent customer test, not proof that Helios has closed the software or performance gap.
Microsoft has not publicly specified the scale-up network for its initial Helios racks. The interconnect controls how accelerators exchange data inside a rack, making its design material to sustained system performance.
Once AMD begins Helios shipments in the second half of 2026, Microsoft still needs to define its commitment by disclosing the number of systems assigned to Azure.
