Clarify Bastion domain controller requirement to include peered virtu…#128225
Clarify Bastion domain controller requirement to include peered virtu…#128225Keanu-Mellett wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
…al networks Updates the Bastion domain controller requirement to reflect that the domain controller can be hosted in the same virtual network as Bastion or in a peered virtual network, improving accuracy for supported deployment scenarios.
|
@Keanu-Mellett : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @abell |
|
Learn Build status updates of commit 98e7b2f: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR updates the documentation for Azure Bastion's Kerberos authentication to clarify that domain controllers can be hosted in either the same virtual network as Bastion or in a peered virtual network, expanding the supported deployment scenarios.
Changes:
- Updated domain controller requirement text to include peered virtual networks as a supported configuration
- Improved capitalization and hyphenation for consistency ("Azure-hosted" and "Bastion")
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Updates the Bastion domain controller requirement to reflect that the domain controller can be hosted in the same virtual network as Bastion or in a peered virtual network, improving accuracy for supported deployment scenarios.