Azure Migrate Overview.
Azure Migrate is really cool.
That's my official term of the day.
We could say that Azure Migrate, more specifically,
is an integrated solution in Azure to assess and
migrate on‑premises infrastructure, apps,
and data to Azure.
You'll see in detail how this works in the demo,
but there are a lot of moving parts,
and there are many different types of workloads that you can migrate.
We're going to do machines in this lesson,
but there's built‑in paths for databases,
for applications, containers, virtual desktops.
It's a one‑stop shop, Azure Migrate is, for your Azure migration goals.
You'll see that Migrate functions along the lines of assessment and migration,
so it's basically a two‑phase process,
and you also can choose between first‑party
Microsoft‑provided tools and third‑party tools.
However, the third‑party tools have different support, different requirements.
Those independent software vendor, or ISV,
tools, for example, work only in the Azure public cloud,
not with the Azure Government cloud.
In terms of server migration, we can migrate physical servers,
VMware, and Hyper‑V virtual machines performing both assessment and migration.
That assessment piece is really important because think of it this way.
You may have a fleet of virtual machines running on‑prem that each
have an allocation of memory and CPU and storage.
You're going to need to model that based on the performance
expectations that you have into Azure virtual machine sizes.
Wouldn't it be nice to get detailed recommendations on,
for example, this particular VM should have Premium Storage,
this other one should have Standard Storage,
and that's going to save you money and give you
better performance in the long term.
Well, you'll see that Azure Migrate assessments can do that for you.
And with migration, we're actually talking about replication and failover.
So what we've learned elsewhere in this AZ‑801 learning path about Azure Site
Recovery comes back in a review sense here because we could look at Azure
Migrate Server Migration in many ways along the same lines as configuring
Azure Site Recovery for disaster recovery.
It's just that when we do the migration/failover,
we don't reverse directions anymore because the idea is we'll continue to run
the workload in Azure and decommission our local environment.
The engineering team at Microsoft, based on customer feedback,
wanted to rely on agents as little as they possibly could, so most of what we have with server migration is agentless.