Skip to content

Commit 6d8bb80

Browse files
authored
Update expressroute-about-virtual-network-gateways.md
upgrade scenario- revision
1 parent cf64e4d commit 6d8bb80

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/expressroute/expressroute-about-virtual-network-gateways.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -30,12 +30,11 @@ Each virtual network can have only one virtual network gateway per gateway type.
3030

3131
[!INCLUDE [expressroute-gwsku-include](../../includes/expressroute-gwsku-include.md)]
3232

33-
If you want to upgrade your gateway to a higher-capacity gateway SKU, you can use the [Gateway Migration tool](expressroute-about-virtual-network-gateways.md) in either the Azure portal or PowerShell. The following upgrades are supported:
33+
You can upgrade your gateway to a higher-capacity SKU within the same SKU family, that is Non-Az-enabled or Az-enabled gateway.
3434

35-
* Non-Az-enabled SKU on Basic IP to Non-Az-enabled SKU on Standard IP
36-
* Non-Az-enabled SKU on Basic IP to Az-enabled SKU on Standard IP
37-
38-
For more information, see [Migrate to an availability zone-enabled gateway](expressroute-howto-gateway-migration-powershell.md).
35+
For example, you can upgrade:
36+
* From one Non-Az-enabled SKU to another Non-Az-enabled SKU
37+
* From one Az-enabled SKU to another Az-enabled SKU
3938

4039
For all other downgrade scenarios, you need to delete and re-create the gateway, which incurs downtime.
4140

0 commit comments

Comments
 (0)