Skip to content

Commit 3495cad

Browse files
authored
Update virtual-network-manage-peering.md
1 parent 43566b7 commit 3495cad

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/virtual-network/virtual-network-manage-peering.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,9 @@ Before creating a peering, familiarize yourself with the requirements and constr
5959
Only one peering for this virtual network can have this setting enabled.
6060

6161
You cannot use remote gateways if you already have a gateway configured in your virtual network. To learn more about using a gateway for transit, see [Configure a VPN gateway for transit in a virtual network peering](../vpn-gateway/vpn-gateway-peering-gateway-transit.md?toc=%2fazure%2fvirtual-network%2ftoc.json)
62+
63+
[!NOTE]
64+
Whenever using a Virtual Network Gateway to send on-premises traffic transitively to a peered VNet you must ensure that the on-premises VPN device has the peered VNet IP range set as 'interesting' traffic. Otherwise, your on-premises resources will not be able to communicate with resources in the peered VNet.
6265

6366
6. Select **OK** to add the peering to the virtual network you selected.
6467

0 commit comments

Comments
 (0)