Microsoft cloud
Host pool
Azure Virtual Desktop host pool
A host pool is the core administrative unit in Azure Virtual Desktop: a collection of virtual machine session hosts, grouped together and managed as a set, that delivers either full desktops or individually published RemoteApps to the users assigned to it.
Why Host pool matters in a Microsoft estate
Host pool 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 Host pool shows up in practice
Every host pool is configured as one of two fundamentally different types, and that choice shapes almost everything else about how the pool behaves and costs. A pooled host pool allows multiple users to share the same session hosts concurrently through Windows multi-session. This is the configuration that gives Azure Virtual Desktop its high-density cost advantage, since infrastructure is shared rather than dedicated per user. It also means user profiles must be made portable across hosts, typically with FSLogix, since a user may land on a different host each session.
A personal host pool assigns each session host to exactly one user, functioning much like a traditional dedicated virtual desktop and removing the shared-host profile problem, at the cost of the density economics a pooled configuration provides. Within a pooled host pool, the load-balancing algorithm directly affects both user experience and cost: either breadth-first, which spreads new sessions evenly across all available hosts to keep each one lightly loaded, or depth-first, which fills one host before moving to the next. Depth-first allows fuller hosts to be scaled down or deallocated during quiet periods more aggressively than breadth-first typically permits.
Host pool sizing is where much of AVD's real, easy-to-miss cost lives: capacity kept running as headroom to absorb peak demand without degrading the user experience is genuine compute spend even while sessions sit idle between peaks. This is why scaling automation, called autoscale, that expands and contracts running host count against actual session demand is one of the highest-value optimisations available on a pooled AVD estate, rather than a nice-to-have left for later. Getting host pool design right, matching pooled versus personal to the right user cohort and tuning autoscale against genuine usage patterns, is usually a bigger lever on total AVD cost than any single VM SKU or reservation decision made afterward.