Skip to content

Commit 9470837

Browse files
committed
Update links screenshots
1 parent 79b9cd4 commit 9470837

File tree

5 files changed

+53
-52
lines changed

5 files changed

+53
-52
lines changed
Lines changed: 53 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,58 @@
11
---
2-
title: 'Create a zone-redundant virtual network gateway in Azure Availability Zones'
3-
description: Learn how to deploy zone-redundant VPN Gateways and ExpressRoute gateways in Azure Availability Zones.
2+
title: 'Create a zone-redundant virtual network gateway in Azure availability zones'
3+
description: Learn how to deploy zone-redundant VPN Gateways and ExpressRoute gateways in Azure availability zones.
44
titleSuffix: Azure VPN Gateway
55
author: cherylmc
66
ms.service: vpn-gateway
77
ms.topic: how-to
8-
ms.date: 09/03/2020
8+
ms.date: 03/15/2024
99
ms.author: cherylmc
1010
ms.custom: devx-track-azurepowershell
1111

1212
---
13-
# Create a zone-redundant virtual network gateway in Azure Availability Zones
13+
# Create a zone-redundant virtual network gateway in availability zones
1414

15-
You can deploy VPN and ExpressRoute gateways 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. For information, see [About zone-redundant virtual network gateways](about-zone-redundant-vnet-gateways.md) and [About Azure Availability Zones](../availability-zones/az-overview.md).
15+
You can deploy VPN and ExpressRoute gateways in Azure availability zones. This brings resiliency, scalability, and higher availability to virtual network gateways. Deploying gateways in availability zones physically and logically separates gateways within a region, while protecting your on-premises network connectivity to Azure from zone-level failures. For more information, see [About zone-redundant virtual network gateways](about-zone-redundant-vnet-gateways.md), [What are availability zones?](../reliability/availability-zones-overview.md), and [Availability zone service and regional support](../reliability/availability-zones-service-support.md).
1616

