Skip to content

Commit afbb1e9

Browse files
authored
Update requirements-network.md
1 parent 101ce66 commit afbb1e9

1 file changed

Lines changed: 8 additions & 4 deletions

File tree

windows-365/enterprise/requirements-network.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -86,10 +86,14 @@ You must allow traffic in your Azure network configuration to the following serv
8686

8787
All endpoints connect over port 443.
8888

89-
>[!IMPORTANT]
90-
>AVD's RDP Broker service endpoints are critical to the end user's experience with their Cloud PCs, and affectivty both connectivity and latency. These should be categorized as **Optimize** endpoints, based on the [Microsoft 365 network connectivity principles](/microsoft-365/enterprise/microsoft-365-network-connectivity-principles?view=o365-worldwide#new-office-365-endpoint-categories). To ease configuration of network security controls, use Service Tags for Azure Virtual Desktop to identity those endpoints for direct routing using an [Azure Networking User Defined Route (UDR)](/azure/virtual-network/virtual-networks-udr-overview). A UDR will result in direct routing between your virtual network and the RDP Broker for lowest latency. For more information on Azure Service Tags and their use in simplifying virtual network configuration, see (Azure service tags overview)[/azure/virtual-desktop/network-connectivity]. For more information about
91-
>
92-
>Changing the network routes of a Cloud PC, either at the network layer or at the Cloud PC layer (e.g. VPN), is likely to break the connection between the Cloud PC and the AVD RDP Broker. This will result in the end user being disconnected from their Cloud PC until a connection be established.
89+
### Remote Desktop Protocol (RDP) broker service endpoints
90+
91+
Azure Virtual Desktop RDP broker service endpoints are critical to Cloud PC performance. These endpoints affect both connectivity and latency. To align with the [Microsoft 365 network connectivity principles](/microsoft-365/enterprise/microsoft-365-network-connectivity-principles?view=o365-worldwide#new-office-365-endpoint-categories), you should categorize these endpoints as **Optimize** endpoints.
92+
93+
To make it easier to configure network security controls, use Azure Virtual Desktop service tags to identity those endpoints for direct routing using an [Azure Networking User Defined Route (UDR)](/azure/virtual-network/virtual-networks-udr-overview). A UDR will result in direct routing between your virtual network and the RDP broker for lowest latency. For more information about Azure Service Tags, see (Azure service tags overview)[/azure/virtual-desktop/network-connectivity].
94+
95+
Changing the network routes of a Cloud PC (at the network layer or at the Cloud PC layer (e.g. VPN)), might break the connection between the Cloud PC and the Azure Virtual Desktop RDP broker. If so, the end user will be disconnected from their Cloud PC until a connection be established.
96+
9397

9498
## DNS requirements
9599

0 commit comments

Comments
 (0)