diff --git a/articles/private-link/increase-private-endpoint-vnet-limits.md b/articles/private-link/increase-private-endpoint-vnet-limits.md
index 74bd93de1cbc3..8ad2b3a754b5b 100644
--- a/articles/private-link/increase-private-endpoint-vnet-limits.md
+++ b/articles/private-link/increase-private-endpoint-vnet-limits.md
@@ -93,6 +93,7 @@ Resources
 
 To enable this feature, configure *Private Endpoint virtual network Policies*. We recommend enabling this property for all virtual networks you want to include in this feature and for all connected compute virtual networks in peering scenarios.
 
+
 > [!WARNING]
 > Upgrading or downgrading this feature triggers a platform update and results in a one-time connection reset. We recommend performing this action during a maintenance window.
 
@@ -117,6 +118,11 @@ resourceGroupName="myResourceGroup"
 az network vnet update --name $vnetName --resource-group $resourceGroupName --pe-vnet-policies="Basic"
 
 ```
+> [!IMPORTANT]
+
+> When using a User Defined Route (UDR) with **Next Hop Type = Virtual Network** for Private Endpoint traffic, configuring `privateEndpointNetworkPolicies` on the Private Endpoint subnet alone isn't sufficient.
+> The virtual network must also have `privateEndpointVNetPolicies` configured as `Basic`.
+> Otherwise, the system-generated Private Endpoint route can be invalidated when Private Endpoint network policies are enabled, while the UDR doesn't become the effective route, resulting in connectivity failure to the Private Endpoint.
 
 ---