17-
## Before you begin
17+
## Azure portal workflow
18+
19+
This section outlines the basic workflow to specify a zone-redundant gateway for an Azure VPN gateway.
20+
21+
### VPN Gateway
22+
23+
Create a virtual network and configure a virtual network gateway using these steps: [Create a VPN gateway](tutorial-create-gateway-portal.md#VNetGateway). When creating the gateway, configure the appropriate SKU and availability zone settings.
24+
25+
* **SKU**: Select an "AZ" SKU from the dropdown. For example, **VpnGw2AZ**. If you don't select an AZ SKU, you can't configure an availability zone setting.
26+
27+
:::image type="content" source="./media/create-zone-redundant-vnet-gateway/vpn-gateway.png" alt-text="Screenshot shows the VPN Gateway SKU selection to select an availability zone SKU." lightbox="./media/create-zone-redundant-vnet-gateway/vpn-gateway.png":::
28+
29+
* **Availability zone**: Select the Availability zone from the dropdown.
30+
31+
:::image type="content" source="./media/create-zone-redundant-vnet-gateway/zone.png" alt-text="Screenshot shows the availability zone dropdown to select an availability zone." lightbox="./media/create-zone-redundant-vnet-gateway/zone.png":::
32+
33+
### ExpressRoute
34+
35+
For an ExpressRoute gateway, follow the [ExpressRoute documentation](../expressroute/configure-expressroute-private-peering.md), selecting the proper [ExpressRoute gateway zone-redundant SKU](../expressroute/expressroute-about-virtual-network-gateways.md#gwsku).
36+
37+
* **SKU**: Select an "AZ" SKU from the dropdown. For example, **ErGw2AZ**. If you don't select an AZ SKU, you can't configure an availability zone setting.
38+
39+
:::image type="content" source="./media/create-zone-redundant-vnet-gateway/expressroute.png" alt-text="Screenshot shows the SKU selection to select an availability zone SKU." lightbox="./media/create-zone-redundant-vnet-gateway/expressroute.png":::
40+
* **Availability zone**: Select the Availability zone from the dropdown.
41+
42+
:::image type="content" source="./media/create-zone-redundant-vnet-gateway/expressroute-zone.png" alt-text="Screenshot shows the availability zone selection to select an availability zone." lightbox="./media/create-zone-redundant-vnet-gateway/expressroute-zone.png":::
43+
44+
## PowerShell workflow
1845

1946
[!INCLUDE [powershell](../../includes/vpn-gateway-cloud-shell-powershell-about.md)]
2047

21-
## <a name="variables"></a>1. Declare your variables
48+
### <a name="variables"></a>1. Declare your variables
2249

23-
Declare the variables that you want to use. Use the following sample, substituting the values for your own when necessary. If you close your PowerShell/Cloud Shell session at any point during the exercise, just copy and paste the values again to re-declare the variables. When specifying location, verify that the region you specify is supported. For more information, see the [FAQ](#faq).
50+
Declare the variables that you want to use. Use the following sample, substituting the values for your own when necessary. If you close your PowerShell/Cloud Shell session at any point during the exercise, just copy and paste the values again to redeclare the variables. When specifying location, verify that the region you specify is supported. For more information, see [Availability zone service and regional support](../reliability/availability-zones-service-support.md).
2451

2552
```azurepowershell-interactive
2653
$RG1 = "TestRG1"
2754
$VNet1 = "VNet1"
28-
$Location1 = "CentralUS"
55+
$Location1 = "EastUS"
2956
$FESubnet1 = "FrontEnd"
3057
$BESubnet1 = "Backend"
3158
$GwSubnet1 = "GatewaySubnet"
@@ -38,7 +65,7 @@ $GwIP1 = "VNet1GWIP"
3865
$GwIPConf1 = "gwipconf1"
3966
```
4067

41-
## <a name="configure"></a>2. Create the virtual network
68+
### <a name="configure"></a>2. Create the virtual network
4269

4370
Create a resource group.
4471

@@ -54,7 +81,7 @@ $besub1 = New-AzVirtualNetworkSubnetConfig -Name $BESubnet1 -AddressPrefix $BEPr
5481
$vnet = New-AzVirtualNetwork -Name $VNet1 -ResourceGroupName $RG1 -Location $Location1 -AddressPrefix $VNet1Prefix -Subnet $fesub1,$besub1
5582
```
5683

57-
## <a name="gwsub"></a>3. Add the gateway subnet
84+
### <a name="gwsub"></a>3. Add the gateway subnet
5885

5986
The gateway subnet contains the reserved IP addresses that the virtual network gateway services use. Use the following examples to add and set a gateway subnet:
6087

@@ -70,75 +97,49 @@ Set the gateway subnet configuration for the virtual network.
7097
```azurepowershell-interactive
7198
$getvnet | Set-AzVirtualNetwork
7299
```
73-
## <a name="publicip"></a>4. Request a public IP address
74-
100+
101+
### <a name="publicip"></a>4. Request a public IP address
102+
75103
In this step, choose the instructions that apply to the gateway that you want to create. The selection of zones for deploying the gateways depends on the zones specified for the public IP address.
76104

77-
### <a name="ipzoneredundant"></a>For zone-redundant gateways
105+
#### <a name="ipzoneredundant"></a>For zone-redundant gateways
78106

79-
Request a public IP address with a **Standard** PublicIpaddress SKU and do not specify any zone. In this case, the Standard public IP address created will be a zone-redundant public IP.
107+
Request a public IP address with a **Standard** PublicIpaddress SKU and don't specify any zone. In this case, the Standard public IP address created is a zone-redundant public IP.
80108

81109
```azurepowershell-interactive
82110
$pip1 = New-AzPublicIpAddress -ResourceGroup $RG1 -Location $Location1 -Name $GwIP1 -AllocationMethod Static -Sku Standard
83111
```
84112

85-
### <a name="ipzonalgw"></a>For zonal gateways
113+
#### <a name="ipzonalgw"></a>For zonal gateways
86114

87-
Request a public IP address with a **Standard** PublicIpaddress SKU. Specify the zone (1, 2 or 3). All gateway instances will be deployed in this zone.
115+
Request a public IP address with a **Standard** PublicIpaddress SKU. Specify the zone (1, 2 or 3). All gateway instances are deployed in this zone.
88116

89117
```azurepowershell-interactive
90118
$pip1 = New-AzPublicIpAddress -ResourceGroup $RG1 -Location $Location1 -Name $GwIP1 -AllocationMethod Static -Sku Standard -Zone 1
91119
```
92120

93-
### <a name="ipregionalgw"></a>For regional gateways
94-
95-
Request a public IP address with a **Basic** PublicIpaddress SKU. In this case, the gateway is deployed as a regional gateway and does not have any zone-redundancy built into the gateway. The gateway instances are created in any zones, respectively.
96-
97-
```azurepowershell-interactive
98-
$pip1 = New-AzPublicIpAddress -ResourceGroup $RG1 -Location $Location1 -Name $GwIP1 -AllocationMethod Dynamic -Sku Basic
99-
```
100-
## <a name="gwipconfig"></a>5. Create the IP configuration
121+
### <a name="gwipconfig"></a>5. Create the IP configuration
101122

102123
```azurepowershell-interactive
103124
$getvnet = Get-AzVirtualNetwork -ResourceGroupName $RG1 -Name $VNet1
104125
$subnet = Get-AzVirtualNetworkSubnetConfig -Name $GwSubnet1 -VirtualNetwork $getvnet
105126
$gwipconf1 = New-AzVirtualNetworkGatewayIpConfig -Name $GwIPConf1 -Subnet $subnet -PublicIpAddress $pip1
106127
```
107128

108-
## <a name="gwconfig"></a>6. Create the gateway
129+
### <a name="gwconfig"></a>6. Create the virtual network gateway
109130

110-
Create the virtual network gateway.
111-
112-
### For ExpressRoute
131+
**VPN Gateway example**
113132

114133
```azurepowershell-interactive
115-
New-AzVirtualNetworkGateway -ResourceGroup $RG1 -Location $Location1 -Name $Gw1 -IpConfigurations $GwIPConf1 -GatewayType ExpressRoute -GatewaySku ErGw1AZ
134+
New-AzVirtualNetworkGateway -ResourceGroup $RG1 -Location $Location1 -Name $Gw1 -IpConfigurations $GwIPConf1 -GatewayType Vpn -VpnType RouteBased -GatewaySku VpnGw2AZ
116135
```
117136

118-
### For VPN Gateway
137+
**ExpressRoute example**
119138

120139
```azurepowershell-interactive
121-
New-AzVirtualNetworkGateway -ResourceGroup $RG1 -Location $Location1 -Name $Gw1 -IpConfigurations $GwIPConf1 -GatewayType Vpn -VpnType RouteBased -GatewaySku VpnGw1AZ
140+
New-AzVirtualNetworkGateway -ResourceGroup $RG1 -Location $Location1 -Name $Gw1 -IpConfigurations $GwIPConf1 -GatewayType ExpressRoute -GatewaySku ErGw2AZ
122141
```
123142

124-
## <a name="faq"></a>FAQ
125-
126-
### What will change when I deploy these new SKUs?
127-
128-
From your perspective, you can deploy your gateways with zone-redundancy. This means that all instances of the gateways will be deployed across Azure Availability Zones, and each Availability Zone is a different fault and update domain. This makes your gateways more reliable, available, and resilient to zone failures.
129-
130-
### Can I use the Azure portal?
131-
132-
Yes, you can use the Azure portal to deploy the new SKUs. However, you will see these new SKUs only in those Azure regions that have Azure Availability Zones.
133-
134-
### What regions are available for me to use the new SKUs?
135-
136-
See [Availability Zones](../availability-zones/az-region.md) for the latest list of available regions.
137-
138-
### Can I change/migrate/upgrade my existing virtual network gateways to zone-redundant or zonal gateways?
139-
140-
Migrating your existing virtual network gateways to zone-redundant or zonal gateways is currently not supported. You can, however, delete your existing gateway and re-create a zone-redundant or zonal gateway.
141-
142-
### Can I deploy both VPN and Express Route gateways in same virtual network?
143+
## Next steps
143144

144-
Co-existence of both VPN and Express Route gateways in the same virtual network is supported. However, you should reserve a /27 IP address range for the gateway subnet.
145+
See the [VPN Gateway](index.yml) and [ExpressRoute](../expressroute/index.yml) pages for other configuration information.
16.4 KB
Loading
64.8 KB
Loading
57.8 KB
Loading
33.7 KB
Loading

0 commit comments

Comments
 (0)