Question 1

How much can a typical AVD environment realistically save?

Accepted Answer

Production environments with standard business hours and no prior optimization typically achieve 40-60% compute cost reduction after implementing demand-based scaling and scheduled power management. Storage and right-sizing optimizations add another 10-20% on top.

Question 2

Does auto-scaling disconnect active user sessions?

Accepted Answer

No. Scale-in policies only trigger on session hosts with zero active sessions. Atlas AVD's DrainGuard component monitors session counts and blocks deallocation of any host with connected users, regardless of the scaling policy timer.

Question 3

What VM sizes work best for knowledge worker AVD workloads?

Accepted Answer

D4as_v5 (4 vCPU, 16 GB) handles 4-6 concurrent knowledge worker sessions comfortably in multi-session host pools. D2as_v5 is appropriate for lighter task-worker profiles. D8as_v5 should be reserved for power users or workloads with higher CPU or memory demands.

Question 4

How quickly does Atlas AVD deliver cost savings?

Accepted Answer

Scaling automation starts reducing compute costs from the first day it's enabled. The largest impact, typically the first weekly billing cycle, comes from eliminating overnight and weekend idle compute.

Question 5

Can Atlas AVD optimize costs across multiple Azure subscriptions?

Accepted Answer

Yes. Atlas AVD's multi-subscription management supports cost tracking, scaling policies, and recommendations across all AVD environments in a tenant, with per-subscription or aggregate reporting.

Azure Virtual Desktop Cost Optimization