Microsoft delivered one of the most consequential Azure Virtual Desktop updates of 2026 in June. Three features reached general availability — Automated Host Pools, Dynamic Autoscaling, and Ephemeral OS Disks — each addressing a different pain point in AVD operations. Together, they reshape how you provision, scale, and manage session hosts.

Here’s what shipped, what it means for your environment, and what you should do about it.

Automated Host Pools: Configuration-Driven Session Host Management

Automated Host Pools introduce a Session Host Configuration (SHC) — a single object that defines the standard for every session host in a pool. Instead of configuring each VM individually, you define the SHC once and Azure Virtual Desktop enforces it across the entire pool.

What the SHC controls:

  • OS image and version
  • VM size and storage settings
  • Extensions (AVD agent, diagnostics, monitoring)
  • Domain join type (Entra ID or AD DS)
  • Network settings (vNet, subnet, NSGs)
  • Managed identity and permissions

Why it matters: Configuration drift is one of the biggest operational headaches in VDI environments. When administrators update one host but not another, you get inconsistent user experiences, security gaps, and troubleshooting nightmares. SHC eliminates this by making the configuration the source of truth — update it once, and every new or reimaged host inherits the change automatically.

Prerequisites: Host pools must use managed identity (rolled out in 2025). SHC is also the foundation for Dynamic Autoscaling — you need it before you can scale dynamically.

Learn more: Session Host Configuration and Session host update.

Dynamic Autoscaling: Create and Delete VMs on Demand

Dynamic Autoscaling goes beyond the traditional start/stop scaling model. It creates and deletes session host VMs based on usage patterns and administrator-defined schedules — full lifecycle management, not just power state changes.

How it works:

  1. Your pooled host pool must use Session Host Configuration.
  2. You define autoscale schedules and rules: minimum/maximum host counts, session density thresholds, time-based patterns for shifts or business hours.
  3. The autoscaling engine creates new VMs (using your SHC definition) when demand increases and deletes VMs when demand drops.
  4. Azure Monitor and Log Analytics provide the metrics to tune your rules.

Cost impact: This is where the economics get interesting. Traditional AVD scaling stops VMs but keeps them allocated — you still pay for the compute reservation. Dynamic Autoscaling deletes idle VMs entirely, eliminating their compute charge. For environments with predictable off-hours (nights, weekends, holidays), the savings can be substantial.

Important limitation: Dynamic Autoscaling in this GA release supports only pooled host pools using SHC. Personal desktops and non-SHC host pools are not covered.

Learn more: Create and assign an autoscale scaling plan.

Ephemeral OS Disks: Stateless Hosts with Local Storage Performance

Ephemeral OS Disks moved from Public Preview (October 2025) to general availability. Session hosts can now use the VM’s local storage for the OS disk instead of a persistent managed disk — enabling truly stateless hosts.

Key benefits:

  • Faster provisioning and reimaging: OS reads/writes hit local SSD/NVMe instead of remote storage, reducing latency and speeding up host creation and reset operations.
  • Lower cost: No managed OS disk charge per session host. For large pools, this eliminates a meaningful line item.
  • Optimized for autoscaling: When Dynamic Autoscaling deletes a VM, there’s no orphaned managed disk to clean up. The OS disk ceases to exist with the VM.

The catch: Ephemeral OS means stateless by design. You must externalize everything:

  • User profiles via FSLogix on Azure Files or SMB shares
  • Applications via App Attach (now supported on Windows Server 2025/2022) or baked into the golden image
  • Any OS-level configuration changes must go through the SHC, not applied directly to running hosts

VM size constraint: Not all Azure VM sizes support ephemeral OS disks. You need SKUs with sufficient local storage capacity. Check the Azure compute documentation for the supported list.

Not for personal desktops: If your users need persistent OS-level customizations (installed apps, desktop settings that survive reboots), ephemeral OS is the wrong choice. Stick with managed disks for personal host pools.

How These Three Features Work Together

The real power of this June 2026 release is how the features complement each other:

  1. SHC defines what a session host looks like — image, size, identity, extensions.
  2. Dynamic Autoscaling uses SHC to create hosts on demand and delete them when idle.
  3. Ephemeral OS Disks make those create/delete cycles fast and cheap — no managed disk overhead, no cleanup needed.

This combination enables a fully stateless, elastic AVD architecture: hosts spin up in minutes during peak hours, disappear entirely during off-hours, and user personalization persists through FSLogix and App Attach independently of the OS disk.

What You Should Do Now

  1. Audit your host pools. If you’re still using the legacy service principal approach, migrate to managed identity — it’s now required for SHC.
  2. Define your Session Host Configuration. Start with one pooled host pool and codify its settings into an SHC. Test that new hosts created from the SHC match your expectations.
  3. Pilot Dynamic Autoscaling on a non-production pool. Define a schedule, set conservative thresholds, and measure the cost delta over a two-week period.
  4. Evaluate Ephemeral OS for stateless workloads. If you have pooled host pools where users don’t need OS-level persistence, test ephemeral OS with a subset of hosts. Verify your FSLogix and App Attach setup handles user state correctly.
  5. Skip ephemeral OS for personal desktops. The trade-offs don’t make sense when users need persistent OS customizations.

Bottom Line

June 2026 is a watershed moment for Azure Virtual Desktop operations. Automated Host Pools, Dynamic Autoscaling, and Ephemeral OS Disks collectively transform AVD from a manually-managed VDI platform into a configuration-driven, elastic, cost-optimized cloud desktop service. If you’re running AVD at any scale, these features warrant immediate evaluation.