MicrosoftDocs
Update bastion-nsg.md
The following should be clearly stated in the doc:
"NSGs rules by default allow traffic that is coming from within the virtual network, in other words, virtual machines within the virtual network can communicate with each other. Subsequently, you can RDP via Azure Bastion to connect from your first virtual machine then connect to the second virtual machine."
@azarboon : Thanks for your contribution! The author(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 7cf884b:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/active-directory-b2c/microsoft-graph-operations.md | :warning:Warning | Details | |
| articles/bastion/bastion-nsg.md | :white_check_mark:Succeeded |
articles/active-directory-b2c/microsoft-graph-operations.md
- Line 265, Column 1: [Warning: invalid-code]
The code snippet "~/ms-identity-dotnetcore-b2c-account-management/src/Program.cs" could not be found. - Line 269, Column 1: [Warning: invalid-code]
The code snippet "~/ms-identity-dotnetcore-b2c-account-management/src/Services/UserService.cs" could not be found.
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.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@cherylmc
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@cherylmc
Can you review this old PR and determine whether it needs to be closed or merged?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. If the changes no longer apply, add an explanation and a #please-close comment to close the PR.
@MicrosoftDocs/public-repo-pr-review-team
#please-close Hi! The PMs said that we should close this one. It's not a scenario that we will document. Thanks!
