1
00:00:01,140 --> 00:00:03,080
Well, if we're talking about agent list, Tim,

2
00:00:03,080 --> 00:00:04,890
what's this Azure Migrate appliance?

3
00:00:04,890 --> 00:00:08,950
Well, the idea is because Azure Migrate: Server Migration doesn't have a

4
00:00:08,950 --> 00:00:14,430
requirement for a site‑to‑site VPN, you need to have some engine of creation

5
00:00:14,430 --> 00:00:19,110
on‑prem. So the Azure Migrate appliance is a downloadable Windows Server

6
00:00:19,110 --> 00:00:24,250
2016 VM that runs on an evaluation license, and it includes a web

7
00:00:24,250 --> 00:00:28,840
application that allows you to register that appliance into your Azure

8
00:00:28,840 --> 00:00:34,110
Migrate server migration project and then take care of orchestrating the

9
00:00:34,110 --> 00:00:35,500
assessment and migration.

10
00:00:35,500 --> 00:00:41,340
There are some limits in the Microsoft docs, 10,000 VMware hosts, 5,000 Hyper‑V

11
00:00:41,340 --> 00:00:46,080
hosts, 1,000 physical servers per appliance, but of course, you can have

12
00:00:46,080 --> 00:00:50,740
multiple appliances. When you turn the appliance loose,

13
00:00:50,740 --> 00:00:54,190
it's going to scan and inventory your environment, and then in your

14
00:00:54,190 --> 00:00:58,500
project you create an assessment. You want that assessment to take

15
00:00:58,500 --> 00:01:01,360
into account as much data as possible.

16
00:01:01,360 --> 00:01:05,870
So what I mean by longer assessment times really means you want to tune

17
00:01:05,870 --> 00:01:09,470
your assessment and give Azure hints, for example,

18
00:01:09,470 --> 00:01:11,800
are you looking to do reserved instances?

19
00:01:11,800 --> 00:01:15,980
Are you looking to do hybrid use benefit? These sorts of things that Azure

20
00:01:15,980 --> 00:01:20,420
would not be able to make an evaluation on. The assessment process that it

21
00:01:20,420 --> 00:01:25,100
automates is looking at the compute, and storage, and networking and giving you

22
00:01:25,100 --> 00:01:29,500
advice on what the target virtual machine configuration should be, you see?

23
00:01:29,500 --> 00:01:35,410
Dependency analysis is an option. It's not required with Azure Migrate: Server

24
00:01:35,410 --> 00:01:39,880
Migration, but it's cool because it allows you to model the client and server

25
00:01:39,880 --> 00:01:44,090
connections going on on those VMs or on those physical servers that you're

26
00:01:44,090 --> 00:01:47,940
looking to migrate to make sure that you're not surprised post migration,

27
00:01:47,940 --> 00:01:52,990
uh‑oh, I forgot about this dependency on this API or whatever it might be,

28
00:01:52,990 --> 00:01:56,840
you see? And then as far as monitoring in the long term,

29
00:01:56,840 --> 00:02:00,360
once the machine is migrated, it becomes an Azure VM, so it's

30
00:02:00,360 --> 00:02:02,800
natively a part of Azure Resource Manager.

31
00:02:02,800 --> 00:02:05,230
So you've got Azure Monitor, Log Analytics,

32
00:02:05,230 --> 00:02:08,050
Sentinel, all of these different monitoring platforms,

33
00:02:08,050 --> 00:02:12,560
Application Insights. But notice that first one in this last bullet point,

34
00:02:12,560 --> 00:02:17,630
Arc. I would submit that you have your on‑premises servers, at least some of

35
00:02:17,630 --> 00:02:21,910
them, maybe your Hyper‑V hosts registered in Azure Arc so you can do

36
00:02:21,910 --> 00:02:24,180
Azure‑based management, if nothing else,

37
00:02:24,180 --> 00:02:30,000
as a prep step for preparing those machines for integration into the Azure ecosystem.