VMware Horizon delivers virtual desktops across on premises and any cloud with mature management, though its commercial model has shifted sharply under Broadcom. Azure Virtual Desktop runs on consumption based Azure compute with exclusive Windows multi session rights and tight Microsoft 365 integration. The real choice is platform neutrality against Azure native economics.
Azure Virtual Desktop and VMware Horizon both deliver enterprise virtual desktops, and the decision has changed since Broadcom acquired VMware and restructured its licensing toward bundles and subscriptions. Horizon remains a mature, infrastructure neutral platform that runs anywhere, but its pricing and packaging now drive many buyers to reassess. AVD runs natively on Azure consumption, holds exclusive rights to Windows multi session, and bundles with Microsoft 365. The decision turns on infrastructure neutrality against Azure native cost and integration.
AVD itself has no per user platform fee when the user holds a qualifying Windows or Microsoft 365 license, so the cost is largely the underlying Azure compute and storage, billed on consumption. Windows multi session, exclusive to AVD, lets many users share a host and lowers that compute cost. VMware Horizon is now licensed through Broadcom bundles and subscriptions on top of the infrastructure it runs on. The honest comparison is consumption based Azure native delivery against a platform fee that buyers increasingly question post acquisition.
Horizon runs on premises, in private cloud, and across multiple public clouds, with mature image and session management and strong protocol performance. For organizations with significant on premises investment, multi cloud mandates, or workloads that cannot sit on Azure, that neutrality and depth remain real advantages. Where the estate is not Azure committed, Horizon flexibility can outweigh AVD native economics.
An evenhanded view. Both are leading VDI platforms. The differences that matter are the cost model, infrastructure neutrality, Windows multi session rights, and the post Broadcom commercial picture.
| Dimension | Azure Virtual Desktop | VMware Horizon |
|---|---|---|
| Platform fee | None with qualifying M365 or Windows | Broadcom bundle or subscription |
| Compute cost | Azure consumption, scalable | On infrastructure of choice |
| Windows multi session | Exclusive to AVD | Not available |
| Infrastructure | Azure native | On premises, private, multi cloud |
| Commercial stability | Stable Microsoft model | Reshaped under Broadcom |
| Microsoft integration | Native to Intune, Entra, M365 | Runs on Azure, less native |
| Best fit | Azure committed estates | On premises and multi cloud estates |
The Broadcom shift changed the question. For Azure committed estates, AVD now often wins on both cost and integration. For on premises and multi cloud estates, Horizon neutrality still earns its place despite the new commercial model.From the practice · virtual desktop engagements
Because AVD is Azure native and Horizon is infrastructure neutral but newly repriced, the framework is about Azure commitment, multi session fit, and the post Broadcom cost. Run these tests before you anchor.
If the estate already runs on Azure with a consumption commitment, AVD slots in natively, carries no platform fee with qualifying licenses, and draws down the Azure commit. If the estate is on premises or multi cloud, Horizon neutrality matters more and AVD native advantage shrinks. Match the platform to where the infrastructure actually lives.
Windows multi session, exclusive to AVD, lets many users share a host and is one of the biggest cost levers in cloud VDI. For pooled, non persistent knowledge workers it cuts compute sharply. Workloads requiring persistent one to one desktops benefit less. Assess how much of the population can run multi session before modeling AVD cost.
Horizon pricing and packaging changed materially under Broadcom, and many buyers face higher costs or unwanted bundles at renewal. Model the actual Horizon renewal under the new terms rather than the historical price, because the comparison against AVD has shifted. The new commercial reality is now part of the decision.
Across our practice the AVD versus Horizon decision now turns heavily on Azure commitment and the post Broadcom Horizon cost rather than a pure feature score. For Azure committed estates, AVD often wins on both economics and integration, with Horizon retained where on premises or multi cloud neutrality genuinely justifies its newly higher commercial model.
Our recommendation by profile is to default Azure committed organizations to AVD, since it carries no platform fee with qualifying Microsoft 365 or Windows licenses, runs on consumption based Azure compute that draws down an existing commitment, and uniquely offers Windows multi session to lower that compute cost. The Broadcom repricing of VMware has strengthened this case for many buyers by raising the Horizon line they are comparing against. Retain Horizon where the estate has significant on premises investment, a genuine multi cloud mandate, or workloads that cannot move to Azure, and where its infrastructure neutrality and mature management justify the new subscription model. A Microsoft committed enterprise should model AVD inside the broader Azure commitment, where the VDI compute counts toward the commit and improves the negotiation, while keeping a credible Horizon or Citrix alternative to preserve leverage. The buyers who get this wrong either stay on Horizon out of inertia and absorb the full post Broadcom increase, or move to AVD without modeling whether their population can use multi session, which is where most of the saving lives. The disciplined move is to model the real Horizon renewal, assess multi session fit honestly, and fold AVD into the wider Azure and Microsoft negotiation. See the Azure Virtual Desktop licensing overview, the Windows 365 Cloud PC licensing note, the Azure cost optimization practice, and the EA renewal practice.
One more factor shapes the call at renewal. Because AVD compute draws down an Azure consumption commitment, moving VDI to AVD both delivers desktops and helps the organization meet a MACC it has already signed, turning a cost into commitment progress. Windows 365 is the third option to weigh, offering a fixed price Cloud PC for users who want simplicity over consumption based flexibility. Decide the desktop delivery strategy across all three before sizing the Azure and Microsoft agreements. See the Windows 365 versus Citrix comparison for the fixed price alternative.
Three patterns we see when organizations compare AVD and Horizon.
The most common mistake post acquisition is renewing Horizon against its historical price rather than the new Broadcom terms. Buyers anchor on what they used to pay and miss the scale of the increase or the unwanted bundle. Model the actual renewal under current packaging before deciding whether Horizon still wins.
The opposite error is switching to AVD expecting savings, then deploying persistent one to one desktops that forfeit the multi session advantage where most of the cost benefit lives. AVD economics depend heavily on how much of the population can share hosts. Assess multi session fit before assuming a saving.
AVD compute runs on Azure, and negotiating it separately from the Azure commitment forfeits leverage and commitment drawdown. Folding AVD, Windows 365, and the VDI decision into the broader Azure and Microsoft negotiation gives the buyer more to trade and Microsoft more reason to concede, while the consumption counts toward the commit. A credible Horizon or Citrix alternative strengthens that negotiation. Buyers who treat VDI as a standalone procurement miss the leverage of negotiating the estate as a whole.
The AVD versus Horizon choice connects to the rest of the end user computing and cloud stack. The related notes below cover the adjacent decisions.
Two analyst calls. No pitch. We model the post Broadcom Horizon cost, assess multi session fit for AVD, weigh Windows 365 for simplicity, and fold the result into the wider Azure and Microsoft negotiation. Buyer side only. Never affiliated with Microsoft.