Merge pull request #187376 from webreidi/master

Update app group limit warning and add link

Author: denrea

articles/virtual-desktop/automatic-migration.md

@@ -33,7 +33,7 @@ Before you use the migration module, make sure you have the following things rea
 - PowerShell or PowerShell ISE to run the scripts you'll see in this article. The Microsoft.RdInfra.RDPowershell module doesn't work in PowerShell Core.
 
 >[!IMPORTANT]
->Migration only creates service objects in the US geography. If you try to migrate your service objects to another geography, it won't work. Also, if you have more than 200 app groups in your Azure Virtual Desktop (classic) deployment, you won't be able to migrate. You'll only be able to migrate if you rebuild your environment to reduce the number of app groups within your Azure Active Directory (Azure AD) tenant.
+>Migration only creates service objects in the US geography. If you try to migrate your service objects to another geography, it won't work. Also, if you have more than 500 app groups in your Azure Virtual Desktop (classic) deployment, you won't be able to migrate. You'll only be able to migrate if you rebuild your environment to reduce the number of app groups within your Azure Active Directory (Azure AD) tenant.
 
 ## Prepare your PowerShell environment
 

articles/virtual-desktop/faq.yml

@@ -155,6 +155,8 @@ sections:
         answer: |
           Yes. Azure Virtual Desktop host pools have an option for selecting either availability set or availability zones when you create a VM. These availability options are the same as the ones Azure Compute uses. If you select a zone for the VM you create in a host pool, the setting automatically applies to all VMs you create in that zone. If you'd prefer to spread your host pool VMs across multiple zones, you'll need to follow the directions in [Add virtual machines with the Azure portal](expand-existing-host-pool.md#add-virtual-machines-with-the-azure-portal) to manually select a new zone for each new VM you create.
           
+          Make sure that [your Azure availability zones](../availability-zones/az-overview.md#azure-regions-with-availability-zones) are available in the region where your VMs are located.
+          
       - question: |
          Which availability option is best for me?
         answer: |