MicrosoftDocs
Update kerberos-authentication-portal.md
Is the placement of the Bastion in the same vnet still needed? From my testing i can confirm that a vnet peered to the vnet with bastion is also fine.
Maybee rephrasing to DC must be located in vnet, connected Bation vNet
@chrochma : 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 3c477fb:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/bastion/kerberos-authentication-portal.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
![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?
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
@cherylmc
Can you review the proposed changes and resolve the merge conflict?
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.
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @cherylmc
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
@chrochma : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
@isamorris99
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
Learn Build status updates of commit 1030c83:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/bastion/kerberos-authentication-portal.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
it may work with peered VNets, but its not officially support. since we are jump-box-as a service, our dns lookup during kerberos authentication may not work if the domain controller is not in the same vnet as bastion.
