Skip to content

Commit 8a6ccd2

Browse files
Merge pull request #304176 from MekaylaMoore/portalupdate
fix image for prepare
2 parents a0697a9 + 5ba6c40 commit 8a6ccd2

File tree

3 files changed

+7
-2
lines changed

3 files changed

+7
-2
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,3 +142,5 @@ To learn how to link your virtual network to an ExpressRoute circuit, advance to
142142

143143
> [!div class="nextstepaction"]
144144
> [Link a Virtual Network to an ExpressRoute circuit](expressroute-howto-linkvnet-portal-resource-manager.md)
145+
146+

articles/expressroute/expressroute-howto-gateway-migration-portal.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,13 +37,13 @@ Follow these steps to migrate to a new gateway using the Azure portal:
3737

3838
1. After successful validation, move to the **Prepare** stage. At this point, a new virtual network gateway will be created, and its Public IP address will be provisioned and managed by Microsoft. In the **Virtual Network Gateway Details** section, enter the following information:
3939
1.
40-
:::image type="content" source="media/gateway-migration/gateway-prepare-update.png" alt-text="Screenshot of the Prepare stage for migrating a virtual network gateway." lightbox="media/gateway-migration/gateway-prepare-stage.png":::
40+
:::image type="content" source="media/gateway-migration/gateway-prepare-update.png" alt-text="Screenshot of the Prepare stage for migrating a virtual network gateway." lightbox="media/gateway-migration/gateway-prepare-update.png":::
4141

4242
| Setting | value |
4343
|--|--|
4444
| **Gateway name** | Enter a name for the new gateway. |
4545
| **Gateway SKU** | Select the SKU for the new gateway. |
46-
| **Public IP address** | Select **Add new**, provide a name for the new public IP, choose an availability zone, and select **OK**. |
46+
4747

4848
> [!NOTE]
4949
> During this process, your existing virtual network gateway is locked, preventing the creation or modification of connections.

articles/expressroute/gateway-migration.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,8 +130,11 @@ During the migration process, traffic is rerouted seamlessly. There is no expect
130130
### What should I do if the Prepare step fails due to a cross-region connection on a Basic SKU circuit during gateway migration?
131131

132132
If the Prepare step fails because your Basic SKU circuit has a cross-region connection, **abort** the gateway migration and **upgrade** the circuit SKU before trying again. This configuration is unsupported, and migration will continue to fail until the circuit SKU is upgraded.
133+
133134
## Next Steps
134135

135136
- Troubleshoot migration issues with [Troubleshooting Gateway Migration](gateway-migration-error-messaging.md).
136137
- Learn how to [migrate using the Azure portal](expressroute-howto-gateway-migration-portal.md).
137138
- Learn how to [migrate using PowerShell](expressroute-howto-gateway-migration-powershell.md).
139+
140+

0 commit comments

Comments
 (0)