Cloud & infrastructure

OpenShift Virtualization on Azure: What Is Announced vs Available Now

Red Hat and Microsoft announced direct virtualization for OpenShift on Azure. See what is roadmap, what you can deploy today, and how it compares for VMware exits.

By EpiFive Editorial TeamReviewed/updated 12 min readHow we check our guides
On this page

Red Hat and Microsoft announced on 18 November 2026 that they are working on "direct virtualization" for OpenShift Virtualization on Azure Red Hat OpenShift (ARO), but the announcement gives no availability date. What you can deploy today is the existing OpenShift Virtualization add-on on ARO standard clusters, Azure VMware Solution, or a lift to native Azure VMs.

This guide separates the announcement from the shipping products, then compares the three routes a VMware shop can take into Azure using the same criteria for each. Pricing is left out on purpose, because none of the pages used here gives a figure you can rely on for your own agreement.

Who this is for and what you will have at the end

This is for infrastructure leads and Azure administrators who run VMware today, are reconsidering it after the licensing changes covered in VMware Licensing After Broadcom: VCF, VVF, Core Counts and Minimums, and read the Ignite headlines about OpenShift on Azure.

At the end you will have a short list of what was announced versus what exists, a comparison table of three migration routes, a prerequisite checklist for OpenShift Virtualization on ARO, and a list of questions to put to your Microsoft or Red Hat representative.

What was announced on 18 November 2026

Red Hat's press release, titled "Red Hat Deepens Collaboration with Microsoft to Power the Future of Enterprise Virtualization", says the following. Each point is Red Hat's wording summarized, not a tested result.

  • Microsoft's direct virtualization technology is meant to give Linux-based and cloud-native platforms running on Azure VMs the virtualization, performance and hardware access that Azure-native services already have.
  • The approach changes Azure's compute architecture so enterprise Linux connects more directly to hardware. It runs lightweight Linux kernels in micro VMs and provides a direct path to hardware such as GPUs.
  • Red Hat is a launch partner for the technology in OpenShift Virtualization on ARO, and Microsoft says ARO is among the first commercial platforms to offer it.
  • The release lists three capabilities: broad availability across popular Azure regions and VM sizes, managed CPU and memory overcommit, and kernel-level isolation for sensitive workloads.
  • Red Hat and Microsoft are co-developing upstream in KubeVirt, libvirt, QEMU and the Linux kernel. Microsoft is one of the first KubeVirt vendors to extend the project to a non-KVM hypervisor, by adding support for Microsoft's hypervisor.
  • Red Hat's Migration Toolkit for Virtualization is cited as a path off legacy hypervisors.

What the announcement does not say

The release gives no general availability date, no region list and no rollout schedule, and it labels nothing as preview or generally available. The wording is forward-looking ("is working with"). The release also does not mention hosted control planes or BGP, so do not infer anything about those from it.

Treat "broad availability", "overcommit" and "kernel-level isolation" as vendor claims. There are no published numbers to compare, so test your own workloads before you rely on them.

What you can deploy today

OpenShift Virtualization on Azure Red Hat OpenShift

Microsoft Learn (page dated 2026-10-22) describes OpenShift Virtualization on ARO as a self-managed add-on to OpenShift Container Platform that runs VMs alongside containers on the same cluster. Red Hat's blog announcing general availability is dated 2025-11-18 and also calls it a self-managed operator inside a fully managed ARO service.

Key requirements from the Microsoft page:

ItemWhat the page says
ArchitectureApplies to the standard architecture only
Cluster version4.18 or later
Node familiesDsv5, Dsv6 and Esv5 with 8 cores or more; Dsv6 is in preview from 4.19
QuotaAt least one D8sv5 SKU; a minimum of 52 cores for a cluster of three 8-core workers
StorageNeeds persistent volume storage; ODF, Azure NetApp Files (preview), Azure Disk and Everpure Cloud are listed as validated
Azure DiskLive migration is not supported with Azure Disk
Windows guestsWindows Server with active Software Assurance or subscription, through Azure Hybrid Benefit; Datacenter licenses can cover only one VM
RHEL guestsUnlimited guest subscriptions on hosts with 96 or more vCPUs; up to 8:1 guest-to-host vCPU below that

The two figures in the RHEL row give a calculation you can repeat: a host with 64 vCPUs, such as Standard_D64s_v5, can run up to 64 x 8 = 512 RHEL guest vCPUs.

The 52-core minimum comes straight from the page. Three workers of eight cores account for 24 of those cores; the page does not break down the rest, so check your control plane sizing in the cluster creation docs rather than assuming it.

Standard versus hosted control planes

ARO comes in two architectures. In the standard architecture the control plane runs on dedicated VMs in your subscription and a cluster needs three control plane nodes and three workers. With hosted control planes, Red Hat hosts the control plane in its own Azure account and you deploy only worker nodes, with a minimum of two. Microsoft's comparison page lists roughly 45 minutes to create a standard cluster versus about 15 to 20 minutes for hosted control planes.

