Skip to content

Update private endpoint VNet limits documentation - #128666

Open
abhis08 wants to merge 2 commits into
MicrosoftDocs:mainfrom
abhis08:main
Open

Update private endpoint VNet limits documentation#128666
abhis08 wants to merge 2 commits into
MicrosoftDocs:mainfrom
abhis08:main

Conversation

@abhis08

@abhis08 abhis08 commented Jul 28, 2026

Copy link
Copy Markdown

Update private endpoint VNet limits documentation

[!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.

@prmerger-automator

Copy link
Copy Markdown
Contributor

@abhis08 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@prmerger-automator

Copy link
Copy Markdown
Contributor

@abhis08 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 76b137d:

✅ Validation status: passed

File Status Preview URL Details
articles/private-link/increase-private-endpoint-vnet-limits.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
v-dirichards requested a review from Copilot July 29, 2026 14:58

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 privateEndpointVNetPolicies to Basic at 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.

Comment on lines 94 to 98
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.
Comment on lines +121 to +125
> [!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.
@v-dirichards

Copy link
Copy Markdown
Contributor

@ivapplyr

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged tracking label for the PR review team label Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants