1 00:00:01,000 --> 00:00:02,090 In this demonstration, 2 00:00:02,090 --> 00:00:05,540 we'll take a look at Azure Migrate: Server Migration. 3 00:00:05,540 --> 00:00:06,790 Now what are we looking at here? 4 00:00:06,790 --> 00:00:12,330 We're actually looking at a Windows Server 2022 member server called MEM1. 5 00:00:12,330 --> 00:00:14,140 And if I bring up Hyper‑V Manager, 6 00:00:14,140 --> 00:00:18,180 I want you to see I have a virtual machine called core1. I 7 00:00:18,180 --> 00:00:20,140 actually got a connection to it right here. 8 00:00:20,140 --> 00:00:26,430 It's just a Windows Server Core virtual machine, and that is our migration goal. 9 00:00:26,430 --> 00:00:30,690 That is to say we're looking to get this into Azure with minimal muss, 10 00:00:30,690 --> 00:00:34,570 fuss, and greasy aftertaste to quote the great Mark Minasi, if that name 11 00:00:34,570 --> 00:00:37,440 means anything to you. Now the process of migrating, 12 00:00:37,440 --> 00:00:42,040 say, a Hyper‑V VM singly maybe isn't that big of a deal. 13 00:00:42,040 --> 00:00:47,150 You can just manually create the VM in Azure, specifying your chosen parameters, 14 00:00:47,150 --> 00:00:51,570 your chosen properties. And as long as the VHD of the given 15 00:00:51,570 --> 00:00:55,120 virtual machine is of the right generation and fixed rather 16 00:00:55,120 --> 00:00:58,310 than dynamically expanding, you're good to go, right? Well, yeah, 17 00:00:58,310 --> 00:00:59,770 that's fine for one VM. 18 00:00:59,770 --> 00:01:04,170 But the idea here is you may have who knows how many dozens, 19 00:01:04,170 --> 00:01:07,270 hundreds, thousands of virtual machines, so we're working with 20 00:01:07,270 --> 00:01:09,080 potential at much greater scale. 21 00:01:09,080 --> 00:01:12,960 So, let's head into the portal here. And if we go over to Azure Migrate, 22 00:01:12,960 --> 00:01:16,710 which you can easily find in the global search, just do a search for 23 00:01:16,710 --> 00:01:19,580 migrate, and it's a bit overwhelming at first, 24 00:01:19,580 --> 00:01:23,400 let's be honest, because there are a number of migration goals. 25 00:01:23,400 --> 00:01:26,370 I'll start at the bottom. Data Box would be where you just 26 00:01:26,370 --> 00:01:30,290 have potentially large volumes of static data that you want 27 00:01:30,290 --> 00:01:32,240 to get into Azure Storage. 28 00:01:32,240 --> 00:01:35,430 So you can essentially rent a storage appliance from 29 00:01:35,430 --> 00:01:38,520 Microsoft, pack it with your data, send it in. 30 00:01:38,520 --> 00:01:42,030 There's both online and offline versions of Data Box. 31 00:01:42,030 --> 00:01:45,980 We'll look at Web apps later, so I'm going to skip that. VDI 32 00:01:45,980 --> 00:01:48,580 stands for virtual desktop infrastructure. 33 00:01:48,580 --> 00:01:52,370 Basically, you're taking your on‑premises VDI and 34 00:01:52,370 --> 00:01:55,540 bringing it into Azure Virtual Desktop. 35 00:01:55,540 --> 00:01:57,800 If you're just looking at databases, 36 00:01:57,800 --> 00:02:01,570 there is a separate set of tools for database assessment and 37 00:02:01,570 --> 00:02:04,620 migration and not only SQL Server, interestingly. 38 00:02:04,620 --> 00:02:08,370 And then lastly, we have this catch all migration goal called servers, 39 00:02:08,370 --> 00:02:09,810 databases, and web apps. 40 00:02:09,810 --> 00:02:14,140 It used to be just called servers, but now it's more robust. 41 00:02:14,140 --> 00:02:18,830 And what I want you to see here is initially this is a blank screen. 42 00:02:18,830 --> 00:02:20,650 Let me see if I have another project. 43 00:02:20,650 --> 00:02:21,270 No, I don't. 44 00:02:21,270 --> 00:02:24,930 So notice that you can use this pill to navigate among multiple 45 00:02:24,930 --> 00:02:27,740 projects. And when you create a top‑level project, 46 00:02:27,740 --> 00:02:30,460 you're just basically specifying where it lives in your 47 00:02:30,460 --> 00:02:32,390 subscription and resource groups, 48 00:02:32,390 --> 00:02:36,890 your geography, and then the project name. You can do public 49 00:02:36,890 --> 00:02:39,930 endpoint or private endpoint if you want to connect to your 50 00:02:39,930 --> 00:02:42,440 project on a private IP address. 51 00:02:42,440 --> 00:02:43,800 When you create a project, 52 00:02:43,800 --> 00:02:48,080 you then choose an assessment tool and a migration tool, and notice that 53 00:02:48,080 --> 00:02:52,280 we can add more assessment tools by clicking, and this brings in some of 54 00:02:52,280 --> 00:02:56,320 the independent software vendor stuff that's not on the exam, but the 55 00:02:56,320 --> 00:02:59,980 idea is that you and your business may already have a license, so why not 56 00:02:59,980 --> 00:03:05,020 take advantage of those? I'm going to assume, and the AZ‑801 exam assumes 57 00:03:05,020 --> 00:03:09,570 that you're using the Microsoft assessment and Microsoft migration tools. 58 00:03:09,570 --> 00:03:12,910 Okay, first we do an assessment. And again, I've already done 59 00:03:12,910 --> 00:03:14,900 all the work here, so it's all filled in. 60 00:03:14,900 --> 00:03:17,170 When you first come in here, it'll be empty. 61 00:03:17,170 --> 00:03:20,010 You'll go to Discover, and you'll choose, well, are we 62 00:03:20,010 --> 00:03:21,790 going to download and use the appliance, 63 00:03:21,790 --> 00:03:25,800 which I definitely recommend you do, otherwise you can do an import from 64 00:03:25,800 --> 00:03:29,940 a CSV by downloading and completing this template. 65 00:03:29,940 --> 00:03:34,540 I like the appliance because it's easier and much more dynamic. Are your 66 00:03:34,540 --> 00:03:38,150 servers virtualized? And depending upon what you choose here, 67 00:03:38,150 --> 00:03:40,440 VMware, Hyper‑V or physical, 68 00:03:40,440 --> 00:03:43,180 you'll get a different download link. I did Hyper‑V 69 00:03:43,180 --> 00:03:45,840 for my case. You name the appliance, 70 00:03:45,840 --> 00:03:50,700 it generates a project key that you'll need to configure on the appliance, 71 00:03:50,700 --> 00:03:56,210 you then download the VHD at 12 GB pre‑configured Windows Server machine, 72 00:03:56,210 --> 00:04:00,290 and then you set it up and initiate discovery. And at the end of that 73 00:04:00,290 --> 00:04:04,920 discovery process, you'll see this dashboard here, Discovered servers, and 74 00:04:04,920 --> 00:04:09,270 these links are all hyperlinked where you can drill into them and look in 75 00:04:09,270 --> 00:04:13,770 greater detail of what's happened and what's brought in. And as you can see 76 00:04:13,770 --> 00:04:13,910 here, 77 00:04:13,910 --> 00:04:18,100 I've got my core1. This is that server core virtual machine that I 78 00:04:18,100 --> 00:04:22,820 showed you a moment ago that's running on my host, MEM1. The reason I 79 00:04:22,820 --> 00:04:27,520 don't have or don't see software inventory or dependencies is that I 80 00:04:27,520 --> 00:04:29,610 chose not to go that route. 81 00:04:29,610 --> 00:04:33,420 You can install the Log Analytics agent on your host and 82 00:04:33,420 --> 00:04:36,950 your VMs, and that gives you much richer insight in your 83 00:04:36,950 --> 00:04:39,160 discovery because as you see here, 84 00:04:39,160 --> 00:04:42,250 you've got the capability of inventorying all the installed 85 00:04:42,250 --> 00:04:45,540 software, as well as visualizing dependencies. 86 00:04:45,540 --> 00:04:48,540 So the idea with that is you go to Dependency analysis, 87 00:04:48,540 --> 00:04:52,720 Add servers. And as long as they meet the requirements, 88 00:04:52,720 --> 00:04:55,040 you can select them here and add them in. 89 00:04:55,040 --> 00:04:59,130 Again, I chose not to do that in this case, whether you do that or not. 90 00:04:59,130 --> 00:05:01,990 But let me go back to Azure Migrate: Server Migration, 91 00:05:01,990 --> 00:05:04,240 and let's pick up where we left off. 92 00:05:04,240 --> 00:05:06,980 Okay, so I've got two discovered servers. 93 00:05:06,980 --> 00:05:10,420 One that's been identified as Windows, one unknown. That's a 94 00:05:10,420 --> 00:05:12,750 VM that's in a really messed up state. 95 00:05:12,750 --> 00:05:15,040 I'm not going to migrate that one. 96 00:05:15,040 --> 00:05:17,560 You then create your assessments. 97 00:05:17,560 --> 00:05:21,420 You organize those assessments into groups because you very well might 98 00:05:21,420 --> 00:05:25,380 want to do your migration in phases, all right? We can review our 99 00:05:25,380 --> 00:05:29,040 appliance metadata, any notifications or groups. 100 00:05:29,040 --> 00:05:32,560 The assessment takes place after discovery, and 101 00:05:32,560 --> 00:05:36,010 notice that there's four templates, two of which are in public preview. 102 00:05:36,010 --> 00:05:40,310 The one we're concerned with is Azure VM. And what we do here is we choose our 103 00:05:40,310 --> 00:05:44,920 discovery source. Did we use a CSV or the appliance? And then we go to our 104 00:05:44,920 --> 00:05:49,490 Assessment settings, and we choose what are our assumptions in the assessment? 105 00:05:49,490 --> 00:05:53,050 Where in Azure do you plan the VMs to go? 106 00:05:53,050 --> 00:05:57,090 Do you know in advance what kind of managed disk type you'd 107 00:05:57,090 --> 00:05:59,530 use? Are you going to use reserved instances? 108 00:05:59,530 --> 00:06:03,440 You can see this. I don't need to read this, but it really allows you to 109 00:06:03,440 --> 00:06:08,740 add assumptions that will have a good personalization effect on that 110 00:06:08,740 --> 00:06:13,680 assessment result, okay? So let me come out of this assessment. I have an 111 00:06:13,680 --> 00:06:18,150 assessment created. It looks like I've got two for Azure VM, two for SQL. 112 00:06:18,150 --> 00:06:23,440 Let's go to that hyperlink. And we can see my core1 assessment. Let's 113 00:06:23,440 --> 00:06:24,840 click into it. 114 00:06:24,840 --> 00:06:28,270 It just gives you some visualizations, as you can see here. 115 00:06:28,270 --> 00:06:30,730 Now it says the confidence rating of the assessment 116 00:06:30,730 --> 00:06:34,060 is low. Wait for at least, okay, that was my problem. 117 00:06:34,060 --> 00:06:37,180 Remember earlier in this module, I mentioned that 118 00:06:37,180 --> 00:06:42,060 the longer your assessment period, the better results you're going to get. 119 00:06:42,060 --> 00:06:42,480 Yes, 120 00:06:42,480 --> 00:06:45,650 especially if you choose not the as is on‑prem 121 00:06:45,650 --> 00:06:47,850 option, but the performance‑based. 122 00:06:47,850 --> 00:06:50,550 So the longer you wait, as it says here, 123 00:06:50,550 --> 00:06:57,000 ensure that you wait for at least a day after starting discovery before creating your assessment.