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/about-zone-redundant-vnet-gateways.md
+14-9Lines changed: 14 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ titleSuffix: Azure VPN Gateway
5
5
author: cherylmc
6
6
ms.service: vpn-gateway
7
7
ms.topic: how-to
8
-
ms.date: 09/03/2020
8
+
ms.date: 12/04/2023
9
9
ms.author: cherylmc
10
10
---
11
11
# About zone-redundant virtual network gateway in Azure availability zones
@@ -38,22 +38,27 @@ For information about gateway SKUs, see [VPN gateway SKUs](vpn-gateway-about-vpn
38
38
39
39
## <aname="pipskus"></a>Public IP SKUs
40
40
41
-
Zone-redundant gateways and zonal gateways both rely on the Azure public IP resource *Standard* SKU. The configuration of the Azure public IP resource determines whether the gateway that you deploy is zone-redundant, or zonal. If you create a public IP resource with a *Basic* SKU, the gateway won't have any zone redundancy, and the gateway resources will be regional.
41
+
Zone-redundant, zonal and non-zonal gateways rely on the configuration of *Standard* SKU of Azure public IP resource. If you create a public IP resource with a *Basic* SKU, the gateway won't have any zone redundancy, and the gateway resources are regional.
42
+
43
+
For more information, see [Availability zones](../virtual-network/ip-services/public-ip-addresses.md#availability-zone).
42
44
43
45
### <aname="pipzrg"></a>Zone-redundant gateways
44
46
45
-
When you create a public IP address using the **Standard** public IP SKU without specifying a zone, the behavior differs depending on whether the gateway is a VPN gateway, or an ExpressRoute gateway.
47
+
When you create a public IP address using the **Standard** public IP SKU with zone-redundant option, the behavior differs depending on whether the gateway is a VPN gateway, or an ExpressRoute gateway.
46
48
47
-
* For a VPN gateway, the two gateway instances will be deployed in any 2 out of these three zones to provide zone-redundancy.
49
+
* For a VPN gateway, the two gateway instances are deployed in any two out of these three zones to provide zone-redundancy.
48
50
* For an ExpressRoute gateway, since there can be more than two instances, the gateway can span across all the three zones.
49
51
50
52
### <aname="pipzg"></a>Zonal gateways
51
53
52
-
When you create a public IP address using the **Standard** public IP SKU and specify the Zone (1, 2, or 3), all the gateway instances will be deployed in the same zone.
54
+
When you create a public IP address using the **Standard** public IP SKU and specify the Zone (1, 2, or 3), all the gateway instances are deployed in the same zone.
55
+
56
+
### <aname="piprg"></a>Non-zonal or regional gateways
53
57
54
-
### <aname="piprg"></a>Regional gateways
58
+
A non-zonal or regional gateway doesn't have zone-redundancy. These gateways are created in the following scenarios:
55
59
56
-
When you create a public IP address using the **Basic** public IP SKU, the gateway is deployed as a regional gateway and doesn't have any zone-redundancy built into the gateway.
60
+
* When you create a public IP address using the **Standard** public IP SKU with the "No Zone" option
61
+
* When you create a public IP address using the **Basic** public IP SKU
57
62
58
63
## <aname="faq"></a>FAQ
59
64
@@ -63,7 +68,7 @@ From your perspective, you can deploy your gateways with zone-redundancy. This m
63
68
64
69
### Can I use the Azure portal?
65
70
66
-
Yes, you can use the Azure portal to deploy these SKUs. However, you'll see these SKUs only in those Azure regions that have Azure availability zones.
71
+
Yes, you can use the Azure portal to deploy these SKUs. However, you see these SKUs only in those Azure regions that have Azure availability zones.
67
72
68
73
### What regions are available for me to use these SKUs?
69
74
@@ -75,7 +80,7 @@ Migrating your existing virtual network gateways to zone-redundant or zonal gate
75
80
76
81
### Can I deploy both VPN and ExpressRoute gateways in same virtual network?
77
82
78
-
Co-existence of both VPN and ExpressRoute gateways in the same virtual network is supported. However, you should reserve a /27 IP address range for the gateway subnet.
83
+
Coexistence of both VPN and ExpressRoute gateways in the same virtual network is supported. However, you should reserve a /27 IP address range for the gateway subnet.
0 commit comments