Merge pull request #263215 from dknappettmsft/patch-14

AVD on HCI added Arc VM agent

Author: prmerger-automator[bot]

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

@@ -48,6 +48,8 @@ Review the [Prerequisites for Azure Virtual Desktop](prerequisites.md) for a gen
 
    - 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).
 
+   - 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).
+
 - 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).
 
 > [!IMPORTANT]

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

@@ -34,11 +34,11 @@ With Azure Virtual Desktop for Azure Stack HCI, you can:
 
 - Deploy the latest fully patched images quickly and easily using [Azure Marketplace images](/azure-stack/hci/manage/virtual-machine-image-azure-marketplace).
 
-## Supported platforms
+## Supported deployment configurations
 
-Your Azure Stack HCI clusters need to be running a minimum of version 23H2. For more information, see [Azure Stack HCI release information](/azure-stack/hci/release-information) and [Updates and upgrades](/azure-stack/hci/concepts/updates).
+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).
 
-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:
+Once you're cluster is ready, you can use the following 64-bit operating system images for your session hosts that are in support:
 
 - Windows 11 Enterprise multi-session
 - Windows 11 Enterprise
@@ -47,7 +47,13 @@ Azure Virtual Desktop for Azure Stack HCI supports the same [Remote Desktop clie
 - Windows Server 2022
 - Windows Server 2019
 
-You must license and activate the virtual machines you use for your session hosts on Azure Stack HCI before you use them with Azure Virtual Desktop. For activating Windows 10 and Windows 11 Enterprise multi-session, and Windows Server 2022 Datacenter: Azure Edition, use [Azure verification for VMs](/azure-stack/hci/deploy/azure-verification). For all other OS images (such as Windows 10 and Windows 11 Enterprise, and other editions of Windows Server), you should continue to use existing activation methods. For more information, see [Activate Windows Server VMs on Azure Stack HCI](/azure-stack/hci/manage/vm-activate).
+To use session hosts on Azure Stack HCI with Azure Virtual Desktop, you also need to:
+
+- License and activate the virtual machines. For activating Windows 10 and Windows 11 Enterprise multi-session, and Windows Server 2022 Datacenter: Azure Edition, use [Azure verification for VMs](/azure-stack/hci/deploy/azure-verification). For all other OS images (such as Windows 10 and Windows 11 Enterprise, and other editions of Windows Server), you should continue to use existing activation methods. For more information, see [Activate Windows Server VMs on Azure Stack HCI](/azure-stack/hci/manage/vm-activate).
+
+- 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).
+
+Finally, users can connect using the same [Remote Desktop clients](users/remote-desktop-clients-overview.md) as Azure Virtual Desktop.
 
 ## Licensing and pricing
 

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

@@ -224,9 +224,9 @@ Here's how to create a host pool using the Azure portal.
 
 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.
 
-### Optional: Post deployment
+### Post deployment
 
-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.
+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.
 
 [!INCLUDE [include-session-hosts-post-deployment](includes/include-session-hosts-post-deployment.md)]
 
@@ -751,6 +751,8 @@ Here's how to assign users or user groups to an application group to a workspace
 
 ## Next steps
 
+# [Portal](#tab/portal)
+
 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).
 
 Here are some extra tasks you might want to do:
@@ -760,3 +762,23 @@ Here are some extra tasks you might want to do:
 - [Add session hosts to a host pool](add-session-hosts-host-pool.md).
 
 - [Enable diagnostics settings](diagnostics-log-analytics.md).
+
+# [Azure PowerShell](#tab/powershell)
+
+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).
+
+Here are some extra tasks you might want to do:
+
+- Configure profile management with FSLogix. To learn more, see [FSLogix profile containers](fslogix-containers-azure-files.md).
+
+- [Enable diagnostics settings](diagnostics-log-analytics.md).
+
+# [Azure CLI](#tab/cli)
+
+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).
+
+Here are some extra tasks you might want to do:
+
+- Configure profile management with FSLogix. To learn more, see [FSLogix profile containers](fslogix-containers-azure-files.md).
+
+- [Enable diagnostics settings](diagnostics-log-analytics.md).

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

@@ -5,7 +5,7 @@ ms.topic: include
 ms.date: 11/15/2023
 ---
 
-### Licensing
+#### Licensing
 
 To ensure your session hosts have licenses applied correctly, you'll need to do the following tasks:
 
@@ -17,7 +17,7 @@ To ensure your session hosts have licenses applied correctly, you'll need to do
 
 <a name='azure-ad-joined-session-hosts'></a>
 
-### Microsoft Entra joined session hosts
+#### Microsoft Entra joined session hosts
 
 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.