Azure Virtual Desktop (AVD) bills you twice: once for the Azure infrastructure (VMs, storage, networking, FSLogix profile containers, gateway), and once for the user access rights that entitle each user to connect to a Windows multi-session desktop. The azure virtual desktop licensing question that determines whether AVD makes financial sense is whether your users already hold an entitling licence — Microsoft 365 E3/E5/E7, Microsoft 365 Business Premium, Windows Enterprise E3/E5 with active SA, or Windows 11 Enterprise via VDA per-user. If they do, AVD user access is included at no incremental per-user charge and the cost is the Azure infrastructure only. If they do not, AVD is structurally more expensive than alternatives like Windows 365 Cloud PC. The licensing layer is the dominant variable.
The two bills AVD generates
Azure Virtual Desktop pricing has two independent components that most procurement teams conflate at their cost.
Bill 1: Azure infrastructure. Session host VMs (typically D-series or F-series for general user populations, NV-series for graphics workloads), FSLogix profile storage on Azure Files Premium, Azure NetApp Files for high-IO scenarios, networking, monitoring, gateway, and storage for image management. Sized correctly with session pooling and autoscaling, this bill runs $24–$56 per active concurrent user per month depending on density and workload class.
Bill 2: User access rights. Every named user connecting to an AVD session host needs an entitling licence. Microsoft includes AVD user access rights with: Microsoft 365 E3, E5, E7, Microsoft 365 Business Premium, Microsoft 365 A3/A5 (education), Windows Enterprise E3/E5 with active Software Assurance, Windows 11 Enterprise VDA per user, and the Microsoft 365 F3 Frontline SKU. If your users hold any of these, the AVD user access right is bundled — no additional purchase. If your users do not, the standalone external user pricing applies on a per-user / per-hour basis, which is materially more expensive.
Where AVD wins on cost
AVD's structural advantage is multi-session Windows 11. A single VM hosts 8–25 concurrent users depending on workload class, sharing CPU, memory, and storage. Compared with single-session VDI (one VM per user) or one Cloud PC per user, session density compresses infrastructure cost dramatically. The break-even crosses Cloud PC at roughly 4–6 concurrent users per session host, which is the floor for most production AVD pools.
Three workload patterns where AVD is the clear winner:
- Knowledge workers with bursty usage. Pooled host pools with autoscaling collapse idle infrastructure between peak hours.
- Contractor and external-party access. The ability to spin a pool of session hosts and entitle access via per-user external pricing keeps contractor footprints flexible.
- BYOD with strict data-out controls. AVD keeps data in Azure and pushes only pixels to the endpoint, which works well in regulated environments where Cloud PC's per-user device model is overkill.
Microsoft sales pushes Windows 365 Cloud PC over AVD in 2026 because Cloud PC is a per-user-per-month subscription that drives more predictable revenue. AVD bills as infrastructure consumption, which is more efficient for the buyer but less attractive on Microsoft's quarterly numbers. For workloads with high session density, AVD is materially cheaper. Run the math for both before accepting the Cloud PC default.
The entitling-license map
| User's licence | AVD access included? | Notes |
|---|---|---|
| Microsoft 365 E3/E5/E7 | Yes | Most common entry point |
| Microsoft 365 Business Premium | Yes | Caps at 300 users |
| Microsoft 365 F3 | Yes (Frontline) | Multi-session Windows 11 only |
| Windows Enterprise E3/E5 + SA | Yes | Must have active SA |
| Windows 11 Enterprise VDA (per user) | Yes | Standalone option |
| External Identity / external user | Per-user hourly | Materially more expensive at scale |
| Microsoft 365 E1, F1 | No | Must add VDA or upgrade |
| Microsoft 365 Apps for Enterprise only | No | Add VDA |
Infrastructure sizing decisions that drive cost
Four infrastructure choices dominate the AVD bill. Get these right and the per-user cost lands at the low end; get them wrong and AVD becomes more expensive than Cloud PC.
- Session density. The number of concurrent users per session host. Higher density = lower per-user cost. Light office users land at 16–25 per D8s v5; power users at 6–10. Profile this empirically rather than relying on Microsoft's defaults.
- Autoscaling. Scale-down rules that idle session hosts during off-hours capture 30–55% reduction in compute cost. Without autoscaling, AVD runs hot 24/7 and the economics deteriorate fast.
- Profile storage tier. FSLogix profiles can sit on Azure Files Premium, Azure NetApp Files, or Azure Files Standard. Premium is the default and the right choice for most enterprises; NetApp Files for >500 user populations or graphics workloads. Standard is too slow for production.
- Reservations and Azure Hybrid Benefit. AVD session hosts are eligible for VM reservations and Azure Hybrid Benefit. Three-year RIs on the steady-state session host fleet plus AHB on Windows licensing captures another 25–40% reduction on the compute line.
AVD vs Windows 365 Cloud PC
Windows 365 Cloud PC is the other half of Microsoft's end-user computing pitch. Cloud PC is per-user, fixed-spec, always-on, billed monthly. AVD is per-session, variable-spec, autoscaled, billed by infrastructure consumption. The trade-off is concurrency: if your concurrency ratio is below ~0.6 (i.e., the typical user uses their desktop less than 60% of the day), AVD wins because session pooling captures the idle hours. If concurrency is above ~0.8, Cloud PC's per-user simplicity wins because the session-pooling overhead does not pay back.
For most enterprise knowledge-worker populations, concurrency is 0.4–0.55, which puts AVD comfortably ahead on cost. For dedicated power users (developers, designers, analysts) with always-on workflows, Cloud PC is often the cleaner choice. A mixed posture is common — AVD pools for the bulk of the workforce, Cloud PC for the dedicated power users.
Anonymised case study: 12,500-seat financial services AVD
A 12,500-seat financial services firm migrated off Citrix-on-Azure to AVD in 2024. Initial AVD deployment used Microsoft's reference architecture with no autoscaling, single density assumption, and no reservations. Run rate: $79 per user per month. We re-engineered the deployment: profiled actual session density (landed at 18 users per D16s v5 for the trader pool, 12 for the analyst pool), implemented autoscaling with scale-down to 25% off-peak, applied three-year RIs and AHB on the steady-state fleet, moved profile storage from Standard to Premium with the correct sizing. New run rate: $34 per user per month. Annual savings: $6.75M with no functional change to the user experience. The savings paid back the re-engineering work in 5 weeks.
Where to take this from here
If you run AVD without autoscaling, reservation coverage, or empirical session density profiling, you are paying 40–60% more than you need to. The remediation is sequenced: density first, autoscaling second, then RIs and AHB. For broader Azure cost context, the complete Azure cost optimisation guide places AVD alongside compute and storage decisions. For the licensing entitlement side, the M365 add-on licensing guide covers VDA and the SKUs that entitle AVD access. For renewal leverage, the EA tier collapse playbook covers how end-user computing licences become a negotiation lever at EA renewal.