So we're back in the portal. Let's go ahead and go into the Resource Group. And you'll see that we have the VM. Here's the public IP address, Network Security Group. There's the network interface. There's the managed disk. Services vault was there from previous. So that wasn't created at this time. Then we have the virtual network. So let's go ahead and go into the VM. Once we go in there, you can see that we have an overview of the VM. So we have a CPU average, network total, disk byte total, disk operations per second average. We want to connect to it. You just click on Connect, and we have the ability of going RDP. Now if this was a Linux machine, it would be SSH. And we also have the ability of doing a bastion, which a bastion, so that we don't have to allow people to be able to access the virtual machine from the Internet or from the external network, that's what I have right now. I have a hole poked in a network security group 43389. What I could do is I can use a bastion, and I would RDP into the bastion, and then RDP into the virtual machines that I have in the back end. That way, it protects our environment. I'm going to go ahead and do the RDP though. Once I do that, you can see here's RDP, SSH, and bastion. I'm going to go ahead and download the file. Go ahead and open up that file. Now, it's asking for the credentials. So, use a different account. And this is going to be azureadmin, and then the password. Then I'm RDPed in just like I would, RDPed into my actual Hyper-V server here. Now, the thing is is this is not the fastest server in the world. It's all I got one processor and 3.5 gigs of RAM. So you have to have a little patience. It's actually going to come up and say that I don't have enough RAM. But it gives us the ability to working with that machine is just as was an on-premises in our Hyper-V server. So you can see I got that memory error right here, low on memory. Just the same things as we would get when we're setting up a server on local machine. So I'm in my Server Manager. So I'm going to go ahead, and I want to add the web server on here. I could do it with the custom script extension, and that's what we use for managing up. Just making this a static web server. So the web server is installed. We can go ahead and make a couple more changes here. I'm turning off the enhanced Internet Explorer. Go ahead and bring up the Internet Explorer. And put in localhost. And that brings up the IES. Now why I do all this stuff? This is 104 211 52 153. Because what I'm going to do is I'm going to show you how we can connect to this virtual machine to this web server. So what we do is we get the IP address. Pop it into our Internet, into RH. It's trying to connect. But says it can't reach it. Why is that? Well, the reason is because, remember, we talked about the network security group. So if we go back in here, And go over to our Network Security Group, We'll see that RDP is the only one that's allowed through. Remember, you have to explicitly open it. So I'm going to go into my inbound security rules. And go ahead and add port 80 and TCP. The priorities will be 310. It's less than the 65,500. It's going to be the second rule that shows up or is going to be executed. And I'll just call this web, and add this. Now, the thing is, is you're dealing with Azure. So that means we're in the cloud. Things that don't take effect as quickly as you would like them to. It may take about three to four minutes or a couple times be able to get access to that website. So if we go back up here to the browser and do a refresh, there we go. So now, we're connected to the web server. And so, what we did here is we installed a Windows server and we opened up the port after we've installed IES. So that's our workload, open up the port within the network security group, so that way we can get access to it. Now, within the VM, we also have VM extensions. And so, remember we talked about this before, you have the backup extension that we looked at with the Azure Recovery Services. Well, we also looked at the network watcher was one of the other objects that we can put on. You can see the type of traffic that was going on during that installation. So we're going to go into the Extensions here. And I'm going to go ahead and add, and I'm going to install the anti-malware. So, Microsoft anti-malware, which is actually Defender. And so, what we can do is we can put in what are the excluded files and locations, excluded file extensions. We can also turn on the real-time, and run a scheduled scan. We can enable that. And then, the scan type, quick. And when's it going to run? On Saturday at 1:20 in the morning. Again, this is going to take a second to be able to be installed. Then we'll be able to go over to the virtual machine, and we should be able to see the actual Defender. Okay, so the extension's been installed. Let's go ahead and see if we can go over here. And there's Microsoft Defender. So, Defender is now installed. And so, that's one of the ways you can work with the extensions. We showed you the other one, we'll talk about how we can use it for configuration later on. So we have down here, we have some support and troubleshooting information for monitoring. We also have up here, there's our connect. There's the backup disaster recovery. Our change tracking, and here's our connection troubleshooter, and we have the serial console. Now, before we didn't have a way of being able to understand what was going on with the virtual machine without actually going and looking at the Azure monitor. But now, we have this ability. And also, we have the connection monitor. And remember that we went in and implemented the Boot Diagnostics. This allows us to be able to see a screenshot. And then we can also look at the serial log.