Skip to content

Commit 8250d1e

Browse files
Merge pull request #291602 from halkazwini/ez-er-ps
AEZ note
2 parents 9a7e9dc + 8a050db commit 8250d1e

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

articles/expressroute/expressroute-howto-add-gateway-resource-manager.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: expressroute
55
author: duongau
66
ms.service: azure-expressroute
77
ms.topic: how-to
8-
ms.date: 12/03/2024
8+
ms.date: 12/06/2024
99
ms.author: duau
1010
ms.custom: devx-track-azurepowershell
1111
---
@@ -128,6 +128,14 @@ The steps for this task use a VNet based on the values in the following configur
128128
New-AzVirtualNetworkGateway -Name $GWName -ResourceGroupName $RG -Location $Location -ExtendedLocation $ExtendedLocation -IpConfigurations $ipconf -GatewayType Expressroute -GatewaySku Standard
129129
```
130130

131+
> [!NOTE]
132+
> To create the gateway in an [Azure Extended Zone](../extended-zones/overview.md), you must first [request access to the Extended Zone](../extended-zones/request-access.md). Once you have access, you can create the gateway.
133+
>
134+
> The following considerations apply when creating a virtual network gateway in an Extended Zone:
135+
> - Availability Zones aren't supported in Azure Extended Zones.
136+
> - The following SKUs are currently supported in Azure Extended Zones: *Standard*, *HighPerformance*, *UltraPerformance*.
137+
> - Local SKU circuit isn't supported with gateways in Azure Extended Zone.
138+
131139
## Verify the gateway was created
132140

133141
Use the following commands to verify that the gateway has been created:

0 commit comments

Comments
 (0)