Linked guidance on removal of SNAT requirement through tag

[juanandmsft]

Linked guidance on how to remove the need of SNAT through disableSnatOnPL tag on the NVA.

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 8f91091:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/private-link/private-endpoint-overview.md	⚠️Warning		Details

articles/private-link/private-endpoint-overview.md

• Line 220, Column 253: [Warning: file-not-found - See documentation] Invalid file link: 'azure/private-link/private-link-disable-snat'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[ShannonLeavitt]

@AbdullahBell - The metadata in this article has an incorrect author value. Could you open a PR in the private repo to change the author value to AbdullahBell?

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

[v-dirichards]

@AbdullahBell Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @abell

[v-ccolin]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[AbdullahBell]

Hello @juanandmsft, please correct this error on line 220:

(/azure/private-link/private-link-disable-snat) in your NVA. |

[v-dirichards]

@juanandmsft - Can you respond to the requested changes or let us know if you would like us to commit them?

@AbdullahBell - 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

[juanandmsft]

@v-dirichards, link should now be fixed.

[learn-build-service-prod]

Learn Build status updates of commit 1091495:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/private-link/private-endpoint-overview.md	✅Succeeded

For more details, please refer to the build report.

[v-dirichards]

@AbdullahBell - 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.

[Copilot]

Pull Request Overview

This PR updates documentation to provide more specific guidance on SNAT requirements for private endpoints. The change clarifies when SNAT is needed and provides a link to documentation about removing this requirement using the disableSnatOnPL tag.

• Updated SNAT limitation description to be more specific about NVA scenarios
• Added reference to disableSnatOnPL tag documentation for removing SNAT requirement

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}