Microsoft cloud
AVD
Azure Virtual Desktop
Azure Virtual Desktop is Microsoft's desktop and application virtualisation service running on Azure, delivering full Windows desktops or individual published applications to users from cloud-hosted session hosts organised into host pools.
Why AVD matters in a Microsoft estate
AVD matters because Microsoft 365, Azure, Windows 365, Teams, and related services are usually managed as one estate. The term connects to planning, cost, configuration, security, and day-two operational decisions across that estate.
How AVD shows up in practice
Its defining characteristic, and the reason it remains the right choice for many estates even as Windows 365 has grown, is architectural flexibility. AVD supports both pooled deployments, where many users share a smaller number of multi-session hosts, and personal, one-to-one assignments. It gives direct control over VM sizing, image management, scaling schedules, and network configuration, and it bills on consumption, meaning cost tracks actual compute and storage usage rather than a flat per-user rate. That flexibility is also where AVD costs most often exceed expectations.
Host pool headroom kept running to absorb peak demand, golden image and FSLogix profile management overhead, and the monitoring, patching, and scaling automation effort all represent real, ongoing cost that does not appear as a single obvious line item the way a per-user licence does. AVD suits workloads that need genuine session-host control or high-density economics. This includes graphics-intensive and GPU-backed users, bursty or scheduled demand where consumption billing can track usage more tightly than a flat rate, and pooled multi-session estates where shared infrastructure economics beat a per-seat model. Since 2022, Windows 365 has offered a parallel, simpler operating model for cohorts that need a persistent, personal Cloud PC without the infrastructure decisions AVD requires.
Microsoft's own Windows 365 migration API now allows Entra-joined or hybrid-joined AVD virtual machines to move into Windows 365 through snapshot-based provisioning, though that path currently targets persistent, single-session machines rather than pooled multi-session host pools, which need a fresh build instead. The practical planning question for most estates is not AVD or Windows 365 as an absolute choice, but which model fits each user cohort. A mixed estate running both, matched to genuine usage patterns, is common and often the most cost-effective outcome.