Fixed blocking issues

Author: dknappettmsft

articles/virtual-desktop/TOC.yml

@@ -284,7 +284,7 @@
       - name: Set personal desktop assignment type
         href: configure-host-pool-personal-desktop-assignment-type.md
       - name: Configure a validation environment
-        href: create-validation-host-pool.md
+        href: configure-validation-environment.md
       - name: Scheduled Agent Updates
         href: scheduled-agent-updates.md
       - name: Delete a host pool

articles/virtual-desktop/create-host-pool.md

@@ -2,6 +2,7 @@
 title: Create a host pool - Azure Virtual Desktop
 description: Learn how to create a host pool in Azure Virtual Desktop by using the Azure portal, Azure CLI, or Azure PowerShell.
 ms.topic: how-to
+ms.custom: references_regions
 author: dknappettmsft
 ms.author: daknappe
 ms.date: 02/28/2023

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

@@ -17,7 +17,7 @@ To ensure your session hosts have licenses applied correctly, you'll need to do
 
 If your users are going to connect to session hosts joined to Azure Active Directory, you'll need to do the following tasks:
 
-- If your users are going to connect to session hosts joined to Azure Active Directory, you must assign them the [*Virtual Machine User Login*](../../role-based-access-control/built-in-roles.md#virtual-machine-user-login) or [*Virtual Machine Administrator Login*](../../role-based-access-control/built-in-roles.md#virtual-machine-administrator-login) RBAC role either on the each virtual machine, the resource group containing the virtual machines, or the subscription. We recommend you assign the *Virtual Machine User Login* RBAC role on the resource group containing your session hosts to the same user group as the you assign to the application group. For more information, see [Log in to a Windows virtual machine in Azure by using Azure AD](../../active-directory/devices/howto-vm-sign-in-azure-ad-windows.md#configure-role-assignments-for-the-vm).
+- If your users are going to connect to session hosts joined to Azure Active Directory, you must assign them the [*Virtual Machine User Login*](../../role-based-access-control/built-in-roles.md#virtual-machine-user-login) or [*Virtual Machine Administrator Login*](../../role-based-access-control/built-in-roles.md#virtual-machine-administrator-login) RBAC role either on each virtual machine, the resource group containing the virtual machines, or the subscription. We recommend you assign the *Virtual Machine User Login* RBAC role on the resource group containing your session hosts to the same user group as you assign to the application group. For more information, see [Log in to a Windows virtual machine in Azure by using Azure AD](../../active-directory/devices/howto-vm-sign-in-azure-ad-windows.md#configure-role-assignments-for-the-vm).
 
 - For users connecting from Windows devices that aren't joined to Azure AD or non-Windows devices, add the custom RDP property `targetisaadjoined:i:1` to the host pool's RDP properties. These connections are restricted to entering user name and password credentials when signing in to a session host. For more information, see [Customize RDP properties for a host pool](../customize-rdp-properties.md).
 

articles/virtual-desktop/prerequisites.md

@@ -88,7 +88,7 @@ You'll need to enter the following identity parameters when deploying session ho
 > [!IMPORTANT]
 > The account you use for joining a domain can't have multi-factor authentication (MFA) enabled.
 > 
-> When joining an Azure AD DS domain, the account you use must be part of the AAD DC administrators group.
+> When joining an Azure AD DS domain, the account you use must be part of the *AAD DC administrators* group.
 
 ## Operating systems and licenses