Skip to content

Commit e3b95c3

Browse files
authored
Update vpn-gateway-about-point-to-site-routing.md
1 parent 9426f9d commit e3b95c3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/vpn-gateway/vpn-gateway-about-point-to-site-routing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: cherylmc
66

77
ms.service: vpn-gateway
88
ms.topic: article
9-
ms.date: 10/08/2019
9+
ms.date: 03/24/2020
1010
ms.author: anzaman
1111

1212
---
@@ -48,7 +48,7 @@ The Point-to-Site VPN gateway connection in this example is for a VNet that is n
4848

4949
## <a name="multipeered"></a>Multiple peered VNets
5050

51-
In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 is peered with VNet2. VNet 2 is peered with VNet3. VNet1 is peered with VNet4. There is no direct peering between VNet1 and VNet3. VNet1 has “Allow gateway transit” and VNet2 has “Use remote gateways” enabled.
51+
In this example, the Point-to-Site VPN gateway connection is for VNet1. VNet1 is peered with VNet2. VNet 2 is peered with VNet3. VNet1 is peered with VNet4. There is no direct peering between VNet1 and VNet3. VNet1 has “Allow gateway transit” and VNet2 and VNet4 have “Use remote gateways” enabled.
5252

5353
Clients using Windows can access directly peered VNets, but the VPN client must be downloaded again if any changes are made to VNet peering or the network topology. Non-Windows clients can access directly peered VNets. Access is not transitive and is limited to only directly peered VNets.
5454

0 commit comments

Comments
 (0)