We have a few Cloud Service (classic) deployments (each in a separate subscription) that need to be migrated to ARM Cloud Service (extended support) deployments. These were all originally deployed before 2017 and do not have a virtual network. Additionally, these were created before the ability to reserve an IP address, though we have been able to maintain the same IP address for each of these when deploying updates from within Visual Studio.
If we first use the PowerShell commands to reserve the IP address for each deployment, is it then possible to migrate them to Cloud Services (extended support) and retain the IP address throughout the process by using either the migration tool within the Azure portal or by using PowerShell commands, given that they are not within a virtual network?
A similar question was asked here:
https://video2.skills-academy.com/en-us/answers/questions/962562/how-to-migrate-azure-cloud-service-(classic)-to-az
However, the accepted answer and comments in that discussion seem to be worded in a way that makes it unclear as to what is supported in the migration tool within the Azure portal versus what is supported in PowerShell.