Skip to content

Commit b55531b

Browse files
committed
Edit fix
1 parent 3789053 commit b55531b

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed
925 Bytes
Loading

articles/vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.author: cherylmc
1515

1616
This article helps you connect your virtual networks using the VNet-to-VNet connection type in the Azure portal. When you use the portal to connect virtual networks using VNet-to-VNet, the virtual networks can be in different regions, but must be in the same subscription. If your virtual networks are in different subscriptions, use the [PowerShell](vpn-gateway-vnet-vnet-rm-ps.md) instructions instead. This article doesn't apply to virtual network peering. For virtual network peering, see the [Virtual Network peering](../virtual-network/virtual-network-peering-overview.md) article.
1717

18-
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/vnet-vnet-diagram.png" alt-text="VNet to VNet diagram." lightbox="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/vnet-vnet-diagram.png":::
18+
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/vnet-vnet-diagram.png" alt-text="Diagram of a VNet-to-VNet connection." lightbox="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/vnet-vnet-diagram.png":::
1919

2020
## About VNet-to-VNet connections
2121

@@ -43,7 +43,7 @@ You might want to connect virtual networks by using a VNet-to-VNet connection fo
4343

4444
Within the same region, you can set up multi-tier applications with multiple virtual networks that are connected together because of isolation or administrative requirements. VNet-to-VNet communication can be combined with multi-site configurations. These configurations let you establish network topologies that combine cross-premises connectivity with inter-virtual network connectivity, as shown in the following diagram:
4545

46-
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/connections-diagram.png" alt-text="VNet connections diagram.":::
46+
:::image type="content" source="./media/vpn-gateway-howto-vnet-vnet-resource-manager-portal/connections-diagram.png" alt-text="Diagram of a VNet-to-VNet connection showing multiple subscriptions.":::
4747

4848
## Create and configure VNet1
4949

@@ -98,7 +98,7 @@ A gateway can take 45 minutes or more to fully create and deploy. You can see th
9898

9999
[!INCLUDE [NSG warning](../../includes/vpn-gateway-no-nsg-include.md)]
100100

101-
## Create and configure VNet4
101+
## Create and configure VNet4
102102

103103
After you've configured VNet1, create VNet4 and the VNet4 gateway by repeating the previous steps and replacing the values with VNet4 values. You don't need to wait until the virtual network gateway for VNet1 has finished creating before you configure VNet4. If you're using your own values, make sure the address spaces don't overlap with any of the virtual networks to which you want to connect.
104104

0 commit comments

Comments
 (0)