Clarifies IP addresses required

Author: dknappettmsft

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

@@ -65,13 +65,21 @@ To re-register the *Microsoft.DesktopVirtualization* resource provider:
 
 ## Create private endpoints
 
-During the setup process, you create private endpoints to the following resources:
+During the setup process, you create private endpoints to the following resources, depending on your scenario.
 
-| Purpose | Resource type | Target sub-resource | Endpoint quantity | IP address quantity |
-|--|--|--|--|--|
-| Connections to host pools | Microsoft.DesktopVirtualization/hostpools | connection | One per host pool | Four per endpoint |
-| Feed download | Microsoft.DesktopVirtualization/workspaces | feed | One per workspace | Two per endpoint |
-| Initial feed discovery | Microsoft.DesktopVirtualization/workspaces | global | **Only one for all your Azure Virtual Desktop deployments** | One per endpoint |
+1. Both clients and session host VMs use private routes. You need the following private endpoints:
+   
+   | Purpose | Resource type | Target sub-resource | Endpoint quantity | IP address quantity |
+   |--|--|--|--|--|
+   | Connections to host pools | Microsoft.DesktopVirtualization/hostpools | connection | One per host pool | Four per endpoint |
+   | Feed download | Microsoft.DesktopVirtualization/workspaces | feed | One per workspace | Two per endpoint |
+   | Initial feed discovery | Microsoft.DesktopVirtualization/workspaces | global | **Only one for all your Azure Virtual Desktop deployments** | One per endpoint |
+
+1. Clients use public routes while session host VMs use private routes. You need the following private endpoints. Endpoints to workspaces aren't required.
+
+   | Purpose | Resource type | Target sub-resource | Endpoint quantity | IP address quantity |
+   |--|--|--|--|--|
+   | Connections to host pools | Microsoft.DesktopVirtualization/hostpools | connection | One per host pool | Four per endpoint |
 
 > [!IMPORTANT]
 > IP address allocations are subject to change as the demand for IP addresses increases. During capacity expansions, additional addresses are needed for private endpoints. It's important you consider potential address space exhaustion and ensure sufficient headroom for growth. For more information on determining the appropriate network configuration for private endpoints in either a hub or a spoke topology, see [Decision tree for Private Link deployment](/azure/architecture/networking/guide/private-link-hub-spoke-network#decision-tree-for-private-link-deployment).
@@ -377,7 +385,6 @@ To create a private endpoint for the *feed* sub-resource for a workspace, select
 
 1. Select **Create** to create the private endpoint for the feed sub-resource.
 
-
 # [Azure PowerShell](#tab/powershell)
 
 1. In the same PowerShell session, create a Private Link service connection for a workspace with the feed sub-resource by running the following commands. In these examples, the same virtual network and subnet are used.