Okay, folks, we are getting there. In this demonstration, we're going to set up and run an assessment of my VMware environment. There are two types of assessments that we can choose from. I mentioned these earlier. They include a performance-based assessment and an as on-premises assessment. I'm not going to go into the details of these since we already covered them, but I just wanted to let you know that what we're going to do here is complete a performance-based assessment.

To run our assessment we need to browse to the servers tab in the Azure Migrate: Server Assessment tile. So let's bounce back to Azure Migrate - Servers here and now from here, we need to click on Assess. Now, in this Assess servers box, or this Assess servers window I should say, we can set our discovery source to either imported machines or machines that were discovered from the Azure Migrate appliance.

Since we did the discovery through our appliance, that's what we're going to choose here. Now we also have to give our assessment a name so I'm just going to call this MyAssessment. And then what we'll do here is we'll click View all to view all of our assessment properties here.

Now, if we hover over Target location here, we can see that this target location references the Azure location to which we want to migrate to eventually. Any sizing or costing recommendations that are done as part of the assessment are going to be based on the location that I specify here. Hovering over Storage type here tells us that this dropdown allows us to specify the storage type that we want to use in Azure.

Now, for a performance-based sizing, which is what we're going to do, the disk type here is suggested based on the disk IOPS and the throughput for each of the on-prem disks. So we'll leave this set at Automatic. And then we can actually set reserved instances here if we want to.

Now, by reserving instances, we can save a ton of money but I don't want to reserve any instances here. So we'll just drop this down to No reserved instances. Now you notice when I change this Reserved instances option, the VM series changes so we'll have to select a VM series down here. And then we see here the sizing criterion for our VM. Essentially this is telling me that performance-based sizing is going to consider the utilization data of the VM and then it's going to right size the VM accordingly in Azure.

The Performance history dropdown is the amount of history, or duration of history, that I want to use when considering the on-prem performance. And one day for me is fine. We could also select one week or one month. And this Percentile utilization here, hovering over this icon tells us that this is the percentile value that we'd like to consider for the performance history of our on-prem VMs. So we want to consider this in the 95th percentile. If we change the dropdown here, we can go as low as 50%. So we'll set it to 95 and leave it.

Hovering over VM series tells us that this dropdown will allows us to choose a VM size based on the workloads running in the on-prem VMs. Azure Migrate is going to recommend a VM size in the VM families that I select here. So, for example, if I do a dropdown here what I can do is if I select all I make a larger pool for Azure Migrate to specify a specific size from that pool. So, for example, selecting all here I have 19. So when Azure Migrate recommends a VM size, it's going to look at all of these sizes and choose accordingly.

Now, this comfort factor is a little misunderstood. Now, what this comfort factor is is a buffer. Now, this buffer gets added on top of utilization data to account for things like seasonal usage or shorter time periods of performance history, like we have here. We have one day. Now, the example they give here is a 10 core VM with a 20% utilization would often result in a two core VM post-migration. Using a comfort factor of two, it results in a four core VM as a match.

We'll leave this at the default for now and then the pricing we can leave at its default as well. Pay as you go in U.S. dollars, no discounts and we're going to set our VM uptime to 31 days a month at 24 hours a day. Now down here, we can specify the Azure Hybrid Benefit. Hovering over the icon for the Hybrid Benefit tells us that this Azure Hybrid Benefit allows current Microsoft customers that have Windows Server Software Assurance or Windows Server subscriptions to bring their own licenses to Azure. I don't have that so I'll select no. And then I'll take a look here, make sure everything looks good and then I'll save my settings.

Now what we'll do here is create a new group. And then what we'll do is we'll add our VM that we're going to migrate to this group. Now, a group in this context collects one or more VMs and puts 'em together in that same grouping for assessment. So we'll just call this MyVMs. And then from here, we can specify the appliance name. We only have the one, MyAppliance. And then we can select the servers that we want to assess. And we'll go ahead and select APP01. And then we'll create our assessment here. And now after we create our assessment we can view it in the Azure Migrate server assessment tile. But you'll notice, we have no assessments here yet, so let's refresh. And now we see we have the group that we created and our assessment. Now I can view the assessment by clicking it here and then clicking on the actual assessment. And we can see our assessment is now ready for use. We can even export our assessment by clicking Export and that will pull it down as an Excel file. So in the next demonstration, we'll walk through the review of our assessment.