Skip to content

Commit 2bc611f

Browse files
authored
Merge pull request #184945 from cherylmc/retire
update
2 parents c523050 + bcc6a49 commit 2bc611f

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

articles/vpn-gateway/vpn-gateway-about-vpngateways.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: cherylmc
66
# Customer intent: As someone with a basic network background, but is new to Azure, I want to understand the capabilities of Azure VPN Gateway so that I can securely connect to my Azure virtual networks.
77
ms.service: vpn-gateway
88
ms.topic: overview
9-
ms.date: 07/08/2021
9+
ms.date: 01/12/2022
1010
ms.author: cherylmc
1111
ms.custom: contperf-fy21q1, e2e-hybrid
1212
---
@@ -29,13 +29,17 @@ When you create a VPN gateway, gateway VMs are deployed to the gateway subnet an
2929

3030
A VPN gateway connection relies on multiple resources that are configured with specific settings. Most of the resources can be configured separately, although some resources must be configured in a certain order.
3131

32-
### <a name="diagrams"></a>Design
32+
### <a name="connectivity"></a> Connectivity
3333

34-
It's important to know that there are different configurations available for VPN gateway connections. You need to determine which configuration best fits your needs. For example, Point-to-Site, Site-to-Site, and coexisting ExpressRoute/Site-to-Site connections all have different instructions and configuration requirements. For information about design and to view connection topology diagrams, see [Design](design.md).
34+
Because you can create multiple connection configurations using VPN Gateway, you need to determine which configuration best fits your needs. Point-to-Site, Site-to-Site, and coexisting ExpressRoute/Site-to-Site connections all have different instructions and configuration requirements. For connection diagrams and corresponding links to configuration steps, see [VPN Gateway design](design.md).
35+
36+
* [Site-to-Site VPN connections](design.md#s2smulti)
37+
* [Point-to-Site VPN connections](design.md#P2S)
38+
* [VNet-to-VNet VPN connections](design.md#V2V)
3539

3640
### <a name="planningtable"></a>Planning table
3741

38-
The following table can help you decide the best connectivity option for your solution.
42+
The following table can help you decide the best connectivity option for your solution. Note that ExpressRoute is not a part of VPN Gateway, but is included in the table.
3943

4044
[!INCLUDE [cross-premises](../../includes/vpn-gateway-cross-premises-include.md)]
4145

@@ -60,7 +64,7 @@ When you create a virtual network gateway, you specify the gateway SKU that you
6064

6165
## <a name="availability"></a>Availability Zones
6266

63-
VPN gateways can be deployed in Azure Availability Zones. This brings resiliency, scalability, and higher availability to virtual network gateways. Deploying gateways in Azure Availability Zones physically and logically separates gateways within a region, while protecting your on-premises network connectivity to Azure from zone-level failures. see [About zone-redundant virtual network gateways in Azure Availability Zones](about-zone-redundant-vnet-gateways.md).
67+
VPN gateways can be deployed in Azure Availability Zones. This brings resiliency, scalability, and higher availability to virtual network gateways. Deploying gateways in Azure Availability Zones physically and logically separates gateways within a region, while protecting your on-premises network connectivity to Azure from zone-level failures. See [About zone-redundant virtual network gateways in Azure Availability Zones](about-zone-redundant-vnet-gateways.md).
6468

6569
## <a name="pricing"></a>Pricing
6670

0 commit comments

Comments
 (0)