How do we automate the migration of legacy VM workloads to Azure using Azure Migrate tools?

All answers to this question.

Migrating legacy systems is a delicate pillar of Cloud Computing (AWS/Azure/GCP) adoption. For Azure Migrate, the agentless approach is excellent but requires high-speed connectivity to handle the initial replication. Regarding IP consistency, you must set up a Site-to-Site VPN or ExpressRoute and stretch your Layer 2 network if you absolutely cannot change IPs. However, I usually recommend updating DNS records instead, as stretching L2 can introduce "tromboning" latency. Make sure to run the assessment tool first to identify any incompatible virtual hardware before you start the sync.

   Answered 2025-11-08 by Melissa Price

Do you have a plan for the "re-platforming" of the applications once they are in the cloud, or is this strictly a "lift-and-shift" operation to get out of the DC?

   Answered 2025-11-10 by Daniel Scott

• Daniel, it's a lift-and-shift initially. We need to clear the physical space by Q3. Once the VMs are stabilized in Azure, we plan to move the web tier to App Services and the databases to Azure SQL. This "move first, optimize later" strategy is helping us meet our aggressive timeline while minimizing the risk of downtime during the actual physical move of the server racks.

     Commented 2025-11-12 by George Harris

Don't forget to check your licensing! Moving Windows Server to Azure is often cheaper if you leverage the Azure Hybrid Benefit with your existing licenses.

   Answered 2025-11-13 by Helen Carter

• That’s a smart move, Helen. Leveraging those existing licenses can save up to 40% on the operational costs of the new virtual machines in the cloud.

     Commented 2025-11-14 by Donna Campbell