Azure VMware Solution

About Azure VMware Solution

Azure VMware Solution is a Microsoft Azure service for organizations that need to move or extend existing VMware environments without immediately redesigning every workload for native cloud services. It provides VMware private clouds in Azure with vSphere, vSAN, NSX, and vCenter on Microsoft managed infrastructure. The strongest fit is usually an enterprise with a significant VMware estate, a data center exit deadline, or applications that would be expensive or risky to refactor before migration. It is not a low cost replacement for ordinary Azure virtual machines. Buyers should evaluate host commitments, VMware licensing, network design, migration tooling, capacity planning, and long term modernization plans before choosing it.

What does Azure VMware Solution provide?

Azure VMware Solution provides a VMware software defined data center environment inside Azure. Microsoft operates and maintains the underlying service infrastructure while customers continue to use familiar VMware administration concepts and tools. Current Microsoft documentation describes private clouds that include VMware vCenter Server, vSphere, vSAN, and NSX. This allows teams to migrate supported VMware virtual machines, create new VMs inside the private cloud, and connect workloads to native Azure services.

The service is designed around dedicated capacity rather than shared general purpose cloud VMs. That distinction matters for cost and planning. A private cloud is built from clusters, and each cluster requires at least three hosts. Microsoft currently documents a maximum of 16 hosts per cluster, up to 12 clusters per private cloud, and up to 96 ESXi hosts per private cloud.

Who is Azure VMware Solution for?

Azure VMware Solution is best suited to organizations that already operate substantial VMware estates and need a lower change migration path. Common scenarios include data center exits, hardware refresh avoidance, mergers that require infrastructure consolidation, disaster recovery designs, and migrations where application teams cannot refactor immediately.

It can also support a phased modernization strategy. A company can first move workloads into a familiar VMware environment in Azure, then selectively adopt services such as Azure Monitor, Azure Backup, Azure Site Recovery, Azure SQL, or other Azure platform capabilities. This staged approach can reduce migration risk, but it only makes sense when the cost of maintaining VMware compatibility is justified by the workloads being moved.

How do private clouds, clusters, and host sizes work?

Azure VMware Solution private clouds contain one or more vSphere clusters. Microsoft currently requires at least three hosts per cluster. Capacity is added at the host level, so buyers need to plan around discrete host increments rather than the smaller VM level increments available with normal Azure compute.

Microsoft documents several host families, including AV36, AV36P, AV48, AV52, and AV64 in supported regions and configurations. The exact host options available depend on region and private cloud generation. Generation 2 uses an updated architecture where VMware hosts attach directly to Azure virtual networks and is currently associated with AV64 deployments. Because host availability and regional support can change, buyers should validate the current Azure region matrix before committing to a design.

What changed with VMware licensing?

A major current buying consideration is VMware Cloud Foundation licensing. Microsoft's current Azure VMware Solution deployment and pricing documentation states that customers must provide a portable VMware VCF subscription from Broadcom for current host configurations. The Azure deployment workflow asks for VCF licensing details such as the license key, site ID, serial number, expiration date, and deployed VCF core count.

This means the Azure infrastructure cost and the VMware software entitlement should be evaluated together. A buyer should not treat the Azure host price as the entire cost of the service. Existing Broadcom agreements, renewal timing, required VCF cores, and the ability to use portable licenses can materially change the business case.

How does Azure VMware Solution pricing work?

Pricing was checked against Microsoft's current Azure VMware Solution pricing page on August 27, 2026. Microsoft prices the service primarily by dedicated host capacity, with rates depending on the host SKU, region, billing offer, and commitment option. The current pricing page lists hourly pricing and, for selected host sizes, one year, three year, or five year reservation options.

Microsoft also notes that all current Azure VMware Solution host sizes require customers to provide a portable VMware VCF subscription from Broadcom. Additional costs can come from networking, ExpressRoute, backup, monitoring, migration tooling, data transfer, and other Azure services used around the private cloud. Buyers should model the complete environment rather than comparing only the host meter with an on premises server purchase.

How does networking connect VMware workloads to Azure and on premises environments?

Networking is a core design dependency. Generation 1 private clouds use Microsoft managed ExpressRoute connectivity to reach Azure virtual networks, while Generation 2 uses a newer architecture in which the VMware hosts attach directly to Azure virtual networks. On premises connectivity can use ExpressRoute Global Reach where supported, and other Azure networking services may also be part of the architecture.

Address planning must be completed before deployment. Microsoft requires a management address block for the private cloud, and it must not overlap with Azure virtual networks or on premises address space. Teams should also plan DNS, firewall rules, routing, internet access, and the location of shared services before migrating production workloads.

What reliability and capacity limits should buyers plan around?

Microsoft documents a minimum of three ESXi hosts per cluster and a maximum of 16. A private cloud can contain up to 12 clusters and up to 96 ESXi hosts. The service uses vSphere High Availability, vSAN resilience, and redundant networking to handle infrastructure faults, but application level resilience is still the customer's responsibility.

Microsoft also recommends keeping vSAN capacity headroom because storage policies and service level requirements depend on available capacity. Buyers should understand host failure behavior, maintenance events, vSAN policy choices, cluster sizing, and recovery requirements before treating the service as a simple lift and shift target.

How does migration work?

Azure VMware Solution is designed to reduce the amount of change required during VMware migration. VMware HCX is commonly used for migration and network extension scenarios, while standard VMware tooling remains familiar to existing administrators. Microsoft also provides Azure Migrate guidance for assessing VMware estates before migration.

The migration plan should still include dependency discovery, network mapping, performance baselines, test migrations, rollback procedures, identity and DNS validation, and post migration cost checks. Moving a VM without refactoring the application can accelerate a data center exit, but it does not automatically improve architecture, licensing efficiency, or operational cost.

What are the main limitations and tradeoffs?

The first tradeoff is cost granularity. Because the service uses dedicated hosts with a minimum cluster size, it is usually a poor fit for small VMware estates or workloads that could run efficiently on ordinary Azure VMs, App Service, Container Apps, or other managed services.

The second tradeoff is platform dependency. Azure VMware Solution preserves VMware operating models, which is useful during migration but can delay cloud native modernization if there is no plan beyond relocation. Teams still need VMware skills, Azure networking knowledge, capacity management, and a current Broadcom licensing strategy.

Regional host availability, quota, deployment lead time, and network design also require advance planning. Microsoft notes that creating a private cloud can take several hours, and host quota may need approval before deployment.

Who should choose something else?

Choose ordinary Azure Virtual Machines when you need infrastructure as a service but do not need a complete VMware software defined data center. Choose Azure Kubernetes Service or Azure Container Apps when the real goal is container modernization. Choose App Service or Functions when applications can move to a managed platform model. For database heavy workloads, a managed Azure database can remove more infrastructure responsibility than carrying the existing VMware stack forward.

Azure VMware Solution is strongest when preserving VMware compatibility has real business value. It is less compelling when the workload estate is small, the organization has already committed to cloud native redesign, or dedicated host economics are difficult to justify. A migration program should therefore compare the cost and risk of rehosting in Azure VMware Solution with replatforming and refactoring alternatives, not assume that the least disruptive technical path is automatically the best long term choice.