You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/vpn-gateway/vpn-gateway-howto-multi-site-to-site-resource-manager-portal.md
+3-10Lines changed: 3 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,19 +2,12 @@
2
2
title: 'Add multiple VPN gateway Site-to-Site connections to a VNet: Azure Portal: Resource Manager| Microsoft Docs'
3
3
description: Add multi-site S2S connections to a VPN gateway that has an existing connection
4
4
services: vpn-gateway
5
-
documentationcenter: na
6
5
author: cherylmc
7
-
manager: jpconnock
8
-
editor: ''
9
-
tags: azure-resource-manager
10
6
11
-
ms.assetid: f3e8b165-f20a-42ab-afbb-bf60974bb4b1
12
7
ms.service: vpn-gateway
13
-
ms.devlang: na
14
8
ms.topic: article
15
-
ms.tgt_pltfrm: na
16
9
ms.workload: infrastructure-services
17
-
ms.date: 02/14/2018
10
+
ms.date: 10/09/2019
18
11
ms.author: cherylmc
19
12
20
13
---
@@ -28,7 +21,7 @@ ms.author: cherylmc
28
21
29
22
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.
30
23
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.
@@ -40,7 +33,7 @@ We update this table as new articles and additional tools become available for t
40
33
## <aname="before"></a>Before you begin
41
34
Verify the following items:
42
35
43
-
* You are not creating an ExpressRoute/S2S coexisting connection.
36
+
* You are not configuring a new coexisting ExpressRoute and VPN Gateway configuration.
44
37
* You have a virtual network that was created using the Resource Manager deployment model with an existing connection.
45
38
* 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.
46
39
* None of the address ranges overlap for any of the VNets that this VNet is connecting to.
0 commit comments