1
00:00:00,940 --> 00:00:03,140
Azure Migrate Overview.

2
00:00:03,140 --> 00:00:04,930
Azure Migrate is really cool.

3
00:00:04,930 --> 00:00:07,350
That's my official term of the day.

4
00:00:07,350 --> 00:00:10,710
We could say that Azure Migrate, more specifically,

5
00:00:10,710 --> 00:00:14,170
is an integrated solution in Azure to assess and

6
00:00:14,170 --> 00:00:16,710
migrate on‑premises infrastructure, apps,

7
00:00:16,710 --> 00:00:17,540
and data to Azure.

8
00:00:17,540 --> 00:00:20,270
You'll see in detail how this works in the demo,

9
00:00:20,270 --> 00:00:23,140
but there are a lot of moving parts,

10
00:00:23,140 --> 00:00:26,420
and there are many different types of workloads that you can migrate.

11
00:00:26,420 --> 00:00:28,870
We're going to do machines in this lesson,

12
00:00:28,870 --> 00:00:31,730
but there's built‑in paths for databases,

13
00:00:31,730 --> 00:00:34,450
for applications, containers, virtual desktops.

14
00:00:34,450 --> 00:00:40,050
It's a one‑stop shop, Azure Migrate is, for your Azure migration goals.

15
00:00:40,050 --> 00:00:45,650
You'll see that Migrate functions along the lines of assessment and migration,

16
00:00:45,650 --> 00:00:48,870
so it's basically a two‑phase process,

17
00:00:48,870 --> 00:00:51,480
and you also can choose between first‑party

18
00:00:51,480 --> 00:00:54,860
Microsoft‑provided tools and third‑party tools.

19
00:00:54,860 --> 00:00:58,430
However, the third‑party tools have different support, different requirements.

20
00:00:58,430 --> 00:01:01,840
Those independent software vendor, or ISV,

21
00:01:01,840 --> 00:01:05,310
tools, for example, work only in the Azure public cloud,

22
00:01:05,310 --> 00:01:06,960
not with the Azure Government cloud.

23
00:01:06,960 --> 00:01:11,860
In terms of server migration, we can migrate physical servers,

24
00:01:11,860 --> 00:01:17,040
VMware, and Hyper‑V virtual machines performing both assessment and migration.

25
00:01:17,040 --> 00:01:19,850
That assessment piece is really important because think of it this way.

26
00:01:19,850 --> 00:01:23,950
You may have a fleet of virtual machines running on‑prem that each

27
00:01:23,950 --> 00:01:27,770
have an allocation of memory and CPU and storage.

28
00:01:27,770 --> 00:01:31,770
You're going to need to model that based on the performance

29
00:01:31,770 --> 00:01:35,790
expectations that you have into Azure virtual machine sizes.

30
00:01:35,790 --> 00:01:39,480
Wouldn't it be nice to get detailed recommendations on,

31
00:01:39,480 --> 00:01:42,720
for example, this particular VM should have Premium Storage,

32
00:01:42,720 --> 00:01:45,230
this other one should have Standard Storage,

33
00:01:45,230 --> 00:01:47,630
and that's going to save you money and give you

34
00:01:47,630 --> 00:01:49,480
better performance in the long term.

35
00:01:49,480 --> 00:01:52,940
Well, you'll see that Azure Migrate assessments can do that for you.

36
00:01:52,940 --> 00:01:57,340
And with migration, we're actually talking about replication and failover.

37
00:01:57,340 --> 00:02:03,350
So what we've learned elsewhere in this AZ‑801 learning path about Azure Site

38
00:02:03,350 --> 00:02:07,950
Recovery comes back in a review sense here because we could look at Azure

39
00:02:07,950 --> 00:02:12,850
Migrate Server Migration in many ways along the same lines as configuring

40
00:02:12,850 --> 00:02:15,640
Azure Site Recovery for disaster recovery.

41
00:02:15,640 --> 00:02:18,900
It's just that when we do the migration/failover,

42
00:02:18,900 --> 00:02:23,330
we don't reverse directions anymore because the idea is we'll continue to run

43
00:02:23,330 --> 00:02:27,140
the workload in Azure and decommission our local environment.

44
00:02:27,140 --> 00:02:31,440
The engineering team at Microsoft, based on customer feedback,

45
00:02:31,440 --> 00:02:40,000
wanted to rely on agents as little as they possibly could, so most of what we have with server migration is agentless.