Microsoft recently made Azure Virtual Desktop Hybrid generally available. Session hosts run on the customer’s own hardware and hypervisor, connected through Azure Arc, while session brokering and management stay in Azure. The pricing follows that split: per-user licensing for the service, with compute, storage, and networking costs remaining on-premises.

InfoQ covered the limited preview in November, when the capability extended beyond Azure Local to Hyper-V, Nutanix AHV, VMware vSphere, and physical Windows Servers. A public preview followed in March. The architecture is unchanged at general availability. Session hosts run in the customer datacenter, Azure Arc connects those machines to Azure, an extension configures the Arc VMs as session hosts, and users reach desktops and apps through Windows App. All communication is outbound over HTTPS, which removes the need for inbound connectivity.

Azure Virtual Desktop Hybrid architecture (Source: Microsoft)

Steve Downs, who announced both the preview and the general availability, frames the release around organizations facing constraints that make a full cloud migration difficult in the near term.

What has changed is that the deployment path is now documented rather than gated behind an interest form. Creating a VM, installing and configuring Azure Arc, installing the extension, and selecting a host pool can all be done from the Azure portal.

The reaction to the announcement has been consistent on one point: nobody can price it yet.

Azure Virtual Desktop Hybrid requires OS user entitlement licensing plus a separate Azure Virtual Desktop Hybrid service license. Microsoft’s documentation says details on the second are still to come. Four of the first commenters on the announcement asked about it.

One, an MVP, put it briefly in the announcement comments:

As others already said, pricing is going to be the key here.

Another asked how to calculate the difference in price when using Hybrid. A second MVP asked how the service fee should be calculated at all, and whether it matches the existing fee for running Azure Virtual Desktop on Azure Local. None of those questions has been answered.

A partner who has been testing Hybrid since it was presented at Ignite 2025 raised a sharper problem. The documentation supports Windows Server only when RDS Client Access Licenses carry Software Assurance:

This requirement alone kills around 90% of our potential customer deployments since most of our customers have no SA on their RDS CALs or have recently purchased RDS CALs with Windows Server 2025 / 2022 without SA, so a relicensing to RDS User Subscription is not economically feasable.

He also noted the double charge, asking whether the Hybrid user license fee required on top of the RDS CALs could absorb the Software Assurance requirement rather than sit alongside it.

That constraint compounds a second one. Windows 11 and Windows 10 Enterprise multi-session are not supported on Hybrid, so the licensing model that underpins most Azure Virtual Desktop deployments does not carry over. Supported options are Windows Server 2016 through 2025 with RDS Client Access Licenses carrying Software Assurance, or single-session Windows 10 and 11 Enterprise through Microsoft 365 and Windows Enterprise licensing. Physical Windows client devices work only as dedicated headless session hosts; laptops and personal PCs do not.

Density is why that matters. Microsoft markets Azure Virtual Desktop on its pricing page as the only cloud VDI solution fully optimized for Windows 11 and Windows 10 multi-session to help reduce costs. Its own examples put multi-session at two users per vCPU for Office workloads and six per vCPU for call center and data entry work. Single-session allocates a VM per user, sized in Microsoft’s example at two vCPUs and 4 GB each. A thousand knowledge workers therefore need several times the compute on Hybrid, absorbed by hardware the customer already owns or has to buy.

Preview feedback said the same thing repeatedly. On an Azure Academy video covering Hybrid, eight separate viewers asked for Windows 11 multi-session support. One noted the commercial consequence:

Good move. I could onboard more customers with this. Even more if you added win11 multi.

A third set of gaps sits in what the service does not do. Azure Virtual Desktop Hybrid does not provision or manage virtual machine state, which rules out power management, autoscale, Start VM on Connect, and Session Host Configuration. Organizations deploy and manage their own session hosts using hypervisor tools, scripts, or partner solutions. That absence explains the partner ecosystem around the release: Nerdio, Login VSI, and others are filling the operational layer Azure supplies natively for cloud-hosted session hosts.

Scott Manchester, chief product and technology officer at Nerdio, described Hybrid as a more flexible path towards Windows 365. He named the reasons organizations are not ready to move fully to the cloud: compliance requirements, cost constraints, and money already spent on infrastructure.

The regulated-workload case still holds. Session hosts and application data stay on-premises while the control plane runs in Azure, which satisfies data residency requirements without moving the workload.

The dependency that is created is documented. Session hosts need outbound access to login.microsoftonline.com for authentication and to *.wvd.microsoft.com for service traffic and RDP connectivity, and Microsoft states that blocking the required endpoints is unsupported. The desktops run locally. The service that authenticates and brokers connections to them does not.