Let's go back to replicating servers.
You wanted to do a test migration first,
which again, is directly analogous to Azure Site Recovery.
You do that here from the replicating machines blade.
You do a test migration, which would not turn off the source VM.
It would create the VM in Azure,
but then you could clean up or delete that VM in Azure with
one command using Clean up test migration,
which I think is pretty cool.
If you're familiar with Azure Site Recovery,
you see a lot here,
so I would make an educated hypothesis that Azure Migrate Server Migration
is indeed using a lot of the ASR bits under the hood.
So we've got a migration taking place here.
Remember that all of the storage is synchronized,
so it's not like we've got a big network hit.
I think the big latency we see,
let's actually dip into the deployment details here,
is a prereq check shutting down the source VM,
so that was successful.
If we come back to Hyper‑V virtual machine,
core1 is turned off, preparing for failover,
start failover, and then ultimately, start the replica virtual machine.
And we can expect that once the failover completes and
we start the replica virtual machine,
we'll then have this core1 machine running as an Azure VM,
and then we're free to archive, decommission,
delete, whatever it is that we need to do with our local on‑premises VM.
And replication also would then stop.
It looks like it just finished now as we were waiting.
Good deal.
Let me head on over to the Virtual machines blade in another browser tab,
and there we have our core1 virtual machine up and running.
It looks like the virtual machine agent status isn't ready.
Well that makes sense because it's a newly deployed new virtual machine.
All of its size,
all of its properties have come via that assessment process that we saw before.
Let's close out of here.
Let's go back to Azure Migrate and go back to Servers, databases, and web apps.
Do a hard refresh.
It may take a little while for the portal to update status.
We should see Migrated servers.
This should go to a one before too long, and there you have it.
Hopefully you have a much clearer picture of the end‑to‑end with Azure Migrate Server Migration.