So once the Azure Migrate appliance has discovered your servers and your VMs,
it now has a way to monitor them, and let it do so for a long time,
and that way you'll get a higher confidence rating.
Ultimately, you're looking at a couple of things here, aren't you?
You're looking at what is this machine's readiness for Azure?
Yes, yes, with conditions not ready, readiness unknown.
Looks like I really didn't wait at all honestly.
As soon as the discovery was finished, I created the assessment.
So, notice that the engine here logically hasn't even determined the OS.
It made a good guess, and it's correct, it is Windows Server 2022.
Though the Azure readiness is an important piece,
you can export these assessments.
They come out as Excel files, and they're really nice and formatted,
they're pretty much presentation‑ready right out of the box.
The other thing you're concerned with it seems to me are the cost details.
How much is this migration going to cost?
And so, you've got your compute,
as long as the virtual machine in Azure is allocated and running,
you're being billed, and then there's the storage cost depending
upon what kind of managed disk you're using.
All right? so you might think, okay, so far so good, all right.
We've configured the appliance.
We've discovered our infrastructure.
Optionally,
we might have deeper insight with dependency analysis and software inventory.
We've created our assessment here and put in our specifications,
and that deliverable is awesome, it really gives us a good idea,
but how do we then use that assessment?
See, because now that we're finished with the discovery and assessment phase,
it's time for us to come to the migration phase.
And this here also says Discover.
What in the world?
Why would it discover again?
I'm bleeding you.
The good news is we can actually use that assessment,
that output, as input to the server migration process.
So when we step through Discovery here,
it asks you what is your virtualization platform,
and then it tells us again, depending upon what your scenario is,
what to do.
With Hyper‑V,
it's a Microsoft virtualization product so it's
officially an agentless approach,
but you still do need to install this Azure Site Recovery
provider agent on not your individual VMs,
fortunately, but your Hyper‑V hosts.
All right?
So you do need that.
Now if you're going to go the route of VMware,
you need to have vSphere, absolutely, and there's two approaches here.
And there's a Docs article that helps you choose whether you want to do
agentless or agent‑based, there's some differences there,
and the Azure Migrate appliance comes down as an OVA file that
you can get going in your VMware environment.
And then physical, it's very similar.
Do you want to install a new replication appliance or scale out an existing?
And there you've got, again, the configuration server virtual appliance.
So that is that.
Let me go back to Hyper‑V.
And that's, I've already finished the discovery and the registration.
So the discovery really should be registration,
where we're making sure that the output of our discovery up
here is being fed into the migration.
The heavy lifting comes in here with Replicate,
because here, we are again going to choose our scenario,
and then here's the magic, apply migration settings from our assessment.
I love this.
So we bring in our core‑1 assessment.
Now I've already done this,
so it's not allowing me to select another virtual machine,
but based on your assessment, if you're doing this in phases,
you'll have only the VMs that are associated with a
given assessment show up in this list, and then you can proceed.
It's not letting me proceed but you've got Target settings,
where are you going to place the virtual machines,
any overrides with compute, and disks, and taxonomic tags,
and then everything is good, review and start replication,
and then it's going to be a replication process that could take a while.
Another good reason to use phases here is that you don't
saturate your internet connection too much.
So at this point, as you can see,
I've got two discovered servers and one that's replicating.
And again, these are all live hyperlinks.
So let's see here,
we've got core1 that is healthy and protected so it's really ready to go.
That other VM there is in a messed‑up state and that's fine.
Can I actually remove it from here?
Yeah,
I can actually force a stop replication because I'm not going
to do anything with that particular machine.
And if you have already seen my modules on Azure Site Recovery,
you know about the difference between a test failover and a real failover.
You have a similar idea here.
Let me come out of here and go to Migrate.
Shutdown machines before migration to minimize data loss?
Yes or No.
What virtual machine are you ready to do your migrate?
And then, migrate. It's pretty easy, isn't it?