Azure Virtual Desktop Licensing: Complete Enterprise Guide

Azure Virtual Desktop is simultaneously one of Microsoft's most complex licensing areas and one of the best cost optimisation opportunities available to M365 Enterprise subscribers. Organisations already paying for Microsoft 365 E3 or E5 are entitled to AVD infrastructure access at no additional per-user licence cost — yet the majority of enterprises we work with are either paying redundant third-party VDI broker licences that AVD makes unnecessary, or have modelled AVD costs incorrectly and significantly overpaid for compute. This guide covers AVD entitlements, VM sizing and density, cost optimisation strategies, and the EA negotiation angles that matter.

AVD Licensing Entitlements: What You Already Own

The foundational rule of AVD licensing is that access to the AVD service itself is included in qualifying Microsoft licences — you pay only for Azure infrastructure consumption (VMs, storage, networking). Understanding exactly which licences qualify determines your per-user economics.

The practical implication: if your organisation is on M365 E1 and considering AVD, you must either upgrade to E3 ($12/user/month incremental) or purchase Windows 10 Enterprise E3 as an add-on ($7/user/month). Either approach is substantially cheaper than purchasing a dedicated VDI licence from Citrix or VMware.

RDS Client Access Licences vs AVD

Traditional Windows Server RDS deployments require RDS CALs ($50-300/device or user depending on type). AVD with Windows 10/11 multi-session eliminates the need for RDS CALs entirely — multi-session uses Windows desktop OS licensing (covered by the per-user entitlement) rather than Windows Server OS licensing. This CAL elimination can save $50-150 per user on licensing alone for organisations migrating from legacy RDS infrastructure.

AVD VM Architecture and Cost Drivers

Infrastructure costs are the variable component of AVD economics. Three factors drive VM costs: SKU selection, session density (users per VM), and autoscale configuration.

VM SKU Selection for AVD Workloads

The density column above assumes business-hours peak load. In practice, healthcare and financial services organisations often model 8-12 hours of peak usage per day — meaning VMs are idle 50-65% of the time. Autoscale that shuts down excess session hosts during off-peak hours is the single highest-impact cost optimisation for most AVD environments.

Storage Cost: The Often-Overlooked Second Line Item

Each AVD session host requires an OS disk. Standard SSD E30 (1 TB) runs approximately $38/month per VM. Premium SSD P30 (1 TB) runs $135/month. For a 50-VM environment, OS disk storage ranges from $1,900/month (Standard) to $6,750/month (Premium). FSLogix profile storage (Azure Files Premium or Azure NetApp Files) adds $0.10-$0.60/GB/month depending on tier, with typical profile sizes of 5-20 GB per user.

Autoscale: The Primary Cost Optimisation Lever

Azure Virtual Desktop's built-in autoscale capability can reduce compute costs by 35-55% compared to always-on configurations. The mechanics: you define peak hours, minimum session hosts for off-peak, ramp-up/ramp-down schedules, and capacity thresholds. Session hosts that drop below minimum session thresholds are gracefully drained and deallocated — you pay for compute only when VMs are running.

A 100-user pooled environment modelled on 24/7 always-on VM availability might cost $8,500/month in compute (PAYG). The same environment with autoscale configured for business hours (8 AM–6 PM weekdays) and weekend shutdown reduces to approximately $3,800-$4,200/month — a 50-55% reduction. Over a 3-year EA commitment, that's $160,000-$170,000 in avoided Azure consumption.

Reservations + Autoscale: Combined Strategy

The optimal AVD cost architecture combines reserved instances for baseline capacity with PAYG for autoscale overflow. For a 100-user environment with 15 baseline VMs and 5 overflow VMs: reserve 12-13 VMs at 3-year pricing (covering the baseline minimum session host count), and keep 2-3 VMs on PAYG for peak handling. This captures 55% savings on 85% of your compute while retaining flexibility on the variable portion.

AVD vs Windows 365: The Correct Decision Framework

See the dedicated Windows 365 vs AVD decision guide for full analysis. The summary: AVD is optimal for variable-usage workloads where autoscale can reduce costs. Windows 365 is optimal for consistent full-day users who need a simple, predictable per-user cost with no infrastructure management overhead. The crossover point is approximately 6-7 hours/day of active use — above this, Windows 365 typically wins on cost; below it, AVD with autoscale is cheaper.

Hybrid Benefit Application to AVD

Azure Hybrid Benefit for Windows Server applies to AVD session hosts running Windows Server OS (traditional RDS scenarios using Server 2019/2022). Each Windows Server Datacenter or Standard licence with SA covers 2 VMs (Datacenter) or 1 VM (Standard). For Windows 10/11 multi-session scenarios — which we recommend for most enterprise deployments — Hybrid Benefit does not apply because the OS entitlement comes from the per-user licence, not from a server licence.

The practical guidance: use Windows 10/11 Enterprise multi-session wherever possible. This eliminates Windows Server CAL requirements, provides a better user experience (desktop OS), and is optimised for Microsoft 365 application compatibility. Reserve Windows Server RDS for specific legacy application compatibility scenarios that genuinely require a server OS environment.

EA Negotiation for AVD

AVD itself carries no separate licence cost for qualified M365 subscribers, so the negotiation focus for AVD is on the Azure consumption side — specifically how AVD infrastructure costs interact with MACC commitments and reserved instance pricing.

MACC acceleration: AVD infrastructure costs (VMs, storage, networking) count toward MACC draw-down. Organisations with significant MACC commitments should route AVD consumption through EA rather than CSP to ensure MACC credit. This is particularly important for organisations in MACC shortfall risk.

Consolidated reservation commitment: When negotiating AVD reserved instances alongside other Azure workload reservations, bundle the commitment into a single reservation purchase conversation. Reservation flexibility (ability to exchange or return) is more negotiable when commitments are larger — aim for instance size flexibility at minimum, or return rights (capped at 1 reservation return per 12 months, up to $50K — negotiate higher limits for large deployments).

Windows 365 cross-comparison leverage: When negotiating Windows 365 pricing, use AVD as competitive backstop. Microsoft knows AVD is a credible alternative for many Windows 365 use cases and will negotiate Windows 365 pricing more aggressively when buyers demonstrate AVD is genuinely in scope. We have achieved 15-20% discounts on Windows 365 user counts using this approach.

AVD Cost Modelling: Complete Example

A representative 500-user pooled AVD environment (light-to-medium workloads, business hours) modelled over 3 years:

Adding the M365 E3 licence cost ($36/user/month) brings total all-in AVD cost to approximately $57/user/month — significantly below equivalent Citrix or VMware Horizon deployments that typically run $80-120/user/month when broker, infrastructure, and user licensing are combined.

Common AVD Licensing Mistakes

1. Not using Windows multi-session when eligible. Organisations deploying Windows Server RDS on AVD when they have qualifying M365 licences are paying for Server CALs unnecessarily and missing the better user experience of Windows 11 Enterprise.

2. Always-on VMs without autoscale. As modelled above, not implementing autoscale for business-hours environments wastes 50%+ of compute spend. This is the most common and expensive AVD configuration mistake we encounter.

3. Oversizing VMs during initial deployment. Initial AVD deployments frequently use oversized VMs "to be safe." After 60-90 days of usage data, right-sizing typically yields 20-30% compute reduction with no user experience impact.

4. Premium SSD for all session hosts. Premium SSD is required for session hosts where boot time matters or where storage I/O is a bottleneck. For light workload pools where users don't regularly log in/out within peak hours, Standard SSD at 72% lower cost is entirely adequate.

Frequently Asked Questions