Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Virtual Desktop (AVD) supports multiple session host operating systems and servicing approaches. The right update strategy depends on several factors:
- The session host operating system: Windows client Enterprise, Windows client multi-session, or Windows Server.
- The type of update: monthly security and quality updates, feature updates, or OS version upgrades.
- The servicing model: patch in-place or image-based servicing.
This article gives an overview of the supported update methods for AVD session hosts. The following table explains what each recommendation marker means.
| Marker | Meaning |
|---|---|
| Recommended | Supported and the preferred method for this operating system. |
| Supported | Works and is an acceptable choice. It's not the single preferred method for this operating system. |
| Not recommended | Works, but discouraged for this operating system. A better option is available. |
| Not supported | Shouldn't be used for, or doesn't apply to, this operating system. |
Supported session host operating systems
The first step in choosing a servicing approach is to identify the session host operating system and host pool type.
| Host pool type | Windows client Enterprise1 | Windows client multi-session | Windows Server |
|---|---|---|---|
| Personal | Supported | Not supported | Supported |
| Pooled | Not recommended2 | Supported | Supported |
1. Also known as Windows client single-session.
2. Session density set to 1 (session limit).
Monthly security and quality updates
Monthly updates include security updates, quality updates, and the latest cumulative updates (LCUs). The recommended delivery method depends on the session host operating system.
| Delivery method | Windows client Enterprise | Windows client multi-session | Windows Server |
|---|---|---|---|
| Windows Update | Recommended | Not recommended | Supported |
| Windows Autopatch (WUfB) | Recommended | Not recommended | Not supported |
| Configuration Manager | Supported | Supported | Supported |
| Azure Update Manager | Not supported | Not supported | Recommended |
| Automatic guest patching | Not supported | Not supported | Recommended |
| Session host update | Not supported | Recommended | Not recommended |
| Azure Compute Gallery | Not recommended | Recommended | Not recommended |
Hotpatch considerations for monthly updates
Hotpatching applies eligible monthly security updates without requiring a reboot. It's supported on Windows Server Azure Edition and on Windows 11 Enterprise, version 24H2 or later, when virtualization-based security (VBS) is enabled and updates are managed through Windows Autopatch and Microsoft Intune.
| Operating system | Hotpatch support |
|---|---|
| Windows client Enterprise | Supported on Windows 11 Enterprise, version 24H2 or later, with VBS enabled. |
| Windows client multi-session | Supported. |
| Windows Server | Supported on Azure Edition only. |
Feature updates
Feature updates, including enablement package (eKB) updates, introduce new Windows features. For example, moving from Windows 11, version 24H2 to Windows 11, version 25H2. Feature updates don't apply to Windows Server.
| Delivery method | Windows client Enterprise | Windows client multi-session | Windows Server |
|---|---|---|---|
| Windows Update | Recommended | Not recommended | Not supported |
| Windows Autopatch (WUfB) | Recommended | Not recommended | Not supported |
| Configuration Manager | Supported | Supported | Supported |
| Windows Server Update Services (WSUS) | Not supported | Not recommended | Not recommended |
| Session host update | Not supported | Recommended | Not recommended |
| Azure Compute Gallery | Not recommended | Recommended | Not supported |
| In-place (Setup.exe or ISO) | Not recommended | Not recommended | Not supported |
OS version upgrades
An OS version upgrade moves a session host to a new operating system version. For example, Windows Server 2022 to Windows Server 2025, or Windows 10 to Windows 11.
The recommended method is to deploy new virtual machines (VMs) that use an image for the target OS version. For more information about in-place upgrades, see Perform an in-place upgrade of a Windows VM in Azure.
| Delivery method | Windows client Enterprise | Windows client multi-session | Windows Server |
|---|---|---|---|
| In-place (Setup.exe or ISO) | Not supported | Not supported | Not supported |
| New VM deployment from a new image (Azure Compute Gallery) | Recommended | Recommended, using session host update | Recommended |
Choose the right servicing model
Each delivery method maps to one of two servicing models: patch in-place or image-based servicing.
| Delivery method | Servicing model |
|---|---|
| Windows Update or Windows Autopatch (WUfB) | Patch in-place |
| Microsoft Intune | Patch in-place |
| Microsoft Configuration Manager | Patch in-place |
| Azure Update Manager | Patch in-place |
| Automatic guest patching | Patch in-place |
| WSUS | Patch in-place |
| Setup.exe or ISO | Patch in-place |
| Session host update | Image-based servicing |
| Azure Compute Gallery or new VM deployment from a new image | Image-based servicing |
Patch in-place
Patch in-place updates the existing session host VM without replacing it. It's typically used for monthly cumulative updates, security updates, and Windows Server patching. Common, recommended technologies include Windows Update, Windows Autopatch (WUfB), Microsoft Intune, Azure Update Manager, automatic guest patching, WSUS, and Microsoft Configuration Manager.
Image-based servicing
Image-based servicing creates a new image version and deploys updated session hosts. The typical workflow is to update the base image, validate applications and configurations, publish a new Azure Compute Gallery image version, deploy new session hosts, then drain and remove the old session hosts. When a session host is updated through image-based servicing, user data and local storage isn't saved.
Image-based servicing through session host update is recommended for pooled AVD environments because it provides consistent host configuration, easier rollback, and reduced impact to active user sessions.