Merge pull request #224125 from igorpag/patch-7

prmerger-automator[bot] · web-flow · commit 1e9727907993 · 2023-02-01T22:00:32.000Z
Update vnet-peering.md
diff --git a/articles/bastion/vnet-peering.md b/articles/bastion/vnet-peering.md
@@ -21,7 +21,7 @@ Azure Bastion works with the following types of peering:
 * **Global virtual network peering:** Connecting virtual networks across Azure regions.
 
 > [!NOTE]
-> This configuration is not supported with Virtual WAN.
+> Deploying Azure Bastion **within** a Virtual WAN hub is not supported. You can deploy Azure Bastion in a spoke VNet and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different VNet via the Virtual WAN hub.
 >
 
 ## Architecture

Original file line number	Diff line number	Diff line change
`@@ -21,7 +21,7 @@ Azure Bastion works with the following types of peering:`
`21`	`21`	`* Global virtual network peering: Connecting virtual networks across Azure regions.`
`22`	`22`
`23`	`23`	`> [!NOTE]`
`24`		`-> This configuration is not supported with Virtual WAN.`
	`24`	`+> Deploying Azure Bastion within a Virtual WAN hub is not supported. You can deploy Azure Bastion in a spoke VNet and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different VNet via the Virtual WAN hub.`
`25`	`25`	`>`
`26`	`26`
`27`	`27`	`## Architecture`