Because the OpenShift Virtualization page says "Applies to: Standard architecture", a design that depends on hosted control planes and VMs together needs written confirmation from Microsoft or Red Hat first.

Azure VMware Solution

Microsoft Learn (page dated 2026-11-03) says Azure VMware Solution provides private clouds containing VMware vSphere clusters built from dedicated bare-metal Azure infrastructure. Every private cloud has vCenter Server, vSAN, vSphere and NSX.

  • The minimum initial deployment is three hosts, up to 16 hosts per cluster.
  • Two generations exist. Generation 1 connects hosts to Azure through Microsoft-managed ExpressRoute circuits. Generation 2 attaches hosts directly to Azure Virtual Networks and is supported only on the AV64 SKU.
  • New deployments list vCenter Server and ESXi 8.0 U3k, NSX 4.2.3.2 and HCX 4.11.5.
  • Microsoft manages the private cloud infrastructure and software; you manage VMs, guest operating systems, networking segments and migration to the cloud.

Azure Migrate: agentless migration to native Azure VMs

Microsoft's migration overview describes a free service for discovery, assessment and migration. Its overview page title now reads "Azure Catalyst" with the note "(formerly Azure Migrate)", while the VMware tutorial still uses the Azure Migrate name, so expect both names in the portal and docs for a while.

For VMware VMs the tutorial (page dated 2026-06-16) says you can use agentless or agent-based migration. Agentless uses the same appliance as discovery and assessment. Limits it states:

  • Up to 500 replications simultaneously.
  • Up to 10 VMs selected at once in the portal; add machines in groups of 10 to migrate more.
  • If Azure connectivity or appliance services are unavailable for more than 90 minutes, the replication cycle resets from 0%.
  • No agentless migration for VMs with a VMDK name containing non-ASCII characters.

The tutorial's flow runs from Manage > Server replication > Start replication, a test migration into an isolated virtual network, then Migrate.

Comparing the three routes

The same six criteria apply to each route, in the same order. Nothing here is a ranking.

CriterionAzure VMware SolutionAzure Migrate to Azure VMsOpenShift Virtualization on ARO
What you run afterwardvSphere, vSAN, NSX on dedicated Azure hostsNative Azure VMsKubeVirt VMs on OpenShift
Tooling change for adminsSmallest; same VMware stackLarge; Azure VM tooling replaces vCenterLarge; OpenShift and Kubernetes tooling
Entry sizeThree-host minimum clusterPer VMCluster with 8-core or larger nodes
Migration toolingHCX and vMotion are in the customer responsibility listAzure Migrate applianceRed Hat Migration Toolkit for Virtualization
Stated limits worth checkingRegion and SKU availability; AV64 rules500 replications; groups of 10Standard architecture only; 4.18+; Azure Disk has no live migration
Licensing notesCheck VMware terms as covered in the related postAzure Hybrid Benefit offered during replication setupAzure Hybrid Benefit with a label on Windows VMs; RHEL guest subscriptions by host vCPU

Best fit by situation

  • A team that wants to keep VMware tools and skills while leaving its own hardware: Azure VMware Solution, with the caveat that you still depend on the VMware software stack.
  • A team ready to rebuild around native Azure services: Azure Migrate to Azure VMs.
  • A team already standardizing on OpenShift or going container-first: OpenShift Virtualization on ARO today, with direct virtualization as a future option to watch.

Downsides to weigh

Azure VMware Solution carries the three-host minimum. Azure Migrate needs per-VM validation and gives you a different operating model afterward. OpenShift Virtualization on ARO is self-managed at the virtualization layer, so your team operates the operator, and the storage choices have gaps, since Azure NetApp Files is in preview and Azure Disk blocks live migration.

A prerequisite check for OpenShift Virtualization on ARO

Before you budget for a pilot, confirm each item against the Microsoft page.

  1. The cluster uses the standard architecture, not hosted control planes.
  2. The cluster version is 4.18 or later. The page links the ARO release calendar for versions.
  3. At least one worker is a Dsv5, Esv5 or preview Dsv6 node with 8 or more cores.
  4. Subscription quota covers the cluster, with a minimum of 52 cores for three 8-core workers.
  5. A storage class suits your needs, noting the Azure Disk live migration limit.
  6. Windows VMs carry the Azure Hybrid Benefit attestation label.

For step 6, the page shows this label on the VirtualMachine object:

metadata:
  labels:
    azure.microsoft.com/windows-ahb-attestation: "true"

Then install the OpenShift Virtualization operator using the Red Hat installation guide the page links, and create VMs from there. For many workloads, the page points to the Migration Toolkit for Virtualization.

