Update private endpoint VNet limits documentation - #128666
Conversation
|
@abhis08 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@abhis08 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 76b137d: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the Private Endpoint VNet limits documentation to clarify a routing/policy prerequisite when using UDRs for Private Endpoint traffic, helping prevent connectivity loss scenarios.
Changes:
- Adds an IMPORTANT note explaining the need to set
privateEndpointVNetPoliciestoBasicat the VNet level when using a UDR next hop to Virtual Network. - Adds minor spacing adjustment near the warning block.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 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. |
| > [!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. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Update private endpoint VNet limits documentation