Validaciones recomendadas antes de migrar una máquina virtual local hacia Azure

Hi ANTHONY KELMAN MAMANI VARGAS & thx for join me at Q&A platform,

Before the final migration, I’d run an Azure Migrate assessment and resolve any Not ready or Ready with conditions findings first. For the VM itself, verify the OS/version is supported, the boot mode and disk layout are compatible, disk sizes are within Azure limits, and there are no unsupported dynamic disks, encryption settings, or dependencies that could prevent the replicated VM from booting.

For permissions, confirm that the migration identity has the required RBAC permissions on the target subscription/resource group, VNet and storage-related resources. Also validate connectivity from the migration appliance to Azure and from the future Azure VM to everything the workload needs, such as DNS, domain controllers, databases, application servers and external endpoints.

The rollback plan should be defined before cutover. Keep the on-premises VM unchanged until the Azure workload has been validated, document the point at which users or DNS will be switched, and define how traffic will be returned to the original VM if validation fails.

The minimum test I’d consider acceptable is an Azure Migrate Test migration into an isolated test VNet before the real migration. Boot the replicated VM, confirm Windows/Linux starts normally, validate network connectivity and DNS, log in, start the application and verify its critical dependencies. Then clean up the test migration and proceed with the final migration only after those checks succeed

rgds,

Alex