Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add details on outbound SNAT #124623

Merged
merged 1 commit into from
Oct 17, 2024
Merged

Conversation

wilfriedwoivre
Copy link
Contributor

Add the IANA RFC 6598 on the FAQ as indicate on the specific page https://learn.microsoft.com/en-us/azure/firewall/snat-private-range?WT.mc_id=AZ-MVP-4039694

Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit d3bad46:

✅ Validation status: passed

File Status Preview URL Details
articles/firewall/firewall-faq.yml ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link
Contributor

PRMerger Results

Issue Description
Yaml File(s) This PR includes changes to .yml file(s) owned by another author.

@Jak-MS
Copy link
Contributor

Jak-MS commented Oct 11, 2024

@vhorne
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 Oct 11, 2024
@vhorne
Copy link
Contributor

vhorne commented Oct 17, 2024

#sign-off

@wilfriedwoivre
Copy link
Contributor Author

@vhorne Thanks for your review, can you approve or reject the change.

@ShannonLeavitt ShannonLeavitt merged commit b44c9b5 into MicrosoftDocs:main Oct 17, 2024
2 checks passed
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