Merge pull request #266146 from dknappettmsft/patch-1

AVD private link overview reorder.

Author: prmerger-automator[bot]

articles/virtual-desktop/private-link-overview.md

@@ -21,7 +21,11 @@ Azure Virtual Desktop has three workflows with three corresponding resource type
 
 3. **Connections to host pools**: every connection to a host pool has two sides - clients and session host virtual machines (VMs). To enable connections, you need to create a private endpoint for the *connection* sub-resource for each host pool you want to use with Private Link.
 
-The following table summarizes the private endpoints you need to create:
+The following high-level diagram shows how Private Link securely connects a local client to the Azure Virtual Desktop service. For more detailed information about client connections, see [Client connection sequence](#client-connection-sequence).
+
+:::image type="content" source="media/private-link-diagram.png" alt-text="A high-level diagram that shows Private Link connecting a local client to the Azure Virtual Desktop service.":::
+
+The following table summarizes the private endpoints required:
 
 | Purpose | Resource type | Target sub-resource | Quantity |
 |--|--|--|--|
@@ -31,10 +35,6 @@ The following table summarizes the private endpoints you need to create:
 
 You can either share these private endpoints across your network topology or you can isolate your virtual networks so that each has their own private endpoint to the host pool or workspace.
 
-The following high-level diagram shows how Private Link securely connects a local client to the Azure Virtual Desktop service. For more detailed information about client connections, see [Client connection sequence](#client-connection-sequence).
-
-:::image type="content" source="media/private-link-diagram.png" alt-text="A high-level diagram that shows Private Link connecting a local client to the Azure Virtual Desktop service.":::
-
 ## Supported scenarios
 
 When adding Private Link with Azure Virtual Desktop, you have the following options to connect to Azure Virtual Desktop. Each can be enabled or disabled depending on your requirements.
@@ -85,7 +85,7 @@ When a user connects to Azure Virtual Desktop over Private Link, and Azure Virtu
 
 Private Link with Azure Virtual Desktop has the following limitations:
 
-- Before you use Private Link for Azure Virtual Desktop, you need to [enable the feature](private-link-setup.md#enable-the-feature) on each Azure subscription you want to Private Link with Azure Virtual Desktop.
+- Before you use Private Link for Azure Virtual Desktop, you need to [enable Private Link with Azure Virtual Desktop](private-link-setup.md#enable-private-link-with-azure-virtual-desktop-on-a-subscription) on each Azure subscription you want to Private Link with Azure Virtual Desktop.
 
 - All [Remote Desktop clients to connect to Azure Virtual Desktop](users/remote-desktop-clients-overview.md) can be used with Private Link. If you're using the [Remote Desktop client for Windows](./users/connect-windows.md) on a private network without internet access and you're subscribed to both public and private feeds, you aren't able to access your feed.
 
@@ -98,8 +98,6 @@ Private Link with Azure Virtual Desktop has the following limitations:
 
 - Early in the preview of Private Link with Azure Virtual Desktop, the private endpoint for the initial feed discovery (for the *global* sub-resource) shared the private DNS zone name of `privatelink.wvd.microsoft.com` with other private endpoints for workspaces and host pools. In this configuration, users are unable to establish private endpoints exclusively for host pools and workspaces. Starting September 1, 2023, sharing the private DNS zone in this configuration will no longer be supported. You need to create a new private endpoint for the *global* sub-resource to use the private DNS zone name of `privatelink-global.wvd.microsoft.com`. For the steps to do this, see [Initial feed discovery](private-link-setup.md#initial-feed-discovery).
 
-- Azure PowerShell cmdlets for Azure Virtual Desktop that support Private Link are in preview. You need to download and install the [preview version of the Az.DesktopVirtualization module](https://www.powershellgallery.com/packages/Az.DesktopVirtualization/5.0.0-preview) to use these cmdlets, which have been added in version 5.0.0.
-
 ## Next steps
 
 - Learn how to [Set up Private Link with Azure Virtual Desktop](private-link-setup.md).

articles/virtual-desktop/private-link-setup.md

@@ -28,14 +28,14 @@ In order to use Private Link with Azure Virtual Desktop, you need the following
 
 - Azure PowerShell cmdlets for Azure Virtual Desktop that support Private Link are in preview. You'll need to download and install the [preview version of the Az.DesktopVirtualization module](https://www.powershellgallery.com/packages/Az.DesktopVirtualization/5.0.0-preview) to use these cmdlets, which have been added in version 5.0.0.
 
-## Enable the feature
+## Enable Private Link with Azure Virtual Desktop on a subscription
 
 To use Private Link with Azure Virtual Desktop, you need to re-register the *Microsoft.DesktopVirtualization* resource provider on each subscription you want to use Private Link with Azure Virtual Desktop.
 
 > [!IMPORTANT]
 > For Azure for US Government and Azure operated by 21Vianet, you also need to register the feature for each subscription.
 
-### Register the feature (Azure for US Government and Azure operated by 21Vianet only)
+### Register Private Link with Azure Virtual Desktop (Azure for US Government and Azure operated by 21Vianet only)
 
 To register the *Azure Virtual Desktop Private Link* feature:
 
@@ -125,7 +125,6 @@ Here's how to create a private endpoint for the *connection* sub-resource for co
 
 1. Select **Create** to create the private endpoint for the connection sub-resource.
 
-
 # [Azure PowerShell](#tab/powershell)
 
 Here's how to create a private endpoint for the *connection* sub-resource used for connections to a host pool using the [Az.Network](/powershell/module/az.network/) and [Az.DesktopVirtualization](/powershell/module/az.desktopvirtualization/) PowerShell modules.
@@ -232,7 +231,7 @@ Here's how to create a private endpoint for the *connection* sub-resource used f
       New-AzPrivateEndpoint @parameters
       ```
 
-   Your output should be similar to the following. Check that the value for **ProvisioningState** is **Succeeded**.
+   Your output should be similar to the following output. Check that the value for **ProvisioningState** is **Succeeded**.
 
    ```output
    ResourceGroupName Name            Location ProvisioningState Subnet
@@ -312,7 +311,7 @@ Here's how to create a private endpoint for the *connection* sub-resource used f
           --output table
       ```
 
-   Your output should be similar to the following. Check that the value for **ProvisioningState** is **Succeeded**.
+   Your output should be similar to the following output. Check that the value for **ProvisioningState** is **Succeeded**.
 
    ```output
    CustomNetworkInterfaceName    Location    Name                  ProvisioningState    ResourceGroup