 Hey folks, Ned Pyle here again. Today I'm going to talk about a option that we released in October for the Windows Admin Center. It is now the ability for you to generate on the fly Azure VMs all within Windows Admin Center, never leaving to go to the Azure portal in line with your workflow. And it works within several workloads, but it also just works when you're setting up a connection in Windows Admin Center. I'm going to do a quick demo right now to show you what I mean. We have these new add option which I have just clicked and you'll notice now that when I'm on the connection page I'm actually able to not just add VMs and servers and cluster and such, but I can actually create Azure VMs right now on the fly. So to create new and I will start making a VM in Azure without leaving Windows Admin Center. So you see this wizard open up, you see my subscription information, you see the resource groups, these are all being drawn using Azure REST APIs down into my Windows Admin Center. I start providing a name and a region, picking out which operating system images I want to be able to deploy. I start putting in some credentials. I'm obviously not Jeff Woolsey, I'm Ned, but I'm using his demo here for convenience of sake. I can size these VMs, I have filters, I can sort. So right now it's just showing all the available VMs for Server 2019. I can store on these columns. It's just a normal convenient user experience of being able to pick out and size up a VM, which in this case, we don't have any sort of real criteria for from the workload. I'm just creating a VM out of nowhere. If I was using storage migration service, it would size it to match my source VM and the same for storage other features inside of Windows Admin Center. I'm on the disk piece now. I can add managed disks for storage, specify their size, their performance type. If this was a different type of workload, not just a regular vanilla VM workload, it would actually be allowing me to specify the file system or automatically assigning the file system based on the workload, say if you were doing a migration for example. Now I can choose to join my on-premises domain as long as I have access to it. In this case, I'm not going to. Ordinarily, I probably would since most servers are joined to AD domains. And then I have access to whatever the network information is specified for the subscription inside of Azure. And I can go and review all this, take a look and see what I've done, make sure it looks right. Get a chance to go back, change my mind. And by clicking OK, by clicking the create there, I'm actually starting the VM generation process in Azure. And you can watch it in the Azure portal. You can watch it here. You can close this browser and go to lunch. This is all fired off into Azure. It's just keeping track of it at this point. Let's go take a look inside of Azure and see what's happening. I'm going to log in here to my subscription and take a look at my Azure deployment here under way. You can see that same server is deploying here. It's just in progress. And so even though I still have the access to all of the Azure portal, I have the convenience of being inside Windows Admin Center, perhaps in the middle of doing something without having to sort of multitask and change directions. So that was deploying an Azure VM from within Windows Admin Center. You notice that I never left to go anywhere else. I stayed right there inside of Windows Admin Center, getting myself brand new Azure Compute Goodness. For more information, I want you to visit this URL. And if you're not seeing it in your Windows Admin Center, make sure you download the latest one and it will be there. Thanks.