Linked guidance on removal of SNAT requirement through tag #127362
Conversation
Linked guidance on how to remove the need of SNAT through disableSnatOnPL tag on the NVA.
|
@juanandmsft : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @abell |
|
Learn Build status updates of commit 8f91091:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/private-link/private-endpoint-overview.md | 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.
| @@ -217,7 +217,7 @@ The following information lists the known limitations to the use of private endp | |||
|
|
|||
| | Limitation | Description | | |||
| | --------- | --------- | | |||
| | SNAT is recommended always. | Due to the variable nature of the private endpoint data-plane, it's recommended to SNAT traffic destined to a private endpoint to ensure return traffic is honored. | | |||
| | SNAT is recommended. | Due to the variable nature of the private endpoint data-plane, it's recommended to SNAT traffic destined to a private endpoint to ensure return traffic is honored when going through an NVA. This limitation can be removed using [disableSnatOnPL tag](azure/private-link/private-link-disable-snat) in your NVA | | |||
There was a problem hiding this comment.
| | SNAT is recommended. | Due to the variable nature of the private endpoint data-plane, it's recommended to SNAT traffic destined to a private endpoint to ensure return traffic is honored when going through an NVA. This limitation can be removed using [disableSnatOnPL tag](azure/private-link/private-link-disable-snat) in your NVA | | |
| | SNAT is recommended. | Due to the variable nature of the private endpoint data-plane, it's recommended to SNAT traffic destined to a private endpoint to ensure return traffic is honored when going through an NVA. This limitation can be removed using [disableSnatOnPL tag](/azure/private-link/private-link-disable-snat) in your NVA. | |
Suggestion to fix link and punctuation
|
@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 IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
Linked guidance on how to remove the need of SNAT through disableSnatOnPL tag on the NVA.