Forum Discussion
Azure Migration without VM Shutdown
You may consider creating a new DC in Azure and decommission the current on-prem one once the migration completed
Kidd_Ip hello,
As a preparation and prerequisites a new DC will be created in Azure therefore it will be a vnet with address space and it will have the same subnet as on-prem to keep same IPs for the VMs.
But between on-prem and Azure we have an expressroute or vpn so we will have overlapping. How we can prevent this since both they will be run in parallel? I am curious to know if there is a possible solution. Thanks in advance- Did you find a resolution for this as I agree that with the expressroute active during Azure Migrate processing, the two (2) DCs would "see and talk" to each other. And with the IPs and FSMO roles likely conflicting, lots wrong can happen. I migrated my DC to Azure but had to leave the original DC active on-prem for a variety of reasons. And now that I need to migrate a few remaining VMs from on-prem to Azure, I'm concerned that the expressroute that's active during Azure Migrate will cause the two DCs with the same name, IP address and FSMO roles to "see" each other.
Ken_Shep hello,
i was asking actually in this community to see if someone has a solution or a workaround. But i have found a microsoft documentation: https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/azure-extended-network
But i think the better is to change the IPs and play with DNS pointing if needed. I was thinking also you could use nat but both workarounds are tough.
