You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> - Azure Virtual Desktop on Azure Extended Zones.
19
19
>
20
-
> - Managing session hosts using a session host configuration. This limited preview is provided as-is, with all faults and as available, and are excluded from the service-level agreements (SLAs) or any limited warranties Microsoft provides for Azure services in general availability.
20
+
> - Managing session hosts using a session host configuration. This limited preview is provided as-is, with all faults and as available, and is excluded from the service-level agreements (SLAs) or any limited warranties Microsoft provides for Azure services in general availability.
21
21
>
22
22
> For legal terms that apply to Azure features that are in beta, in preview, or otherwise not yet released into general availability, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
23
23
@@ -181,7 +181,9 @@ Here's how to generate a registration key by using the [desktopvirtualization](/
181
181
You can use the Azure portal to specify the number of session hosts you want to add, then Azure Virtual Desktop automatically creates them based on the session host configuration. At this time, you can't use PowerShell to add session hosts to a host pool with a session host configuration.
182
182
183
183
> [!NOTE]
184
-
>[Diagnostics for host pools using a session host configuration](https://learn.microsoft.com/en-us/azure/virtual-desktop/session-host-update-diagnostics) are recorded with Log Analytics in Azure Monitor and won't be available in your ARM deployments history. We recommended that you [enable Log Analytics](https://learn.microsoft.com/en-us/azure/virtual-desktop/diagnostics-log-analytics) for any host pool using a session host configuration.
184
+
> [Diagnostics for host pools using a session host configuration](session-host-update-diagnostics.md) are recorded with Log Analytics in Azure Monitor and won't be available in your Azure Resource Manager deployments history. We recommended that you [enable Log Analytics](diagnostics-log-analytics.md) for any host pool using a session host configuration.
185
+
>
186
+
> You can choose to use the legacy method of using an ARM template to create session hosts through the Azure portal until September 1, 2025. To access that experience, use this link to access the [Azure portal](https://portal.azure.com/?feature.enableSessionHostProvisioning=false).
185
187
186
188
Here's how to add session hosts:
187
189
@@ -203,7 +205,7 @@ Here's how to add session hosts:
203
205
204
206
### Cancel in-progress session host creation
205
207
206
-
You can cancel in-progress session host creation using the Azure portal. Session hosts that are in the process of being created can't be cancelled.
208
+
You can cancel in-progress session host creation using the Azure portal. Session hosts that are in the process of being created can't be canceled.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/azure-ad-joined-session-hosts.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Microsoft Entra joined session hosts in Azure Virtual Desktop
3
3
description: Learn about using Microsoft Entra joined session hosts in Azure Virtual Desktop.
4
4
author: dougeby
5
5
ms.topic: how-to
6
-
ms.date: 04/17/2025
6
+
ms.date: 06/11/2025
7
7
ms.author: avdcontent
8
8
ms.custom: docs_inherited
9
9
---
@@ -34,7 +34,7 @@ You can deploy Microsoft Entra joined VMs directly from the Azure portal when yo
34
34
35
35
After you've created your host pool, you must assign users access to their resources. To grant access to resources, add each user to the application group. Follow the instructions in [Manage application groups](manage-app-groups.md) to assign user access to apps and desktops. We recommend that you use user groups instead of individual users wherever possible.
36
36
37
-
For Microsoft Entra joined VMs in host pools without a session host configuration, you need to do two extra things on top of the requirements for Active Directory or Microsoft Entra Domain Services-based deployments. For host pools using a session host configuration, this additional role assignment is not required.
37
+
For Microsoft Entra joined VMs in host pools without a session host configuration, you need to do the following extra tasks on top of the requirements for Active Directory or Microsoft Entra Domain Services-based deployments. For host pools using a session host configuration, this additional role assignment isn't required.
38
38
39
39
- Assign your users the **Virtual Machine User Login** role so they can sign in to the VMs.
40
40
- Assign administrators who need local administrative privileges the **Virtual Machine Administrator Login** role.
@@ -63,9 +63,9 @@ In addition to the general prerequisites, you need:
63
63
64
64
- If you're joining session hosts to an Active Directory domain or using [Microsoft Entra hybrid join](/entra/identity/devices/concept-hybrid-join) you need additional permissions:
65
65
66
-
-If you're joining session hosts to a Microsoft Entra Domain Services domain, you need to be a member of the [*AAD DC Administrators* group](../active-directory-domain-services/tutorial-create-instance-advanced.md#configure-an-administrative-group).
66
+
-For Microsoft Entra Domain Services domain, you need to be a member of the [*AAD DC Administrators* group](../active-directory-domain-services/tutorial-create-instance-advanced.md#configure-an-administrative-group).
67
67
68
-
-If you're joining session hosts to an Active Directory Domain Services (AD DS) domain, you need to use an account with more permissions than typically required for joining a domain because the new OS image reuses the existing computer object. The permissions and properties in the following table need to be applied to the account on the Organizational Unit (OU) containing your session hosts:
68
+
-For an Active Directory Domain Services (AD DS) domain, you need to use an account with more permissions than typically required for joining a domain because the new OS image reuses the existing computer object. The permissions and properties in the following table need to be applied to the account on the Organizational Unit (OU) containing your session hosts:
69
69
70
70
| Name | Type | Applies to |
71
71
|--|--|--|
@@ -97,10 +97,9 @@ In addition to the general prerequisites, you need:
97
97
98
98
- Don't disable [Windows Remote Management](/windows/win32/winrm/about-windows-remote-management) (WinRM) when creating session hosts using the Azure portal, as [PowerShell DSC](/powershell/dsc/overview) requires it.
99
99
100
-
### PowerShell prerequisites
101
100
- If you want to use Azure PowerShell locally, see [Use Azure CLI and Azure PowerShell with Azure Virtual Desktop](cli-powershell.md) to make sure you have the [Az.DesktopVirtualization](/powershell/module/az.desktopvirtualization) PowerShell module installed. Alternatively, use the [Azure Cloud Shell](../cloud-shell/overview.md).
102
101
103
-
- Azure PowerShell cmdlets for Azure Virtual Desktop that support host pools with a session host configuration are in preview. You need to download and install the [preview version of the Az.DesktopVirtualization module](https://www.powershellgallery.com/packages/Az.DesktopVirtualization/) to use these cmdlets, which are added in version 5.3.0.
102
+
- Azure PowerShell cmdlets for Azure Virtual Desktop that support host pools with a session host configuration are in preview. You need to download and install the [preview version of the Az.DesktopVirtualization module](https://www.powershellgallery.com/packages/Az.DesktopVirtualization/) to use these cmdlets, which were added in version 5.3.0.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/host-pool-management-approaches.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,21 +64,20 @@ For a comparison of host pool with a session host configuration and a host pool
64
64
65
65
### Session host management policy
66
66
67
-
A session host management policy is a sub-resource of a host pool that specifies how session hosts in the host pool should be updated and created. The session host management policy persists throughout the lifetime of the host pool and is used when updating the session hosts in the host pool or adding new session hosts. Each host pool with a session host configuration only has a single session host management policy, and you can't delete a session host management policy independently of the host pool.
67
+
A session host management policy is a sub-resource of a host pool that specifies how session hosts in the host pool should be updated and created. The session host management policy persists throughout the lifetime of the host pool and it's used when updating the session hosts in the host pool or adding new session hosts. Each host pool with a session host configuration only has a single session host management policy, and you can't delete a session host management policy independently of the host pool.
68
68
69
69
When you use the Azure portal, a default session host management policy is created when you create a host pool with a session host configuration. You can override its values when updating and creating session hosts, or you can also update the session host management policy at any time using PowerShell.
70
70
71
71
The session host management policy includes the following parameters:
72
72
73
73
| Parameter | Description | Azure portal default value |
74
74
|--|--|--|
75
-
|**Time zone**| The time zone to use when scheduling an update of the session hosts in a host pool. | UTC |
76
-
|**Max VMs removed during update**| The maximum number of session hosts to update concurrently, also known as the *batch size*. |1|
77
-
|**Logoff delay in minutes**| The amount of time to wait after an update start time for users to be notified to sign out, between 0 and 60 minutes. Users will automatically be signed out after this time elapses. |2|
75
+
|**Time zone**| The time zone to use when scheduling an update of the session hosts in a host pool. |`UTC`|
76
+
|**Max VMs removed during update**| The maximum number of session hosts to update concurrently, also known as the *batch size*. |`1`|
77
+
|**Logoff delay in minutes**| The amount of time to wait after an update start time for users to be notified to sign out, between 0 and 60 minutes. Users will automatically be signed out after this time elapses. |`2`|
78
78
|**Logoff message**| A message to display to users that the session host they're connected to will be updated. |`You will be signed out`|
79
-
|**Leave in drain mode**| Determines whether newly created session hosts will be left in drain mode for post-creation actions before users can log in. This parameter does not apply for session host update.| False |
80
-
|**Failed session host cleanup policy**| Determines whether to keep none, some, or all session hosts that encounter an error during session host creation. This parameter does not apply for session host update.| KeepAll|
81
-
79
+
|**Leave in drain mode**| Determines whether newly created session hosts will be left in drain mode for post-creation actions before users can log in. This parameter doesn't apply for session host update. |`False`|
80
+
|**Failed session host cleanup policy**| Determines whether to keep none, some, or all session hosts that encounter an error during session host creation. This parameter doesn't apply for session host update. |`KeepAll`|
Copy file name to clipboardExpand all lines: articles/virtual-desktop/session-host-update-configure.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,9 @@ To learn more about how session host update works, see [Session host update](ses
24
24
25
25
Before you update session hosts using session host update, you need:
26
26
27
-
- An [existing pooled host pool with a session host configuration](https://learn.microsoft.com/azure/virtual-desktop/deploy-azure-virtual-desktop?tabs=portal-session-host-configuration%2Cportal-standard%2Cportal&pivots=host-pool-session-host-configuration#prerequisites) with session hosts that are all in the same Azure region and resource group.
27
+
- An [existing pooled host pool with a session host configuration](deploy-azure-virtual-desktop.md?pivots=host-pool-session-host-configuration) with session hosts that are all in the same Azure region and resource group.
28
28
29
-
- RBAC permissions required to [update a session host configuration](https://learn.microsoft.com/azure/virtual-desktop/deploy-azure-virtual-desktop?tabs=portal-session-host-configuration%2Cportal-standard%2Cportal&pivots=host-pool-session-host-configuration#prerequisites)
29
+
- RBAC permissions required to [update a session host configuration](deploy-azure-virtual-desktop.md?pivots=host-pool-session-host-configuration#prerequisites).
30
30
31
31
- The new image must be [supported for Azure Virtual Desktop](prerequisites.md#operating-systems-and-licenses) and match the [generation of virtual machine](/azure/virtual-machines/generation-2). If you're using [Trusted launch virtual machines](security-guide.md#trusted-launch) or [Confidential virtual machines](security-guide.md#azure-confidential-computing-virtual-machines), your image must be for generation 2 VMs. It can be from:
32
32
@@ -36,7 +36,9 @@ Before you update session hosts using session host update, you need:
36
36
37
37
- Remove any resource locks on session hosts or the resource group they're in.
38
38
39
-
- If you are planning to use PowerShell, you need to download and install the preview version of the Az.DesktopVirtualization module to use these cmdlets, which are added in version 5.3.0.
39
+
- If you want to use Azure PowerShell locally, see [Use Azure CLI and Azure PowerShell with Azure Virtual Desktop](cli-powershell.md) to make sure you have the [Az.DesktopVirtualization](/powershell/module/az.desktopvirtualization) PowerShell module installed. Alternatively, use the [Azure Cloud Shell](../cloud-shell/overview.md).
40
+
41
+
- Azure PowerShell cmdlets for Azure Virtual Desktop that support host pools with a session host configuration are in preview. You need to download and install the [preview version of the Az.DesktopVirtualization module](https://www.powershellgallery.com/packages/Az.DesktopVirtualization/) to use these cmdlets, which were added in version 5.3.0.
40
42
41
43
## Schedule an update and edit a session host configuration
Copy file name to clipboardExpand all lines: articles/virtual-desktop/whats-new.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.topic: release-notes
5
5
ms.custom: references_regions
6
6
author: dougeby
7
7
ms.author: avdcontent
8
-
ms.date: 06/06/2025
8
+
ms.date: 06/16/2025
9
9
---
10
10
11
11
# What's new in Azure Virtual Desktop?
@@ -32,6 +32,18 @@ Azure Virtual Desktop graphics processing unit (GPU) acceleration support for fr
32
32
33
33
For more information, see [Enable GPU acceleration for Azure Virtual Desktop](graphics-enable-gpu-acceleration.md).
34
34
35
+
### Session host creation using a session host configuration
36
+
37
+
We extended the session host creation functionality from session host update and dynamic autoscaling to apply to all session hosts created in a host pool with a session host configuration. We also added support for Microsoft Entra-joined devices. This update brings the following changes:
38
+
39
+
- You can configure a host pool to use Microsoft Entra-join without needing to assign the **Virtual Machine User** RBAC role to a user.
40
+
- Error reporting is consistent across services and auto-retry functionality is added to session host creation to mitigate transient errors.
41
+
- Log analytics for a host pool now includes session host creation activity, providing a consolidated view of session host management. Resource group deployments no longer contain per-session host creation details.
42
+
- The host pool user interface, including banners, provides session host creation status on the session host menu item, though you should also enable log analytics on a host pool to see a detailed diagnostic history.
43
+
- You can now increase the host pool size via API or custom ARM templates, which triggers the Azure Virtual Desktop service to create new session hosts.
44
+
45
+
For more information, see [Create a host pool with a session host configuration](deploy-azure-virtual-desktop.md?pivots=host-pool-session-host-configuration) and [Add session hosts to a host pool](add-session-hosts-host-pool.md?pivots=host-pool-session-host-configuration).
0 commit comments