Skip to content

Conversation

jp-poulin
Copy link

Correct "Ah" protocol to "Any" in the NSG rules

Correct "Ah" protocol to "Any" in the NSG rules
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit de49951:

✅ Validation status: passed

File Status Preview URL Details
articles/bastion/bastion-nsg.md ✅Succeeded

For more details, please refer to the build report.

@ShannonLeavitt
Copy link
Contributor

@AbdullahBell - You weren't automatically assigned to this PR because the author metadata is incorrect:

image

When you get a chance, could you open a PR in the private repo to fix the metadata?

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 Sep 16, 2025
@jp-poulin
Copy link
Author

Looks like the "Ah" value is actually correct based on the documentation:
https://learn.microsoft.com/en-us/powershell/module/az.network/add-aznetworksecurityruleconfig?view=azps-14.4.0#-protocol

Not sure why the PowerShell values and portal values don't match. The portal will show "Ah" when PowerShell was used to set it up, but if you open the NSG rule, make no change and hit save, it will change it to "Any".

So this issue needs to be modified from updating a doc to somewhat challenging why the source parameter is not "Any".

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.

3 participants