All righty then. So, if you're still with me, congratulations. I know it's been a long haul to get through these demos and into an actual assessment. I mean, just getting to that is actually quite a bit of work. So, what exactly is an assessment anyway? What information are we looking for when we do an assessment? Well, we're looking for a couple of different things when we do an assessment.

When we review our assessment here we want to see which VMs are suitable for migration to Microsoft Azure and what the estimated monthly compute and storage costs are going to be to run our migrated VMs in Azure. We want to see that monthly storage cost estimation because it's important to understand what those estimated costs are going to be for disc storage after our migration.

From this assessments screen I can see what assessments have been performed.

Under Azure readiness here, I can see if my VMs are ready for migration to Microsoft Azure. There are four different statuses that are shown here. They include Ready for Azure, Ready with conditions, Not ready for Azure, and Readiness unknown.

Ready for Azure shows VMs that are ready for migration right now. A VM is counted as ready when Azure Migrate recommends a VM size and cost estimate for it during the assessment. Ready with conditions shows VMs with issues, but also suggests remediations. Not ready for Azure includes VMs that have issues that make them, obviously, not ready for migrations and then Readiness unknown includes VMs that Azure Migrate can't assess readiness for due to data availability issues.

I can view each of these by clicking on the Azure readiness tile here. This allows me to view the VM readiness details for each status. And I could even drill down to the individual virtual machines to see details like storage, compute and network sites.

Now, for this APP01, we can see Azure VM readiness shows unsupported boot type. If we click on unsupported boot type, it's going to take us out to the troubleshoot guide for Azure Migrate. And if we scroll down here. As a matter of fact, what we'll do is we'll search for boot and there we go. We see an unsupported boot type. Azure doesn't support VMs with an EFI boot type. If we bounce back over here and go back into readiness, we can see the EFI boot type.

Now, what Microsoft recommends is that we convert the boot type to BIOS before we run a migration. It also tells us here that we can use Azure Migrate Server Migration to handle the migration of these types of VMs. What it will do is convert the boot type of the VM to BIOS during the migration. So, although we're getting the conditions here, we're good here based on what this is telling us.

Now, if we go back to our assessments here. Let's go back out to our assessments page. And let's review some of the cost details. The assessment summary here shows what the estimated compute and storage costs are going to be for running my VMs in Azure.

Now, these costs are aggregated for all of my VMs that are included in my assessment group. So what I can do here is drill down and take a look at what the estimated compute cost will be for running my VM in Azure. Can also look at the storage. We can see my estimated compute cost for a standard F2S_v2 would be $128, $129 and storage would be roughly $35. We can see the target disk is going to be 256 gig, it's going to be a premium disk and it shows the cost for that disk. It also shows here the number of cores, what the utilization can be expected, the memory size and the utilization.

Now, I should mention that these cost estimates are based on the size recommendations that Azure makes for a machine along with its disks and other properties. These estimates are for running the on-prem virtual machine as infrastructure as a service or IaaS VMs in Azure.Azure Migrate server assessment doesn't consider platform as a service or software as a service costs, so keep that in mind.

Now, lastly, when we perform an assessment, Azure Migrate server assessment is going to assign a confidence rating to our performance-based assessment. This rated from one star, which is the lowest rating, to five stars, which is the highest rating.

So, let's bounce back out to our assessments here. Now, this confidence rating here helps you estimate the reliability of the assessment's size recommendations. The rating is based on the availability of data points that are needed to compute the assessment.

Now, the confidence rating here is one star, largely because I have about an hour's worth of data for my APP01 server. So, Azure Migrate recognizes that and is telling me, hey, I have enough data here, but it's not a whole lot. So, while I can give you an assessment, I'm not real confident because I don't have a ton of data to go by.

Now, that being said, you can learn more about these confidence ratings by visiting the URL that you see on your screen.

Be sure to join me in the next lesson, which is really, again, just another demonstration, where we'll begin the migration of APP01 from VMware to Microsoft Azure using Azure Migrate.