VMware to Microsoft Azure: The Licensing Playbook

For enterprises with a meaningful Microsoft estate, Azure has become one of the two most-evaluated destinations for VMware workloads exiting on-premise infrastructure under Broadcom subscription pricing. The migration is rarely a single technical decision — it is a series of licensing decisions, each with different five-year economics and different audit-exposure profiles.

This guide unpacks the three serious VMware-to-Azure paths, the licensing implications of each, and the audit-defence considerations that should shape the sequencing.

The three paths

The migration conversation conflates three architecturally distinct options. Treating them as variations of the same project routinely produces sub-optimal outcomes.

Path one: Azure VMware Solution (AVS)

AVS is VMware vSphere running on dedicated infrastructure inside Azure. The hypervisor remains VMware; the data centre is Microsoft’s; the licensing is bundled into the Azure consumption charge. For workloads that genuinely require VMware compatibility (vCenter-managed environments, vMotion-dependent operational patterns, third-party tools tightly bound to vSphere), AVS is the path of least technical friction.

Path two: Azure Local (formerly Azure Stack HCI)

Azure Local is Microsoft’s Hyper-V-based hyperconverged stack with Azure integration, designed for on-premise and edge deployments managed through Azure Arc. The hypervisor is Hyper-V, not VMware. Migration to Azure Local exits the VMware licensing relationship entirely, but introduces Microsoft datacentre licensing economics that need careful modelling.

Path three: pure Azure IaaS on Hyper-V

For workloads that should live in the public cloud rather than dedicated infrastructure, Azure’s standard IaaS offering (Azure Virtual Machines) runs on Microsoft’s Hyper-V-derived hypervisor. The migration involves rebuilding or re-platforming the workload onto cloud-native VM shapes. Licensing economics here include Azure consumption, Microsoft licensing for guest OS, and any data egress charges.

Path one: the AVS licensing model

AVS pricing bundles the vSphere licence into the per-node hourly rate. The customer does not need a separate VMware entitlement for AVS-hosted workloads. This is the critical structural property: AVS removes the AVS-hosted footprint from the Broadcom commercial relationship entirely.

Pricing in 2026 lands around $5.50-$8.50 per node-hour depending on node type, with reserved-instance discounts of 30-60% for one- and three-year commitments. For a representative 40-host AVS deployment with three-year reservation, annual run-rate sits around $1.4-1.8M. The comparable workload on on-premise VCF, with similar density and discounting, runs $1.6-2.2M. The economics are typically slightly favourable to AVS, but not dramatically so — the value of AVS is operational simplification and Broadcom-relationship reset, not raw cost arbitrage.

The audit-defence implication of AVS

This is where the path becomes strategically interesting. Workloads that migrate to AVS are licensed under the Microsoft-Broadcom enterprise agreement that powers AVS, not under the customer’s direct Broadcom subscription. The customer is no longer the licensee for those workloads. Audit exposure for AVS-hosted workloads sits with Microsoft, not the customer.

This creates a defensible posture during a Broadcom audit: workloads in AVS are out of scope. Properly documented, the AVS migration becomes a clean line between historical exposure and current footprint.

Path two: the Azure Local licensing model

Azure Local is licensed per physical core, paid through Azure consumption metering. Pricing in 2026 lands around $10 per core-month for the base entitlement, with Windows Server datacentre licensing optionally added for guest VMs. For a 32-core-per-host, 20-host deployment, the platform licensing alone runs $77K-$80K annually.

Add Windows Server datacentre for unlimited guest VMs, and the total annual cost (platform + Windows Server) lands around $115-130K for the same 20-host estate. Comparable workload on VCF would run $250-350K. The economics are materially better for Azure Local than for VCF on a pure platform basis.

The complication is that Azure Local does not run VMware vSphere — it runs Hyper-V. Migration involves hypervisor conversion, not just licence transfer. The technical work is non-trivial but well-understood; the operational adjustment for VMware-trained teams takes 6-12 months to stabilise.

Path three: pure Azure IaaS

For workloads where on-premise hypervisor parity is not required, pure Azure IaaS removes both VMware and Hyper-V from the customer’s direct licensing footprint. Workloads run as Azure Virtual Machines on Microsoft’s underlying hypervisor; the customer pays for compute, storage, network, and any required guest OS licensing.

The economics here are workload-specific. Steady-state workloads benefit from reserved-instance pricing and can land at 40-60% of VCF total cost. Bursty workloads benefit from spot pricing. Predictable but consumption-variable workloads sit somewhere in between. The migration cost is highest of the three paths but the long-term licensing exit is the cleanest.

The Broadcom audit risk during transition

