Update Azure Bastion FAQ for Virtual WAN support #128053
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Clarified Azure Bastion support for Virtual WAN, including details on subnet requirements and routing configurations.
Contributor
|
@aparnabhatms : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @abell |
Contributor
|
Learn Build status updates of commit bc3d1a9:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/bastion/bastion-faq.md | Details |
articles/bastion/bastion-faq.md
- Line 39, Column 227: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/architecture/networking/guide/private-link-virtual-wan-dns-virtual-hub-extension-pattern' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 39, Column 877: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies#azurefirewall' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 39, Column 227: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/architecture/networking/guide/private-link-virtual-wan-dns-virtual-hub-extension-pattern' will be broken in isolated environments. Replace with a relative link. - Line 39, Column 877: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies#azurefirewall' will be broken in isolated environments. Replace with a relative link.
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.
| ### <a name="vwan"></a>Does Azure Bastion support Virtual WAN? | ||
|
|
||
| Yes, you can use Azure Bastion for Virtual WAN deployments. However, deploying Azure Bastion within a Virtual WAN hub isn't supported. You can deploy Azure Bastion in a spoke virtual network and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different virtual network via the Virtual WAN hub. If the Azure Virtual WAN hub will be integrated with Azure Firewall as a [Secured Virtual Hub](../firewall-manager/secured-virtual-hub.md), the AzureBastionSubnet must reside within a Virtual Network where the default 0.0.0.0/0 route propagation is disabled at the virtual network connection level. | ||
| Yes, you can use Azure Bastion for Virtual WAN deployments. However, deploying Azure Bastion within a Virtual WAN hub isn't supported. You can deploy Azure Bastion in a spoke virtual network with only AzureBastionSubnet using [virtual hub extention pattern](https://learn.microsoft.com/en-us/azure/architecture/networking/guide/private-link-virtual-wan-dns-virtual-hub-extension-pattern) and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different virtual network via the Virtual WAN hub. If the Azure Virtual WAN hub will be integrated with Azure Firewall as a [Secured Virtual Hub](../firewall-manager/secured-virtual-hub.md), the AzureBastionSubnet must reside within a Virtual Network where the default 0.0.0.0/0 route propagation is disabled at the virtual network connection level. Additionally, under the [Secured hub routing configuration](https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies#azurefirewall), INTERNET TRAFFIC for the Bastion spoke should be set to Unsecured. This ensures that Internet traffic to the Bastion Host does not pass through the Azure Firewall. |
Contributor
There was a problem hiding this comment.
Suggested change
| Yes, you can use Azure Bastion for Virtual WAN deployments. However, deploying Azure Bastion within a Virtual WAN hub isn't supported. You can deploy Azure Bastion in a spoke virtual network with only AzureBastionSubnet using [virtual hub extention pattern](https://learn.microsoft.com/en-us/azure/architecture/networking/guide/private-link-virtual-wan-dns-virtual-hub-extension-pattern) and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different virtual network via the Virtual WAN hub. If the Azure Virtual WAN hub will be integrated with Azure Firewall as a [Secured Virtual Hub](../firewall-manager/secured-virtual-hub.md), the AzureBastionSubnet must reside within a Virtual Network where the default 0.0.0.0/0 route propagation is disabled at the virtual network connection level. Additionally, under the [Secured hub routing configuration](https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies#azurefirewall), INTERNET TRAFFIC for the Bastion spoke should be set to Unsecured. This ensures that Internet traffic to the Bastion Host does not pass through the Azure Firewall. | |
| Yes, you can use Azure Bastion for Virtual WAN deployments. However, deploying Azure Bastion within a Virtual WAN hub isn't supported. You can deploy Azure Bastion in a spoke virtual network with only AzureBastionSubnet using [virtual hub extension pattern](/azure/architecture/networking/guide/private-link-virtual-wan-dns-virtual-hub-extension-pattern) and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different virtual network via the Virtual WAN hub. If the Azure Virtual WAN hub will be integrated with Azure Firewall as a [Secured Virtual Hub](../firewall-manager/secured-virtual-hub.md), the AzureBastionSubnet must reside within a Virtual Network where the default 0.0.0.0/0 route propagation is disabled at the virtual network connection level. Additionally, under the [Secured hub routing configuration](/azure/virtual-wan/how-to-routing-policies#azurefirewall), INTERNET TRAFFIC for the Bastion spoke should be set to Unsecured. This ensures that Internet traffic to the Bastion Host does not pass through the Azure Firewall. |
Suggestion to fix links and typo
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Azure Bastion FAQ to provide more detailed guidance on Virtual WAN support. The changes clarify deployment patterns and routing configurations when using Azure Bastion with Virtual WAN and Azure Firewall.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### <a name="vwan"></a>Does Azure Bastion support Virtual WAN? | ||
|
|
||
| Yes, you can use Azure Bastion for Virtual WAN deployments. However, deploying Azure Bastion within a Virtual WAN hub isn't supported. You can deploy Azure Bastion in a spoke virtual network and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different virtual network via the Virtual WAN hub. If the Azure Virtual WAN hub will be integrated with Azure Firewall as a [Secured Virtual Hub](../firewall-manager/secured-virtual-hub.md), the AzureBastionSubnet must reside within a Virtual Network where the default 0.0.0.0/0 route propagation is disabled at the virtual network connection level. | ||
| Yes, you can use Azure Bastion for Virtual WAN deployments. However, deploying Azure Bastion within a Virtual WAN hub isn't supported. You can deploy Azure Bastion in a spoke virtual network with only AzureBastionSubnet using [virtual hub extention pattern](https://learn.microsoft.com/en-us/azure/architecture/networking/guide/private-link-virtual-wan-dns-virtual-hub-extension-pattern) and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different virtual network via the Virtual WAN hub. If the Azure Virtual WAN hub will be integrated with Azure Firewall as a [Secured Virtual Hub](../firewall-manager/secured-virtual-hub.md), the AzureBastionSubnet must reside within a Virtual Network where the default 0.0.0.0/0 route propagation is disabled at the virtual network connection level. Additionally, under the [Secured hub routing configuration](https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies#azurefirewall), INTERNET TRAFFIC for the Bastion spoke should be set to Unsecured. This ensures that Internet traffic to the Bastion Host does not pass through the Azure Firewall. |
There was a problem hiding this comment.
This sentence is very long and covers multiple distinct topics (deployment pattern, IP-based connections, secured virtual hub configuration, and routing settings). Consider breaking it into separate sentences or a bulleted list for better readability.
Contributor
|
@AbdullahBell - Could you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clarified Azure Bastion support for Virtual WAN, including details on subnet requirements and routing configurations.