Windows 365 and Azure Virtual Desktop both deliver a Windows desktop from Microsoft's cloud, but they license on opposite principles: Windows 365 is a fixed, predictable per-user subscription, while Azure Virtual Desktop is consumption-based infrastructure you size, run, and pay for by usage. That difference — predictability versus flexibility — drives almost everything about which one fits a given workforce. This comparison is part of our Microsoft licensing complete guide.
How Windows 365 licenses
Windows 365 delivers a Cloud PC — a dedicated, persistent Windows desktop — to each user on a fixed monthly per-user subscription. You select a Cloud PC configuration (a defined amount of vCPU, RAM, and storage) per user, and the price is a flat monthly amount regardless of how many hours that user actually works. The model is deliberately simple: one licence, one persistent desktop, one predictable cost per person.
Windows 365 also has eligibility prerequisites. Users generally need an appropriate Windows and Microsoft 365 entitlement for the Cloud PC to be licensed correctly, so the per-user subscription typically sits on top of an existing Microsoft 365 footprint rather than replacing it. Confirming the current prerequisite entitlements against Microsoft's published terms is an essential step before standardising on Windows 365.
How Azure Virtual Desktop licenses
Azure Virtual Desktop takes a different approach entirely. The desktop and app virtualisation service itself is accessed through existing eligible Windows and Microsoft 365 licences — there is no separate per-user AVD subscription in the Windows 365 sense — but you pay for the underlying Azure infrastructure that runs the desktops on a consumption basis. That means Azure compute, storage, and networking are billed by what you actually use, and you are responsible for sizing, scaling, and managing that infrastructure.
The consequence is flexibility with management overhead. AVD supports multi-session Windows, lets you scale capacity up and down with demand, and can be highly cost-efficient for workforces with predictable peaks and troughs — but it requires the skills to architect, autoscale, and optimise an Azure environment. The licensing is entitlement-plus-consumption rather than a flat per-user fee.
The core trade-off: Windows 365 trades cost flexibility for operational simplicity and budget predictability — you always know the per-user cost, but you pay it whether the user works one hour or forty. AVD trades simplicity for flexibility — it can be cheaper for variable or part-time usage and multi-session workloads, but only if you have the Azure skills to size and autoscale it well. The right choice follows your usage profile, not a universal verdict.
The two models side by side
| Dimension | Windows 365 | Azure Virtual Desktop |
|---|---|---|
| Pricing model | Fixed monthly per user | Azure consumption (usage-based) |
| Desktop type | Persistent, dedicated Cloud PC | Persistent or pooled, single- or multi-session |
| Cost predictability | High — flat per user | Variable — tracks usage |
| Management overhead | Low — Microsoft-managed simplicity | Higher — you size and manage Azure |
| Best for variable usage | Less efficient — you pay regardless | More efficient — pay for what you use |
| Entitlement prerequisites | Eligible Windows/M365 licences | Eligible Windows/M365 licences |
When Windows 365 fits
Windows 365 suits organisations that value predictability and simplicity over squeezing out every last unit of cost. It fits full-time knowledge workers who use their desktop consistently, scenarios where IT wants a fixed per-seat budget line, and teams without deep Azure infrastructure skills who want a managed, persistent Cloud PC without architecting an environment. It is also attractive for rapid onboarding — assigning a licence provisions a desktop without infrastructure design.
When Azure Virtual Desktop fits
Azure Virtual Desktop suits organisations with the Azure capability to manage it and usage patterns that reward consumption pricing. It fits variable or part-time workforces, seasonal peaks, multi-session workloads where many users share pooled capacity efficiently, and scenarios needing fine-grained control over the desktop environment and its scaling. For organisations already invested in Azure, AVD can be the more cost-efficient path — provided the environment is sized and autoscaled with discipline.
Most estates end up hybrid
In practice many organisations run both, matching the model to the worker. Full-time staff who need predictable, persistent desktops go on Windows 365; variable, seasonal, or multi-session populations go on AVD. The licensing strategy then becomes about segmenting the workforce correctly rather than choosing one model for everyone. The mistake to avoid is standardising on a single model for the whole estate without testing it against the different usage profiles within it.
The disciplined approach is to profile your user populations by usage pattern, model both options against each segment, and confirm the current entitlement prerequisites before committing. For help right-sizing the decision across your estate, our Microsoft licensing experts model both options against real usage, and the complete guide sets the wider context. Related SKU decisions are covered in Intune Plan 1 vs Plan 2 and Power BI Pro vs Premium.