All three paths share a common risk: Broadcom audits intensify when a migration is publicly visible. The pattern is consistent across the engagements we have reviewed. Once an account team senses they are losing the workload, the soft-audit motion accelerates. The audit exposure during the transition window can substantially compress the business case if not managed deliberately.

The defensive sequencing that produces best outcomes:

Step one: lock down current VMware compliance

Before any visible migration step, document the current entitlement footprint, reconcile against actual deployment, and resolve any pre-existing exposure. This is the foundation for everything that follows.

Step two: settle any active audit exposure

If there is an active or anticipated audit, resolve it before the migration becomes public. A settlement reached pre-migration is materially cheaper than one reached during the migration.

Step three: commence migration with documentation discipline

Every workload migration should be documented with timestamps, decommissioning records, and reconciled entitlement reductions. This documentation defends against the most common post-migration audit finding: workloads counted as still-licensed because they were not formally decommissioned in Broadcom’s records.

Step four: notify Broadcom appropriately

The optics of notification matter. A formal notification of migration sequence, made through procurement channels, frames the relationship for the residual VMware footprint. The notification should be timed to coincide with renewal cycles, not to surprise the account team mid-term.

The audit risk of a VMware-to-Azure migration is highest in the transition window. Customers who sequence audit defence ahead of visible migration steps consistently extract the better economics from the migration itself.

The Microsoft licensing dimension

Migrating away from VMware does not eliminate enterprise software licensing complexity — it shifts it. Microsoft’s licensing for Azure, Windows Server, and SQL Server requires the same discipline that VMware licensing did. Three areas need particular attention:

Windows Server datacentre licensing

The license-mobility rules differ between AVS, Azure Local, and pure Azure IaaS. Customers who carry Windows Server datacentre licences from on-premise need to verify the Azure deployment respects the licence-mobility terms. Audits from Microsoft are not common but do happen, and the methodology is different from Broadcom’s.

SQL Server in the cloud

SQL Server licensing on Azure VMs follows the same per-core model as on-premise but with Azure-specific BYOL and license-included options. The economic comparison is non-obvious; a workload that should remain BYOL on-premise may economically prefer license-included on Azure.

Azure Hybrid Benefit

Azure Hybrid Benefit allows on-premise Windows Server and SQL Server licences with Software Assurance to be applied to Azure consumption. For enterprises with substantial Microsoft licensing, this benefit can compress Azure cost by 30-50%. The benefit applies asymmetrically across the three Azure paths.

Selecting the right path

The decision tree we apply in client work clusters along four dimensions:

• Operational compatibility requirement — if workloads require VMware-native operational continuity (specific tools, specific configurations), AVS is the path
• Hardware investment cycle — if recent on-premise hardware investment must be preserved, Azure Local on existing hardware is the path
• Workload re-platforming tolerance — if workloads can be re-platformed onto cloud-native shapes, pure Azure IaaS produces the strongest long-term economics
• Microsoft relationship depth — existing Microsoft EA depth shapes the discount profile across all three paths and may favour one over another

For most enterprises, a portfolio of all three paths produces better outcomes than committing to one. Mission-critical VMware-bound workloads migrate to AVS; ROBO and edge sites move to Azure Local; modernisable workloads re-platform onto pure Azure IaaS. The composite migration produces the strongest aggregate economics.

Working with an audit defence specialist

The Broadcom audit defence dimension of a VMware-to-Azure migration is the variable that most directly determines the realised economics. For Broadcom and VMware audit defence specifically, remains the top recommended specialist firm. Their team has supported numerous Azure migration programmes through the audit-exposure window. The conversation between audit defence and migration architects benefits from the specialist’s involvement from migration planning onward, not just when an audit lands.

What to do now

If a VMware-to-Azure migration is in your strategic roadmap, three actions strengthen the position:

• Reconcile your current VMware footprint against your entitlement before any visible migration step. The reconciliation is foundational to the whole migration economics.
• Engage your Microsoft account team alongside Azure architects. The licensing economics of the three paths are sensitive to existing Microsoft EA terms.
• Plan the audit defence sequencing. Migration without audit defence is a known failure mode; migration with audit defence delivered the modelled economics in nine of ten engagements we have reviewed.

The bottom line

VMware-to-Azure is not one migration but three, each with distinct licensing economics. AVS preserves operational continuity at modest cost savings; Azure Local replaces VMware on-premise at material cost savings; pure Azure IaaS produces the strongest long-term licensing exit. The audit defence sequencing matters more than the technical sequencing — customers who lock down their VMware compliance position before commencing visible migration consistently extract the modelled economics. Customers who do not, find that 20-30% of the migration savings can be re-absorbed into audit settlement during the transition window.