VMware to Azure Migration: Licensing, Costs, and Commercial Strategy

Why Azure Migration Is on the Agenda Post-Broadcom

The Broadcom acquisition of VMware has put cloud migration back at the top of infrastructure strategy agendas in a way that was not true two years ago. Enterprises that had shelved cloud migration plans — or settled into a "cloud-adjacent" hybrid posture — are now re-evaluating, driven by VCF pricing that in some cases has increased their annual VMware spend by 200–400%.

For organisations already heavily invested in Microsoft Azure, Azure VMware Solution (AVS) represents a particularly compelling path: migrate the VMware workload to Azure-hosted VMware infrastructure, eliminate the on-premises Broadcom dependency, and consolidate cloud spend under an existing Microsoft relationship — potentially counting the spend against a MACC (Microsoft Azure Consumption Commitment).

This article covers the AVS licensing model in detail. For a broader comparison of VMware alternatives including on-premises options, see our VMware alternatives guide. For the full Broadcom commercial context, our Broadcom VMware Licensing Guide is essential background reading.

Azure VMware Solution: What It Is

Azure VMware Solution is a first-party Microsoft service that runs VMware vSphere, vSAN, and NSX-T on dedicated Azure bare-metal infrastructure. Broadcom licenses are handled by Microsoft — you do not have a direct commercial relationship with Broadcom for AVS workloads. The service is operated and supported by Microsoft, though VMware-layer technical issues involve Broadcom in the resolution chain.

From a technical standpoint, AVS is designed to be a near-identical VMware environment to what you run on-premises. Your existing VMs, VM templates, vSphere management skills, and VMware-compatible tools all work. The migration path is lift-and-shift at the vSphere layer — no application re-architecture required for the initial move.

AVS Pricing Model

AVS is priced per Azure VMware Solution node — dedicated bare-metal servers running in Azure datacentres. Each node is a high-specification server (typically 36+ cores, 576GB+ RAM, 15+ TB NVMe storage) and is billed on a per-hour or reserved instance basis.

The per-node model is fundamentally different from Broadcom's per-core model, which is an important factor in the cost comparison. A single AVS node typically equates to 36–64 cores of compute capacity, plus integrated storage (vSAN) and networking (NSX). When you compare the all-in cost of AVS (compute + storage + networking in a single node price) against VCF per-core pricing (compute only, with vSAN and NSX included in the VCF bundle), the economics are closer than a superficial comparison suggests.

A Worked Cost Comparison

An enterprise running 50 vSphere hosts (100 sockets, averaging 24 cores per socket = 2,400 licensed cores) under Broadcom VCF at $160/core/year pays approximately $384,000 per year. A comparable AVS deployment might require 8–12 AVS nodes depending on VM density and storage requirements. At 3-year reserved pricing, 10 AVS nodes cost approximately $400,000–$500,000 per year — a similar or marginally higher cost, but with the Broadcom relationship eliminated and Azure MACC credit eligibility.

The important variable is workload density. AVS nodes are high-specification servers — if your on-premises estate runs at low utilisation, you may need fewer AVS nodes than a direct host-for-host comparison suggests. Running a workload consolidation analysis before sizing AVS is essential.

Three Migration Paths to Azure

Azure Hybrid Benefit: The Licensing Multiplier

For enterprises with Microsoft Software Assurance on Windows Server and SQL Server licences, Azure Hybrid Benefit (AHB) allows those licences to be applied to Azure VMs — significantly reducing the Azure compute cost for Windows workloads. A Windows Server Datacenter licence with SA covers unlimited Windows VMs on the licensed physical server; in Azure, it covers a substantial number of Azure VM cores.

AHB can reduce the effective cost of running Windows Server workloads in Azure by 40–60% compared to fully-licensed Azure VM rates. For enterprises with significant Windows Server SA coverage, this is a material commercial factor in the migration economics. Our team models AHB impact as a standard part of any Azure migration cost analysis — it frequently changes the make-or-buy calculation significantly.

MACC Commitments and AVS Spend

If your organisation has a Microsoft Azure Consumption Commitment (MACC) — a committed Azure spend arrangement that provides overall commercial benefits — AVS spend typically qualifies toward that commitment. This is commercially valuable in two ways: it helps you meet an existing commitment you may be struggling to reach, and it consolidates your VMware infrastructure spend into the Microsoft commercial relationship where you may have more negotiating leverage overall.

Enterprises that are under-consuming their MACC commitments face financial penalties or reduced commercial terms at renewal. Directing VMware workloads to AVS as part of a migration programme is a strategic way to increase Azure consumption while resolving the Broadcom pricing problem simultaneously. Our Microsoft advisory service covers MACC negotiation and optimisation in detail.

Commercial Negotiation for the Azure Migration

The Azure migration path involves two commercial negotiations: the Broadcom exit (or transition) and the Microsoft AVS terms. Both can be improved with the right approach.

1. Use AVS as Broadcom Leverage First — Obtain a formal AVS assessment and rough sizing before entering the Broadcom renewal window. Present this as evidence that Azure migration is actively being evaluated. Broadcom consistently offers better terms when a credible cloud migration alternative is on the table.
2. Negotiate AVS Reserved Instance Pricing with Microsoft — AVS reserved instance pricing is negotiable as part of broader Azure commercial discussions. If you have a significant Azure footprint or MACC commitment, Microsoft has incentive to structure favourable AVS terms to win or retain the VMware workload.
3. Stagger the Migration and the Contract — If a phased migration is the plan, avoid committing to a 3-year Broadcom contract for the full current estate. Negotiate a shorter term (12–18 months) or reduced-scope contract that covers only the workloads that won't be migrated in the initial phase.
4. Model the Full TCO Including Migration Costs — AVS migration is not free. HCX professional services, network connectivity (ExpressRoute), Azure Migrate licensing, and internal IT resource costs all add to the migration programme cost. A full TCO model — not just a licensing comparison — is necessary for an informed decision.

IT Negotiations provides independent commercial advisory for both the Broadcom and Microsoft sides of this transition. We help enterprises avoid the common outcome of trading one overpriced contract for another. Request a free consultation to model the commercial economics for your specific estate, or review our Broadcom VMware advisory service and Microsoft advisory service for more detail on how we work.

Decision Framework: When AVS Makes Sense

Azure VMware Solution is the right path when several conditions are met simultaneously:

• You have a meaningful Azure relationship — MACC commitments, Azure-deployed workloads, or Azure-aligned cloud strategy. AVS spend counting toward MACC is a genuine differentiator versus other migration paths.
• Speed to exit Broadcom is a priority — AVS with HCX is the fastest path to getting VMware workloads off the Broadcom relationship. If time is a constraint, AVS wins on migration velocity.
• Your workloads have VMware dependencies — Applications that require specific VMware APIs, VMware-aware backup tools, or vSphere-native features are better served by AVS than a native Azure IaaS re-host.
• You have Windows/SQL Server SA — Azure Hybrid Benefit combined with AVS can deliver materially better economics than continuing to run on-premises with Broadcom pricing.

Where AVS may not be the right answer: estates with low workload density (where on-premises alternatives like Nutanix are more cost-effective), organisations without Azure commitments or cloud strategy, or environments where data sovereignty or latency requirements preclude cloud hosting.