update

Author: sipastak

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

@@ -11,7 +11,7 @@ ms.date: 04/11/2024
 
 > [!IMPORTANT]
 >- Azure Virtual Desktop on Azure Stack HCI is currently in preview with HCI version 22H2. Portal provisioning is not available. 
->- See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+>- See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. 
 
 Using Azure Virtual Desktop on Azure Stack HCI, you can deploy session hosts for Azure Virtual Desktop where you need them. If you already have an existing on-premises virtual desktop infrastructure (VDI) deployment, Azure Virtual Desktop on Azure Stack HCI can improve your experience. If you're already using Azure Virtual Desktop with your session hosts in Azure, you can extend your deployment to your on-premises infrastructure to better meet your performance or data locality needs.
 
@@ -78,7 +78,7 @@ Azure Virtual Desktop on Azure Stack HCI has the following limitations:
 
 - Azure Stack HCI supports many types of hardware and on-premises networking capabilities, so performance and user density might vary compared to session hosts running on Azure. Azure Virtual Desktop's [virtual machine sizing guidelines](/windows-server/remote/remote-desktop-services/virtual-machine-recs) are broad, so you should use them for initial performance estimates and monitor after deployment.
 
-- You can only join session hosts on Azure Stack HCI to an Active Directory Domain Services domain.
+- You can only join session hosts on Azure Stack HCI to an Active Directory Domain Services domain. Microsoft Entra hybrid join is also available.
 
 ## Next step
 

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

@@ -198,7 +198,7 @@ Here's how to create a host pool by using the Azure portal:
       | **Network and security** |  |
       | **Network dropdown** | Select an existing network to connect each session to. |
       | **Domain to join** |  |
-      | **Select which directory you would like to join** | **Active Directory** is the only available option.  |
+      | **Select which directory you would like to join** | **Active Directory** is the only available option. Microsoft Entra hybrid join is also available.  |
       | **AD domain join UPN** | Enter the user principal name (UPN) of an Active Directory user who has permission to join the session hosts to your domain. |
       | **Password** | Enter the password for the Active Directory user. |
       | **Specify domain or unit** | Select **yes** if you want to join session hosts to a specific domain or be placed in a specific organizational unit (OU). If you select **no**, the suffix of the UPN is used as the domain. |

articles/virtual-desktop/prerequisites.md

@@ -93,7 +93,7 @@ To access desktops and applications from your session hosts, your users need to
 You need to join session hosts that provide desktops and applications to the same Microsoft Entra tenant as your users, or an Active Directory domain (either AD DS or Microsoft Entra Domain Services).
 
 > [!NOTE]
-> For Azure Stack HCI, you can only join session hosts to an Active Directory Domain Services domain. 
+> For Azure Stack HCI, you can only join session hosts to an Active Directory Domain Services domain. Microsoft Entra hybrid join is also available.
 
 To join session hosts to Microsoft Entra ID or an Active Directory domain, you need the following permissions: