Skip to content

Commit fbb458c

Browse files
Merge pull request #295236 from MekaylaMoore/patch-17
Update gateway-migration.md
2 parents c05f98c + 8fcea32 commit fbb458c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/expressroute/gateway-migration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: About migrating to an availability zone-enabled ExpressRoute virtual network gateway
33
titleSuffix: Azure ExpressRoute
4-
description: This article explains how to seamlessly migrate from Standard/HighPerf/UltraPerf SKUs to ErGw1/2/3AZ SKUs.
4+
description: This article explains how to migrate from Standard/HighPerf/UltraPerf SKUs to ErGw1/2/3AZ SKUs.
55
services: expressroute
66
author: duongau
77
ms.service: azure-expressroute
@@ -37,7 +37,7 @@ For enhanced reliability, it's recommended to use an Availability-Zone Enabled v
3737

3838
Historically, users had to use the Resize-AzVirtualNetworkGateway PowerShell command or delete and recreate the virtual network gateway to migrate between SKUs.
3939

40-
With the guided gateway migration experience you can deploy a second virtual network gateway in the same GatewaySubnet and Azure automatically transfers the control plane and data path configuration from the old gateway to the new one. During the migration process, there will be two virtual network gateways in operation within the same GatewaySubnet. This feature is designed to support migrations without downtime. However, users may experience brief connectivity issues or interruptions during the migration process.
40+
With the guided gateway migration experience you can deploy a second virtual network gateway in the same GatewaySubnet and Azure automatically transfers the control plane and data path configuration from the old gateway to the new one. During the migration process, there will be two virtual network gateways in operation within the same GatewaySubnet. This feature is designed to support migrations without disruption. However, users may experience brief connectivity issues or interruptions during the migration process.
4141

4242
> [!NOTE]
4343
> The total time required for the migration to complete can take up to one hour. During this period, the gateway will remain locked, and no changes will be permitted.

0 commit comments

Comments
 (0)