Merge pull request #299608 from MekaylaMoore/gwerror

Gwerror

Author: prmerger-automator[bot]

articles/expressroute/gateway-migration-error-messaging.md

@@ -19,8 +19,9 @@ Follow these best practices to minimize errors during the gateway migration proc
 
 * **Maintain resource health**: Ensure all resources remain in a **succeeded** state throughout the migration. Avoid running updates on related resources during the process.
 * **Avoid property updates**: Refrain from updating properties like **FastPath**, **route weight**, or **traffic toggles** for connections and gateways, as these updates can cause resource failures.
-* **Sequential circuit migration**: Migrate gateways connected to the same circuit one at a time. Parallel migrations on the same circuit aren't supported.
-* **Avoid manual connection changes**: Don't manually create or delete connections for gateways actively carrying traffic (admin state enabled) during migration.
+* **Sequential gateway migration**: Migrate gateways connected to the same circuit one at a time. Parallel migrations on the same circuit aren't supported.
+* **Avoid manual changes**: Refrain from manually creating, deleting, updating, or resetting gateways or their connections while they are actively carrying traffic (admin state enabled) during the migration process.
+
 * **Check for maintenance**: Avoid creating connections to gateways undergoing maintenance, as this operation fails. Any failed connections must be deleted before retrying.
 
 By adhering to these practices, you can reduce the likelihood of encountering errors during migration.

articles/expressroute/gateway-migration.md

@@ -74,6 +74,8 @@ For enhanced reliability and high availability, we recommend migrating to an Az-
 
 The guided gateway migration experience has the following limitations:
 
+- The migration tool is exclusively designed for ExpressRoute virtual network gateways. It does not support migration for VPN gateways or other gateway types.
+- The migration tool only supports gateway migration within the same virtual network. It does not allow migration across different subscriptions, regions, or gateway types such as VPN gateways.
 - Downgrade scenarios, such as migrating from an Az-enabled SKU to a non-Az-enabled SKU, aren't supported.
 - The GatewaySubnet must have a prefix of /27 or longer to proceed with the migration.
 - Private endpoints (PEs) in the virtual network connected through ExpressRoute private peering can experience connectivity issues during migration. For guidance on mitigating these issues, see [Private endpoint connectivity](expressroute-about-virtual-network-gateways.md#private-endpoint-connectivity-and-planned-maintenance-events).