Hello Eva Calderón Gómez
According to the Microsoft document https://learn.microsoft.com/en-us/azure/vpn-gateway/basic-public-ip-migrate-about
The migration tool automatically creates a second virtual network gateway with:
Admin state = disabled
A new Standard SKU public IP
All existing connections copied over
This second gateway is not user-created—it is provisioned by the migration workflow itself.
The tool performs validation checks before proceeding. If prerequisites (like subnet size or available IPs) are not met, the migration will not proceed. The migration process is customer-initiated and incurs up to 10 minutes of downtime.
our question is: Is it possible to create this second virtual network gateway, public IP and connections in advance so the maintenance window for the migration is shorter? Would the migration tool detect this new VNG in order to proceed with the migration process?
No, it is not supported to manually pre-create the second VNG, public IP, and connections for the migration from a Basic SKU public IP to a Standard SKU. The Azure migration tool does not detect or use manually created resources for this process.
3.While you can't pre-create the second VNG, you can reduce downtime by:
- Ensuring the GatewaySubnet has at least three available IP addresses (recommended size: /27 or larger)
- Validating that all connections and configurations are healthy before initiating migration
- Scheduling the migration during a low-traffic window
https://learn.microsoft.com/en-us/azure/vpn-gateway/basic-public-ip-migrate-howto?web=1
I hope this helps! If these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.
If the above is unclear or you are unsure about something, please add a comment below.