Azure Virtual Desktop (AVD) has always been a cloud-native VDI service. But starting this week, that description needs an asterisk — because Microsoft just made AVD truly hybrid.

On May 4, 2026, Microsoft moved AVD for hybrid environments with Arc-Enabled Servers from limited preview to public preview. The headline capability: you can now deploy AVD session hosts on any on-premises hypervisor or even bare-metal Windows Server, connected through Azure Arc. The control plane stays in Azure, but your session hosts can live anywhere the Arc agent can run.

For organizations that have been waiting for a viable on-ramp from legacy VDI — Citrix, Omnissa (formerly VMware Horizon), or traditional RDS — this is the moment the calculus shifts.

What’s Changing

AVD on Any Infrastructure

Previously, running AVD session hosts outside of Azure meant using Azure Local (formerly Azure Stack HCI), which required certified hardware and a specific Microsoft-managed stack. That option is still available, but the new hybrid capability strips away those requirements.

With this public preview, you can onboard any on-premises machine to Azure Arc and register it as an AVD session host. Supported environments include:

  • Microsoft Hyper-V — the default for many organizations already running Windows Server
  • VMware vSphere — no need to migrate VMs off VMware before adopting AVD
  • Nutanix AHV — direct integration for Nutanix shops
  • Any hypervisor that supports Windows virtual machines
  • Bare-metal Windows Server — physical servers can function as session hosts

How It Works

The architecture is clean: Azure handles brokering, identity (Microsoft Entra ID), workspace assignment, policy, and monitoring. Your on-premises machines, connected via the Azure Arc Connected Machine Agent, act as the session hosts. An AVD-specific Azure Arc extension (Microsoft.AzureVirtualDesktop.CloudDeviceExtension) registers each machine with the AVD service.

The result is a split control plane — cloud management, on-premises execution. Users connect through the familiar Windows App, and the experience is indistinguishable from a cloud-hosted AVD session.

What’s NOT Included (Important)

This is a public preview, and there are meaningful limitations to be aware of:

  • Validation host pools only. You cannot deploy this on production host pools during preview. Doing so would require redeployment at GA.
  • No VM provisioning or power management. Auto-scale, Start VM on Connect, and session host configuration are not supported. Organizations are responsible for managing their hypervisor’s lifecycle tools or using partner solutions.
  • Windows 11 Enterprise Multi-Session is not supported. Only Windows 11 single-session and Windows Server (2016–2025) are available. This limits density for organizations that rely on concurrent user consolidation.
  • PowerShell/CLI deployment only. There is no portal wizard yet — you register hosts by installing the Arc extension via script.
  • No session host configuration. Standard host pools only.

What This Means for Enterprise IT

A Migration Path from Legacy VDI

This is, without question, the biggest takeaway. Organizations running Citrix or Omnissa on on-premises hypervisors have been stuck — the cost and complexity of migrating to a fully cloud-native VDI was a barrier. Now you can replace the legacy control plane with AVD’s cloud-native brokering while keeping your existing hypervisor, storage, and network infrastructure.

The migration becomes incremental rather than forklift: modernize the management layer first, then move session hosts to Azure at your own pace.

Data Residency and Compliance

For financial services, healthcare, and government organizations where data sovereignty is non-negotiable, AVD Hybrid eliminates the compromise. Session host data stays on-premises. Only control and metadata traffic flows to Azure. This satisfies strict regulatory requirements without sacrificing the security and governance benefits of Microsoft’s cloud — Azure Policy, Microsoft Defender for Cloud, and Microsoft Sentinel all extend to Arc-connected servers.

Latency-Sensitive Workloads

Applications that demand low latency — CAD/CAM, real-time process monitoring, voice workloads — can now benefit from AVD without performance trade-offs. The session host lives in your datacenter, physically adjacent to backend databases and application servers, while the management plane remains in Azure.

Edge and Remote Office Scenarios

Remote offices with limited bandwidth to Azure benefit from local session hosts. Users get responsive desktop experiences while IT maintains centralized management, monitoring, and identity. RDP Shortpath (UDP) and RDP Multipath are both fully supported, ensuring optimal connectivity.

What Organizations Should Do

  1. Sign up for the public preview. Contact your Microsoft account team or use the preview interest form. This is the time to start testing.
  2. Set up a validation host pool. The preview requires validation environments — use this to build your deployment playbook.
  3. Test Arc onboarding. If you haven’t deployed Azure Arc in your on-premises environment, start with a proof of concept. Validate outbound connectivity, firewall rules, and private endpoint configuration.
  4. Evaluate partner tooling. Partners like Nerdio, ControlUp, and LoginVSI provide lifecycle management, scaling, and monitoring that fill the gaps left by the preview limitations. Assess which partners align with your operational model.
  5. Model your licensing costs. The preview is free, but GA pricing hasn’t been announced. Model Windows Server RDS CAL/SAL costs and partner tooling alongside potential Microsoft charges.
  6. Plan your legacy VDI exit. For organizations on Citrix or Omnissa, map out a phased migration: Arc onboarding of existing hypervisors → AVD control plane → gradual session host migration to Azure.
  7. Document what hasn’t changed. Your existing AVD deployments in Azure, Azure Local-based deployments, FSLogix profile strategy, and App Attach configurations are unaffected by this announcement.

What Has NOT Changed

  • AVD in Azure remains the primary deployment model and continues to receive all new features first.
  • Azure Local-based AVD is still supported and provides VM provisioning and power management that the hybrid preview lacks.
  • Windows 11 Enterprise Multi-Session remains available only on Azure and Azure Local — not on third-party hypervisors.
  • FSLogix, App Attach, and RDP features (Shortpath, Multipath) work the same way across all deployment models.
  • Identity, security, and governance capabilities (Microsoft Entra ID, Conditional Access, Azure Policy) remain consistent.

The Bigger Picture

This release is the clearest signal yet of Microsoft’s desktop virtualization strategy: AVD as the universal control plane for Windows desktops, wherever they run.

Azure Arc is the connective tissue. By extending Arc to AVD session hosts, Microsoft is creating a unified management layer that spans cloud, edge, and on-premises environments — with consistent identity, policy, security, and monitoring across all of them.

For organizations that have been managing separate VDI platforms for cloud and on-premises users, this convergence is significant. And for competitors like Citrix and Omnissa, the argument that “you need a third-party broker for hybrid VDI” just got a lot harder to make.

The public preview is early, and the limitations are real. But the direction is unmistakable: Microsoft is building AVD to be the single platform for Windows desktop delivery, full stop.

Need Help Navigating Azure Virtual Desktop Changes? Big Hat Group helps organizations design, deploy, and manage AVD environments — whether in Azure, on Azure Local, or across hybrid infrastructure with Arc-Enabled Servers. Contact us to assess your readiness, plan your migration, or build your deployment playbook.

Big Hat Group is a Microsoft partner specializing in Azure Virtual Desktop, modern endpoint management, and Microsoft 365 deployments.