Last-minute edits by PM.

Author: Heidilohr

articles/virtual-desktop/create-host-pools-powershell.md

@@ -29,7 +29,7 @@ This article assumes you've already followed the instructions in [Set up the Pow
 Run the following cmdlet to sign in to the Windows Virtual Desktop environment:
 
 ```powershell
-New-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -WorkspaceName <workspacename> 
+New-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -WorkspaceName <workspacename> -HostPoolType <RemoteApp|Desktop>  -Location -DesktopAppGroupName <appgroupname> 
 ```
 
 This will create the host pool, workspace and desktop app group. Additionally, it will register the desktop app group to the workspace. You can only create a workspace with this, not use an existing workspace in this cmdlet. 

articles/virtual-desktop/overview.md

@@ -93,9 +93,12 @@ The Azure virtual machines you create for Windows Virtual Desktop must have acce
 |prod.warmpath.msftcloudes.com|443|Agent traffic|AzureCloud|
 |catalogartifact.azureedge.net|443|Azure Marketplace|AzureCloud|
 |kms.core.windows.net|1688|Windows activation|Internet|
+|wvdportalstorageblob.blob.core.windows.net|443|Resource creation in Azure portal|AzureCloud|
 
 >[!IMPORTANT]
 >We recommend you use the service tags instead of URLs in most cases to prevent service issues. Unblocking these URLs is essential for a reliable Windows Virtual Desktop deployment. Blocking access to these URLs is unsupported and will affect service functionality. These URLs only correspond to Windows Virtual Desktop sites and resources, and don't include URLs for other services like Azure Active Directory.
+>
+>Windows Virtual Desktop now supports the FQDN tag. For more information, see [this article](../firewall/protect-windows-virtual-desktop.md).
 
 The following table lists optional URLs that your Azure virtual machines can have access to: