What was announced
Azure Red Hat OpenShift (ARO) will be one of the first commercial workload-hosting platforms to offer these capabilities. The work spans several layers:
- Red Hat and Microsoft are co-developing upstream capabilities in KubeVirt, LibVirt, QEMU and the Linux kernel. KubeVirt is the standard for managing VMs alongside containers on Kubernetes.
- Microsoft is one of the first vendors in the KubeVirt community to extend the project to a non-KVM hypervisor. This adds Microsoft's hypervisor as another option. It does not remove KVM.
- Microsoft is working with Red Hat to evolve Azure's compute architecture so it can interface natively with enterprise Linux through direct virtualization.
Red Hat also describes the mechanism. Direct virtualization runs lightweight Linux kernels in micro VMs. That is meant to give isolated workloads a direct pipeline to hardware such as GPUs. These are vendor descriptions, and no design paper or benchmark accompanied them.
Why direct virtualization matters
A Microsoft Tech Community post on direct virtualization gives useful background. Instead of nesting a second hypervisor, it provides a direct path between strongly isolated sandboxes and Azure's underlying virtualization platform. The same post says Microsoft and Red Hat are collaborating so OpenShift Virtualization can use direct virtualization on Azure Red Hat OpenShift.
The practical reading is that OpenShift Virtualization currently runs VMs on top of Azure VMs. Cutting out the nested layer is the point of this work. The Microsoft post says it preserves isolation while reducing the overhead of a nested hypervisor.
What customers are promised
Red Hat lists three intended benefits:
- Broad availability: across popular Azure regions and VM sizes.
- Efficiency: consolidation per VM through managed CPU and memory overcommit, which Red Hat says will cut stranded capacity and total cloud costs.
- Isolation: kernel-level isolation to protect sensitive AI and enterprise workloads.
No region or SKU list, overcommit ratios, cost comparisons or performance figures were published. Treat these as goals, not measured results.
Launch partner, not launch date
Red Hat says it is among the first launch partners for the technology. It also points to its Migration Toolkit for Virtualization as a path off legacy hypervisors. The release names no source hypervisors and no supported migration scenarios.
Red Hat frames the timing around rising hypervisor licensing costs, hardware scarcity and AI demand. ITdaily observed that VMware is not named, but Red Hat increasingly positions OpenShift as an alternative. That is the trade press's reading, not a claim in the announcement.
What already exists on ARO
OpenShift Virtualization on ARO is not new. It went into public preview as a self-managed operator on ARO. Microsoft's release notes record general availability in November 2025. IT Social notes it has run in public preview since May 2025 on conventional Azure VMs. The new element is the direct-virtualization path and the upstream non-KVM support.
Microsoft's current documentation describes the existing offering, which may not match the new capability's prerequisites:
- It is a self-managed add-on that runs VMs alongside containers on the same cluster. That matches the description in Microsoft Learn.
- It requires OpenShift 4.18 or later.
- It supports only Dsv5, Dsv6 and Esv5 nodes with eight or more cores. Dsv6 is in preview from 4.19.
- It requires persistent storage. Azure Disk does not support live migration.
- Windows Server VMs are supported through Azure Hybrid Benefit. A Datacenter license covers only one OpenShift Virtualization VM, and each Windows VM needs an attestation label.
- RHEL guest subscriptions are included. Hosts with 96 or more vCPUs get unlimited guests, and smaller hosts allow up to 8:1 guest-to-host vCPU.
Microsoft's release notes also show September 2026 support updates for Esv5, Easv5 and Dasv5 instances. Support boundaries are evolving. "Popular regions and VM sizes" should not be read as universal coverage until a feature-specific list appears.
Why Windows and Azure admins should care
For shops with Windows Server VMs, the Azure Hybrid Benefit and licensing rules above are the first thing to check. They govern how Windows workloads can be hosted on OpenShift Virtualization. Teams weighing a move away from their current hypervisor should treat this as a roadmap item and plan around what is documented today.
Brendan Burns of Microsoft said the open-source work means other cloud-native VM platforms can also build on it, as the Red Hat release states. IT Social reads this as Azure becoming a destination for several virtualization solutions, not just Red Hat's.
What to watch
- A published availability list of regions and VM sizes
- Prerequisites, including OpenShift version and storage
- Licensing and pricing, including how MACC consumption commitments apply
- Independent performance and density results
- Upstream KubeVirt code and release details for the Microsoft hypervisor support
Until those arrive, this is a credible direction backed by upstream work, not a deployable feature. The claims on cost, consolidation and isolation come from the vendors and remain unverified.
References
- Red Hat Deepens Collaboration with Microsoft to Power the Future of Enterprise Virtualization AiThority · 2026-11-19T08:01:16+00:00
- Red Hat and Microsoft strengthen collaboration on virtualisation on Azure: a lure for VMware customers? - ITdaily itdaily.com
- OpenShift Virtualization for Azure Red Hat OpenShift - Azure Red Hat OpenShift | Microsoft Learn learn.microsoft.com