What happens if already discovered VM is moved to another vCenter

[Lars Villaume Jørgensen]

Hello, 

In an Azure Migrate project with VMWare Azure Migrate discovery appliance, what would happen if a VM that is already discovered via a vCenter, if the VM is then moved to a new vCenter instance that is added as a discovery source to the same Azure Migrate project and same VMWare appliance - whould it been seen as the same VM i.e. it would not cause problems to migrate VMs from one vCenter to a new vCenter during the discovery and assessment period?

[#2]

https://docs.microsoft.com/en-us/azure/migrate/scale-vmware-assessment#planning-limits

You can analyze dependencies on servers across vCenter Servers discovered from the same appliance.

Ensure there is no overlap among the servers on the vCenter accounts provided. A discovery with such an overlap is an unsupported scenario. If a server is discovered by more than one appliance, this results in a duplicate in discovery and in issues while enabling replication for the server using the Azure portal in Server Migration.

[#3]

Thanks for your reply Tommy.
The scenario here is a little different.
Although the appliance is configured with two vCenters connections which is supported, I can't see from the documentation what will happen if a VM is first discovered in the first vCenter but later as it is moved to the second vCenter, it is now discovered here. My concern is that it will cause duplicate objects in the Azure Migrate project.

[#4]

I am not sure to be honest, but I believe that if you have only one Appliance connected to more than one vcenter it will work :) please aks MS via Azrue Support Request to be sure