Question 1

Does Microsoft provide native autoscaling for AVD?

Accepted Answer

Yes. Microsoft's Autoscale feature in Azure Virtual Desktop provides basic demand-based scaling. Atlas AVD extends this with DrainGuard session protection, predictive warm-up, multi-pool coordination, historical analytics, and policy templates that are not available in the native implementation.

Question 2

What is the minimum number of hosts that should stay warm?

Accepted Answer

For a production environment, at least one host should remain warm at all times to handle the first user connections without waiting for VM provisioning. For larger environments, the minimum should be set to handle your expected off-peak baseline, typically 10-15% of your peak host count.

Question 3

How long does it take to start a new session host?

Accepted Answer

AVD session host startup time depends on the VM SKU and image complexity. D-series VMs typically start in 3-5 minutes. Images with large application stacks can extend this to 8-10 minutes. Atlas AVD's predictive warm-up ensures new hosts are ready before users experience queue wait times.

Question 4

Can scaling be suspended for maintenance windows?

Accepted Answer

Yes. Atlas AVD supports maintenance mode per host pool, which suspends scale-in policies to prevent hosts from being deallocated during planned maintenance, patching windows, or image testing periods.

Azure Virtual Desktop Autoscaling