From 7b8ca166b5f1c8ba34662512ac164936a12648c4 Mon Sep 17 00:00:00 2001
From: Abhishek Kumar <106214431+abhis08@users.noreply.github.com>
Date: Tue, 28 Jul 2026 23:16:32 +0530
Subject: [PATCH 1/2] Update increase-private-endpoint-vnet-limits.md

---
 .../private-link/increase-private-endpoint-vnet-limits.md   | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/articles/private-link/increase-private-endpoint-vnet-limits.md b/articles/private-link/increase-private-endpoint-vnet-limits.md
index 74bd93de1cbc3..e4ab3f23ed8a9 100644
--- a/articles/private-link/increase-private-endpoint-vnet-limits.md
+++ b/articles/private-link/increase-private-endpoint-vnet-limits.md
@@ -93,6 +93,12 @@ 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.
 
+> [!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.
+
 > [!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.
 

From 76b137d65a96d0dc484c182467d10ef5f1ae5f62 Mon Sep 17 00:00:00 2001
From: Abhishek Kumar <106214431+abhis08@users.noreply.github.com>
Date: Tue, 28 Jul 2026 23:18:53 +0530
Subject: [PATCH 2/2] Update increase-private-endpoint-vnet-limits.md

---
 .../increase-private-endpoint-vnet-limits.md           | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/articles/private-link/increase-private-endpoint-vnet-limits.md b/articles/private-link/increase-private-endpoint-vnet-limits.md
index e4ab3f23ed8a9..8ad2b3a754b5b 100644
--- a/articles/private-link/increase-private-endpoint-vnet-limits.md
+++ b/articles/private-link/increase-private-endpoint-vnet-limits.md
@@ -93,11 +93,6 @@ 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.
 
-> [!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.
 
 > [!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.
@@ -123,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.
 
 ---