azure-docs Adding knowledge about not using ports below 1024 on unix-based OS

There is at least one open issue at az-cli GitHub about getting errors with 'az network bastion tunnel' command when using local port 22 to open the tunnel on unix-based operating system. As ports below 1024 are privileged ports only accessible by root I would recommend that the information about this is added into examples.

Mar 18 '25 22:03 tsimiz

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

Mar 18 '25 22:03 prmerger-automator[bot]

Learn Build status updates of commit 2d3b93f:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
includes/bastion-native-connect-tunnel.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

Mar 18 '25 23:03 learn-build-service-prod[bot]

@cherylmc

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

Mar 19 '25 14:03 ttorble

I sent an email to the content owner today.

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

May 21 '25 21:05 v-dirichards

Product team is investigating.

May 23 '25 16:05 cherylmc

I sent an email to the content owner today.

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

Jun 20 '25 07:06 v-ccolin

#assign:isamorris99

Jun 20 '25 15:06 cherylmc

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

Thanks!

Jun 20 '25 20:06 v-dirichards

@isamorris99

Can you review this old PR and determine whether it needs to be closed or merged?

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

Jul 01 '25 15:07 v-dirichards

I sent a Teams message to the content owner today.

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

Jul 22 '25 20:07 v-dirichards

I sent email to the content owner today.

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

Aug 14 '25 07:08 ttorble

I sent an email to the content owner today.

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

Sep 19 '25 09:09 v-ccolin

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

Oct 15 '25 15:10 ttorble

#sign-off

Oct 15 '25 15:10 asudbring

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

Oct 15 '25 15:10 prmerger-automator[bot]