Skip to content

Commit e16cefe

Browse files
committed
Adding prerequisite to add session hosts
1 parent 79ade1e commit e16cefe

File tree

4 files changed

+31
-5
lines changed

4 files changed

+31
-5
lines changed

articles/virtual-desktop/add-session-hosts-host-pool.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,8 @@ Review the [Prerequisites for Azure Virtual Desktop](prerequisites.md) for a gen
4848

4949
- At least one Windows OS image available on the cluster. For more information, see how to [create VM images using Azure Marketplace images](/azure-stack/hci/manage/virtual-machine-image-azure-marketplace), [use images in Azure Storage account](/azure-stack/hci/manage/virtual-machine-image-storage-account), and [use images in local share](/azure-stack/hci/manage/virtual-machine-image-local-share).
5050

51+
- If you create VMs on Azure Stack HCI outside of the Azure Virtual Desktop service, such as with an automated pipeline, then add them as session hosts to a host pool, you need to install the [Azure Connected Machine agent](../azure-arc/servers/agent-overview.md) on the virtual machines so they can communicate with [Azure Instance Metadata Service](../virtual-machines/instance-metadata-service.md), which is a [required endpoint for Azure Virtual Desktop](../virtual-desktop/required-fqdn-endpoint.md).
52+
5153
- If you want to use Azure CLI or Azure PowerShell locally, see [Use Azure CLI and Azure PowerShell with Azure Virtual Desktop](cli-powershell.md) to make sure you have the [desktopvirtualization](/cli/azure/desktopvirtualization) Azure CLI extension or the [Az.DesktopVirtualization](/powershell/module/az.desktopvirtualization) PowerShell module installed. Alternatively, use the [Azure Cloud Shell](../cloud-shell/overview.md).
5254

5355
> [!IMPORTANT]

articles/virtual-desktop/azure-stack-hci-overview.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ With Azure Virtual Desktop for Azure Stack HCI, you can:
3838

3939
Your Azure Stack HCI clusters need to be running a minimum of [version 23H2](/azure-stack/hci/release-information) and [registered with Azure](/azure-stack/hci/deploy/register-with-azure).
4040

41-
Azure Virtual Desktop for Azure Stack HCI supports the same [Remote Desktop clients](user-documentation/index.yml) as Azure Virtual Desktop, and you can use the following 64-bit operating system images that are in support:
41+
Once you're cluster is ready, you can use the following 64-bit operating system images for your session hosts that are in support:
4242

4343
- Windows 11 Enterprise multi-session
4444
- Windows 11 Enterprise
@@ -53,6 +53,8 @@ To use session hosts on Azure Stack HCI with Azure Virtual Desktop, you also nee
5353

5454
- Install the [Azure Connected Machine agent](../azure-arc/servers/agent-overview.md) on the virtual machines so they can communicate with [Azure Instance Metadata Service](../virtual-machines/instance-metadata-service.md), which is a [required endpoint for Azure Virtual Desktop](../virtual-desktop/required-fqdn-endpoint.md). The Azure Connected Machine agent is automatically installed when you add session hosts using the Azure portal as part of the process to [Deploy Azure Virtual Desktop](deploy-azure-virtual-desktop.md) or [Add session hosts to a host pool](add-session-hosts-host-pool.md).
5555

56+
Finally, users can connect using the same [Remote Desktop clients](users/remote-desktop-clients-overview.md) as Azure Virtual Desktop.
57+
5658
## Licensing and pricing
5759

5860
To run Azure Virtual Desktop on Azure Stack HCI, you need to make sure you're licensed correctly and be aware of the pricing model. There are three components that affect how much it costs to run Azure Virtual Desktop for Azure Stack HCI:

articles/virtual-desktop/deploy-azure-virtual-desktop.md

Lines changed: 24 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -224,9 +224,9 @@ Here's how to create a host pool using the Azure portal.
224224

225225
1. Once the host pool has been created, select **Go to resource** to go to the overview of your new host pool, then select **Properties** to view its properties.
226226

227-
### Optional: Post deployment
227+
### Post deployment
228228

229-
If you also added session hosts to your host pool, there's some extra configuration you might need to do, which is covered in the following sections.
229+
If you also added session hosts to your host pool, there's some extra configuration you need to do, which is covered in the following sections.
230230

231231
[!INCLUDE [include-session-hosts-post-deployment](includes/include-session-hosts-post-deployment.md)]
232232

@@ -751,6 +751,8 @@ Here's how to assign users or user groups to an application group to a workspace
751751
752752
## Next steps
753753
754+
# [Portal](#tab/portal)
755+
754756
Once you've deployed Azure Virtual Desktop, your users can connect. There are several platforms you can connect from, including from a web browser. For more information, see [Remote Desktop clients for Azure Virtual Desktop](users/remote-desktop-clients-overview.md) and [Connect to Azure Virtual Desktop with the Remote Desktop Web client](users/connect-web.md).
755757
756758
Here are some extra tasks you might want to do:
@@ -760,3 +762,23 @@ Here are some extra tasks you might want to do:
760762
- [Add session hosts to a host pool](add-session-hosts-host-pool.md).
761763
762764
- [Enable diagnostics settings](diagnostics-log-analytics.md).
765+
766+
# [Azure PowerShell](#tab/powershell)
767+
768+
Once you've deployed a host pool, workspace, and application group, you'll need to create session hosts before your users can connect. You can do this by following the steps in [Add session hosts to a host pool](add-session-hosts-host-pool.md).
769+
770+
Here are some extra tasks you might want to do:
771+
772+
- Configure profile management with FSLogix. To learn more, see [FSLogix profile containers](fslogix-containers-azure-files.md).
773+
774+
- [Enable diagnostics settings](diagnostics-log-analytics.md).
775+
776+
# [Azure CLI](#tab/cli)
777+
778+
Once you've deployed a host pool, workspace, and application group, you'll need to create session hosts before your users can connect. You can do this by following the steps in [Add session hosts to a host pool](add-session-hosts-host-pool.md).
779+
780+
Here are some extra tasks you might want to do:
781+
782+
- Configure profile management with FSLogix. To learn more, see [FSLogix profile containers](fslogix-containers-azure-files.md).
783+
784+
- [Enable diagnostics settings](diagnostics-log-analytics.md).

articles/virtual-desktop/includes/include-session-hosts-post-deployment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.topic: include
55
ms.date: 11/15/2023
66
---
77

8-
### Licensing
8+
#### Licensing
99

1010
To ensure your session hosts have licenses applied correctly, you'll need to do the following tasks:
1111

@@ -17,7 +17,7 @@ To ensure your session hosts have licenses applied correctly, you'll need to do
1717

1818
<a name='azure-ad-joined-session-hosts'></a>
1919

20-
### Microsoft Entra joined session hosts
20+
#### Microsoft Entra joined session hosts
2121

2222
If your users are going to connect to session hosts joined to Microsoft Entra ID, you'll also need to enable single sign-on or legacy authentication protocols, assign an RBAC role to users, and review your multifactor authentication policies so they can sign in to the VMs.
2323

0 commit comments

Comments
 (0)