Merge pull request #299057 from MekaylaMoore/patch-29

Update gateway-migration.md

Author: prmerger-automator[bot]

articles/expressroute/gateway-migration.md

@@ -79,6 +79,8 @@ The guided gateway migration experience has the following limitations:
 - 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).
 - ExpressRoute Gateways that were established or connected to circuits in 2017 or earlier.
+- ExpressRoute Gateways with the SKU named "default" are not supported for migration.
+
 ## Common Validation Errors
 
 During the gateway migration process, it's essential to validate whether your resources are ready for migration. Below are some common validation errors you can encounter: