PR for merging PowerShell Script for Ingress and Egress Rules for AzureBastionSubnet NSG

[gayatriramac]

Added a powershell script to add the mentioned 8 network security rules (4 inbound and 4 outbound) to the network security group created for AzureBastionSubnet.

This script is tested.

Inbound Rules:
Via Script:

Via Documentation:

Outbound Rules:
Via Script:

Via Documentation:

Note: The protocol is "Ah" as the powershell code uses "Ah" for "Any" protocol type.

[prmerger-automator]

@gayatriramac : 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 6e319b8:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/bastion/bastion-nsg.md	⚠️Warning		Details

articles/bastion/bastion-nsg.md

• Line 58, Column 1: [Warning: code-block-unclosed - See documentation] Unclosed code block. Code blocks must begin and end with triple backticks (```).

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.

[Court72]

@AbdullahBell

Can you review the proposed changes? Note that the validation warning must be resolved before merging.

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

[isamorris99]

#sign-off

[prmerger-automator]

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

[Court72]

@isamorris99,

PRMerger will only accept sign off from the article's listed author. However, if you are a Microsoft employee authorized to update this content, you can send a request to [email protected] for this PR to be merged. Include your role and an explanation of why the PR should be merged without approval from the listed author.

Important: The validation warning must be resolved before we can merge.