In this phase, you or your IT team updates your DNS with records that map the FQDNs that you specified in the Schedule Migration UI to the appropriate IP addresses.
Same as for a greenfield Horizon Edge deployment, you are responsible for creating the DNS records. The self-service migration cannot perform that update on your behalf.
As described in the page about Migration Phase 5, the IP addresses are typically allocated and visible in your Microsoft Azure subscription within 48 hours of your scheduling the migration.
Typically those instances are up and running within 48 hours from the time you saved the migration schedule using the Schedule Migration UI.
Even though the DNS records that map the IP addresses to their FQDNs can be done at a later date, it is a best practice to create those records as soon as the IP addresses are assigned to the instances.
The reason for putting the mapping into place sooner than later is because lack of the records that map your chosen FQDNs to the instances' underlying IP address will prevent your next-gen environment from being fully functional for the post-migration validation steps.
For the details about which IP addresses need to be mapped to the FQDNs, see the page Configure Required DNS Records After Deploying Horizon Edge Gateway and Unified Access Gateway in the next-gen documentation.
In the Horizon Universal Console, the FQDNs and relevant load balancer IPs are displayed in the Horizon Edge's details page. You can drill-down to the Horizon Edge's details from the console's Capacity page ().
Next Steps
When the starting time for the scheduled migration maintenance window arrives, the system begins the remaining migration activities.
In this migration documentation, continue reading with Phase 7 - During the Migration Maintenance Window.