If you are checking the Dsv6 route, the page notes that the MachineSet needs image.sku set to 419-v2 and image.version set to 419.6.20250523, and gives the command az vm image list --architecture x64 -o table --all --offer aro4 --publisher azureopenshift to find the values.

Questions to ask your Microsoft or Red Hat representative

  • Which ARO architectures will direct virtualization support, standard, hosted control planes or both?
  • What is the planned availability by region and VM size, and is it preview or general availability at launch?
  • What are the support boundaries between Red Hat and Microsoft for the virtualization layer?
  • Which VM sizes will be supported, and does the current 8-core minimum change?
  • Which storage options will support live migration?
  • How do Azure Hybrid Benefit and RHEL guest subscriptions apply to the new model?

Troubleshooting planning problems

SymptomLikely cause and next step
A hosted control planes cluster cannot enable OpenShift VirtualizationThe Microsoft page applies to the standard architecture only; create a standard cluster for the pilot
VM live migration fails on OpenShiftThe VM disk may be on Azure Disk, which does not support live migration; use a storage option that does
A VM size is not accepted for virtualizationCheck that the family is Dsv5, Esv5 or preview Dsv6, with 8 cores or more
Azure Migrate replication restarts at 0%A connectivity or appliance outage lasted more than 90 minutes; fix connectivity and monitor the project
Only 10 VMs can be selected for migrationThat is the portal limit; add the rest in batches of 10

Closing checklist

  • Write down which of your VMs are Windows, RHEL or other, since licensing differs by route.
  • Pick a pilot workload for each route you are considering and test it, instead of relying on vendor claims.
  • Do not plan production capacity around direct virtualization until a dated availability page exists.
  • Re-check the Microsoft pages when the availability update appears, because several of them were edited this month.

How we evaluated

The six criteria in the table are what a VMware team has to decide on: what you run afterward, how much admin tooling changes, the minimum entry size, the migration tooling, the documented limits, and licensing notes. Each product's facts come from its own vendor pages, opened on 2026-11-21: Microsoft Learn for Azure VMware Solution, Azure Migrate and ARO, and Red Hat for the announcement and the general availability blog. No competitor or review site was used for any product's facts. Not tested hands-on; based on each vendor's documentation as of 2026-11-21.

See also

What we checked

  • Opened Red Hat's 18 November 2026 press release on 2026-11-21 and recorded the capabilities listed above; confirmed it gives no GA date, region list or rollout schedule and does not mention hosted control planes or BGP.
  • Opened Microsoft Learn's OpenShift Virtualization for ARO page on 2026-11-21 (ms.date 2026-10-22): the 4.18 requirement, node families, 52-core minimum, storage list and the standard-architecture-only scope.
  • Cross-checked that scope against the ARO standard versus hosted control planes comparison page (updated 2026-11-17), which lists the control plane, node count, creation time and billing differences.
  • Opened Red Hat's blog on OpenShift Virtualization general availability on ARO; its date is shown as 2025-11-18 and it describes a self-managed operator.
  • Opened the Azure VMware Solution introduction (ms.date 2026-11-03) and the Azure Migrate overview and VMware agentless tutorial; the limits quoted come from those pages.
  • Recalculated: 64 host vCPUs x 8 = 512 RHEL guest vCPUs; 3 workers x 8 cores = 24 of the 52-core minimum.
  • Not checked: no cluster, subscription or VMware environment was used; steps follow documentation as of 2026-11-21. Pricing, the Microsoft Ignite announcement pages and the Red Hat availability update page were not read, so no price or date for direct virtualization is stated.

Last tested: 2026-11-21

References

Questions people ask

Is direct virtualization for OpenShift Virtualization on Azure generally available?

Red Hat's 18 November 2026 press release describes it as joint work in progress and gives no general availability date, region list or rollout schedule. It does not label any part as preview or GA. What you can deploy today is OpenShift Virtualization on Azure Red Hat OpenShift as documented by Microsoft Learn.

Does OpenShift Virtualization run on Azure Red Hat OpenShift with hosted control planes?

Microsoft's OpenShift Virtualization page for ARO says it applies to the standard architecture only. The hosted control planes architecture is documented separately and the page does not list OpenShift Virtualization for it. Check that page again before you plan a design around hosted control planes.

What are my main options for moving VMware VMs into Azure?

Three documented routes are Azure VMware Solution (keep vSphere on dedicated Azure hosts), Azure Migrate agentless migration to native Azure VMs, and OpenShift Virtualization on ARO for teams going container-first. Each has different operating effort, so match the route to how much of the VMware stack you want to keep.

Which Azure VM sizes does OpenShift Virtualization on ARO support?

Microsoft lists Dsv5 and Esv5 families with eight or more cores on cluster version 4.18 and later, and Dsv6 as a preview from 4.19. Smaller sizes are not listed as supported.

OpenShift VirtualizationAzure Red Hat OpenShiftAzure VMware SolutionAzure MigrateKubeVirt