Skip to content

Commit a9b4db7

Browse files
committed
fix FAQ
1 parent 4c52563 commit a9b4db7

File tree

3 files changed

+12
-1
lines changed

3 files changed

+12
-1
lines changed

articles/expressroute/gateway-migration.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,8 +99,19 @@ You have up to 15 days to commit after migration preparation. Use this time to v
9999

100100
Azure Advisor will notify you if your gateway is eligible or requires migration. You can also check your ExpressRoute Gateway resource in the Azure portal—if your gateway is eligible, a banner at the top of the page will display the message "Implement Zone Redundant ExpressRoute Gateways."
101101

102-
:::image type="content" source="./media/gateway-migration/advisor.png" alt-text="Image showing Azure Advisor notification in overview of the gateway." lightbox="./media/expressroute-howto-linkvnet-portal-resource-manager/gateway-circuit.png":::
102+
:::image type="content" source="./media/gateway-migration/advisor.png" alt-text="Image showing Azure Advisor notification in overview of the gateway." lightbox="./media/gateway-migration/advisor-expansion.png":::
103+
104+
### How do I validate if my gateway is Zone Resilient after migration?
105+
106+
To confirm your gateway is zone resilient after migration:
107+
108+
- Check Azure Advisor: If your gateway is zone resilient, you will no longer see Advisor alerts recommending a zone-redundant gateway.
109+
- Verify resource tags: The migrated gateway will have a default tag labeled `GatewaySKUMigration`, indicating it has been moved to the zone-resilient deployment model.
110+
111+
These checks confirm that your gateway is now zone resilient.
112+
103113
### Can I roll back this change?
114+
104115
Yes, until it is committed. The migration is composed of four major steps:​
105116

106117
1. Validate – Confirms if your gateway is eligible for migration. ​
129 KB
Loading
290 KB
Loading

0 commit comments

Comments
 (0)