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-vnet-vnet-resource-manager-portal.md
+19-22Lines changed: 19 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,22 +2,20 @@
2
2
title: 'Configure a VNet-to-VNet VPN gateway connection: Azure portal'
3
3
titleSuffix: Azure VPN Gateway
4
4
description: Learn how to create a VPN gateway connection between VNets.
5
-
services: vpn-gateway
6
5
author: cherylmc
7
-
8
6
ms.service: vpn-gateway
9
7
ms.topic: how-to
10
-
ms.date: 09/23/2021
8
+
ms.date: 09/14/2022
11
9
ms.author: cherylmc
12
10
13
11
---
14
12
# Configure a VNet-to-VNet VPN gateway connection by using the Azure portal
15
13
16
-
This article helps you connect virtual networks (VNets) by using the VNet-to-VNet connection type using the Azure portal. The virtual networks can be in different regions and from different subscriptions. When you connect VNets from different subscriptions, the subscriptions don't need to be associated with the same Active Directory tenant. This type of configuration creates a connection between two virtual network gateways. This article does not apply to VNet peering. For VNet peering, see the [Virtual Network peering](../virtual-network/virtual-network-peering-overview.md) article.
14
+
This article helps you connect virtual networks (VNets) by using the VNet-to-VNet connection type using the Azure portal. The virtual networks can be in different regions and from different subscriptions. When you connect VNets from different subscriptions, the subscriptions don't need to be associated with the same Active Directory tenant. This type of configuration creates a connection between two virtual network gateways. This article doesn't apply to VNet peering. For VNet peering, see the [Virtual Network peering](../virtual-network/virtual-network-peering-overview.md) article.
17
15
18
-
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/vnet-vnet-diagram.png" alt-text="VNet to VNet diagram":::
16
+
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/vnet-vnet-diagram.png" alt-text="VNet to VNet diagram.":::
19
17
20
-
You can create this configuration using various tools, depending on the deployment model of your VNet. The steps in this article apply to the Azure [Resource Manager deployment model](../azure-resource-manager/management/deployment-models.md) and the Azure portal. To switch to a different deployment model or deployment method article, use the dropdown.
18
+
You can create this configuration using various tools, depending on the deployment model of your VNet. The steps in this article apply to the Azure [Resource Manager deployment model](../azure-resource-manager/management/deployment-models.md) and the Azure portal. To switch to a different deployment model or deployment method article, use the dropdown.
@@ -35,11 +33,12 @@ The following sections describe the different ways to connect virtual networks.
35
33
36
34
### VNet-to-VNet
37
35
38
-
Configuring a VNet-to-VNet connection is a simple way to connect VNets. When you connect a virtual network to another virtual network with a VNet-to-VNet connection type (VNet2VNet), it's similar to creating a Site-to-Site IPsec connection to an on-premises location. Both connection types use a VPN gateway to provide a secure tunnel with IPsec/IKE and function the same way when communicating. However, they differ in the way the local network gateway is configured.
36
+
Configuring a VNet-to-VNet connection is a simple way to connect VNets. When you connect a virtual network to another virtual network with a VNet-to-VNet connection type (VNet2VNet), it's similar to creating a Site-to-Site IPsec connection to an on-premises location. Both connection types use a VPN gateway to provide a secure tunnel with IPsec/IKE and function the same way when communicating. However, they differ in the way the local network gateway is configured.
37
+
38
+
When you create a VNet-to-VNet connection, the local network gateway address space is automatically created and populated. If you update the address space for one VNet, the other VNet automatically routes to the updated address space. It's typically faster and easier to create a VNet-to-VNet connection than a Site-to-Site connection. However, the local network gateway isn't visible in this configuration.
39
39
40
-
When you create a VNet-to-VNet connection, the local network gateway address space is automatically created and populated. If you update the address space for one VNet, the other VNet automatically routes to the updated address space. It's typically faster and easier to create a VNet-to-VNet connection than a Site-to-Site connection. However, the local network gateway is not visible in this configuration.
41
40
* If you know you want to specify additional address spaces for the local network gateway, or plan to add additional connections later and need to adjust the local network gateway, you should create the configuration using the Site-to-Site steps.
42
-
* The VNet-to-VNet connection does not include Point-to-Site client pool address space. If you need transitive routing for Point-to-Site clients, then create a Site-to-Site connection between the virtual network gateways, or use VNet peering.
41
+
* The VNet-to-VNet connection doesn't include Point-to-Site client pool address space. If you need transitive routing for Point-to-Site clients, then create a Site-to-Site connection between the virtual network gateways, or use VNet peering.
43
42
44
43
### Site-to-Site (IPsec)
45
44
@@ -48,6 +47,7 @@ If you're working with a complicated network configuration, you may prefer to co
48
47
### VNet peering
49
48
50
49
You can also connect your VNets by using VNet peering.
50
+
51
51
* VNet peering doesn't use a VPN gateway and has different constraints.
52
52
*[VNet peering pricing](https://azure.microsoft.com/pricing/details/virtual-network) is calculated differently than [VNet-to-VNet VPN Gateway pricing](https://azure.microsoft.com/pricing/details/vpn-gateway).
53
53
* For more information about VNet peering, see the [Virtual Network peering](../virtual-network/virtual-network-peering-overview.md) article.
@@ -160,17 +160,16 @@ After you've configured VNet1, create VNet4 and the VNet4 gateway by repeating t
160
160
161
161
## Configure the VNet1 gateway connection
162
162
163
-
When the virtual network gateways for both VNet1 and VNet4 have completed, you can create your virtual network gateway connections. In this section, you create a connection from VNet1 to VNet4. These steps work only for VNets in the same subscription. If your VNets are in different subscriptions, you must use [PowerShell](vpn-gateway-vnet-vnet-rm-ps.md) to make the connection. However, if your VNets are in different resource groups in the same subscription, you can connect them by using the portal.
163
+
When the virtual network gateways for both VNet1 and VNet4 have completed, you can create your virtual network gateway connections. In this section, you create a connection from VNet1 to VNet4. VNets in the same subscription can be connected using the portal, even if they are in different resource groups. However, if your VNets are in different subscriptions, you must use [PowerShell](vpn-gateway-vnet-vnet-rm-ps.md) to make the connections.
164
164
165
-
1. In the Azure portal, select **All resources**, enter *virtual network gateway* in the search box, and then navigate to the virtual network gateway for your VNet. For example, **VNet1GW**. Select the gateway to open the **Virtual network gateway** page.
166
-
1. On the gateway page, go to **Settings ->Connections**. Then, select**+Add**.
165
+
1. In the portal, go to your virtual network gateway. For example, **VNet1GW**.
166
+
1. On the virtual network gateway page, go to **Connections**. Select**+Add**.
167
167
168
-
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/connections.png" alt-text="Screenshot showing the connections page." border="false":::
169
-
1. The **Add connection** page opens.
168
+
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/connections-add.png" alt-text="Screenshot showing the connections page." lightbox="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/connections-add.png":::
170
169
171
-
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/vnet1-vnet4.png" alt-text="Screenshot showing the Add connection page.":::
170
+
1. On the **Add connection** page, fill in the connection values.
172
171
173
-
On the **Add connection** page, fill in the values for your connection:
172
+
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/add-connection.png" alt-text="Screenshot showing the Add Connection page." lightbox="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/add-connection.png":::
174
173
175
174
***Name**: Enter a name for your connection. For example, *VNet1toVNet4*.
176
175
@@ -180,7 +179,7 @@ When the virtual network gateways for both VNet1 and VNet4 have completed, you c
180
179
181
180
***Second virtual network gateway**: This field is the virtual network gateway of the VNet that you want to create a connection to. Select **Choose another virtual network gateway** to open the **Choose virtual network gateway** page.
182
181
183
-
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/choose.png" alt-text="Screenshot showing Choose a virtual network gateway page with another gateway selected.":::
182
+
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/choose-gateway.png" alt-text="Screenshot showing Choose a virtual network gateway page with another gateway selected."lightbox="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/choose-gateway.png":::
184
183
185
184
* View the virtual network gateways that are listed on this page. Notice that only virtual network gateways that are in your subscription are listed. If you want to connect to a virtual network gateway that isn't in your subscription, use the [PowerShell](vpn-gateway-vnet-vnet-rm-ps.md).
186
185
@@ -198,20 +197,18 @@ Next, create a connection from VNet4 to VNet1. In the portal, locate the virtual
198
197
1. Locate the virtual network gateway in the Azure portal.
199
198
1. On the **Virtual network gateway** page, select **Connections** to view the **Connections** page for the virtual network gateway. After the connection is established, you'll see the **Status** values change to **Connected**.
200
199
201
-
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/view-connections.png" alt-text="Screenshot showing the Connections page to verify the connections." border="false":::
200
+
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/view-connections.png" alt-text="Screenshot showing the Connections page to verify the connections." border="false" lightbox="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/view-connections.png":::
202
201
1. Under the **Name** column, select one of the connections to view more information. When data begins flowing, you'll see values for **Data in** and **Data out**.
203
202
204
-
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/status.png" alt-text="Screenshot shows a resource group with values for Data in and Data out" border="false":::
203
+
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/status.png" alt-text="Screenshot shows a resource group with values for Data in and Data out." border="false" lightbox="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/status.png":::
205
204
206
205
## Add additional connections
207
206
208
207
If you want to add additional connections, navigate to the virtual network gateway from which you want to create the connection, then select **Connections**. You can create another VNet-to-VNet connection, or create an IPsec Site-to-Site connection to an on-premises location. Be sure to adjust the **Connection type** to match the type of connection you want to create. Before you create additional connections, verify that the address space for your virtual network doesn't overlap with any of the address spaces you want to connect to. For steps to create a Site-to-Site connection, see [Create a Site-to-Site connection](./tutorial-site-to-site-portal.md).
209
208
210
209
## VNet-to-VNet FAQ
211
210
212
-
View the FAQ details for additional information about VNet-to-VNet connections.
0 commit comments