Skip to content

Commit b966453

Browse files
authored
Merge pull request #91108 from cherylmc/patch-2
Update coexist info to clarify
2 parents 26fcf38 + 87b0921 commit b966453

File tree

1 file changed

+3
-10
lines changed

1 file changed

+3
-10
lines changed

articles/vpn-gateway/vpn-gateway-howto-multi-site-to-site-resource-manager-portal.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,19 +2,12 @@
22
title: 'Add multiple VPN gateway Site-to-Site connections to a VNet: Azure Portal: Resource Manager| Microsoft Docs'
33
description: Add multi-site S2S connections to a VPN gateway that has an existing connection
44
services: vpn-gateway
5-
documentationcenter: na
65
author: cherylmc
7-
manager: jpconnock
8-
editor: ''
9-
tags: azure-resource-manager
106

11-
ms.assetid: f3e8b165-f20a-42ab-afbb-bf60974bb4b1
127
ms.service: vpn-gateway
13-
ms.devlang: na
148
ms.topic: article
15-
ms.tgt_pltfrm: na
169
ms.workload: infrastructure-services
17-
ms.date: 02/14/2018
10+
ms.date: 10/09/2019
1811
ms.author: cherylmc
1912

2013
---
@@ -28,7 +21,7 @@ ms.author: cherylmc
2821
2922
This article helps you add Site-to-Site (S2S) connections to a VPN gateway that has an existing connection by using the Azure portal. This type of connection is often referred to as a "multi-site" configuration. You can add a S2S connection to a VNet that already has a S2S connection, Point-to-Site connection, or VNet-to-VNet connection. There are some limitations when adding connections. Check the [Before you begin](#before) section in this article to verify before you start your configuration.
3023

31-
This article applies to Resource Manager VNets that have a RouteBased VPN gateway. These steps do not apply to ExpressRoute/Site-to-Site coexisting connection configurations. See [ExpressRoute/S2S coexisting connections](../expressroute/expressroute-howto-coexist-resource-manager.md) for information about coexisting connections.
24+
This article applies to Resource Manager VNets that have a RouteBased VPN gateway. These steps do not apply to new ExpressRoute/Site-to-Site coexisting connection configurations. However, if you are merely adding a new VPN connection to an already existing coexist configuration, you can use these steps. See [ExpressRoute/S2S coexisting connections](../expressroute/expressroute-howto-coexist-resource-manager.md) for information about coexisting connections.
3225

3326
### Deployment models and methods
3427
[!INCLUDE [vpn-gateway-classic-rm](../../includes/vpn-gateway-classic-rm-include.md)]
@@ -40,7 +33,7 @@ We update this table as new articles and additional tools become available for t
4033
## <a name="before"></a>Before you begin
4134
Verify the following items:
4235

43-
* You are not creating an ExpressRoute/S2S coexisting connection.
36+
* You are not configuring a new coexisting ExpressRoute and VPN Gateway configuration.
4437
* You have a virtual network that was created using the Resource Manager deployment model with an existing connection.
4538
* The virtual network gateway for your VNet is RouteBased. If you have a PolicyBased VPN gateway, you must delete the virtual network gateway and create a new VPN gateway as RouteBased.
4639
* None of the address ranges overlap for any of the VNets that this VNet is connecting to.

0 commit comments

Comments
 (0)