In this video, Sharon will step through how to create an Azure virtual network using the Azure Resource Manager portal. Creating and modifying subnet address ranges will also be shown.
- [Instructor] Now that we have an understanding of virtual networks, let's go ahead and create one within Azure. I have already created a resource group called VirtualNetworks, and I'm now in the resource group. As you can see, there is nothing in this resource group. I'm going to go ahead and add in a virtual network. To do so, click Add. You can either search for virtual network ... In my case, I already have it available. I'm going to go ahead and click it. We have a little bit of information about our virtual network. We select our deployment model. I'm going to be doing everything in the Resource Manager, but there may be cases where you still have to work in the classic portal, and I'm going to go ahead and click Create.
We're going to provide a name for our virtual network, and for our example, we're going to call it Production. Next, I'm going to go ahead and assign an address space. For our demonstration, I'm going to be using an address space of 192.168.0.0, CIDR notation 24. I now have 256 addresses available to me within that virtual network, or so it seems. We'll expand on that as we go through this. Next, you always have to provide a subnet. This is mandatory. You could use default, but I want to go ahead and create two subnets within our virtual network.
I'm going to create a front end and a backend subnet. I'm going to start off with the front end, and as I tab down, we'll notice that we now have an error. So now I have to change my subnet address range. For this example, to start with, I'm going to go ahead and use 192.168.0.0/29, which will provide us with eight addresses. Again, or so we think. My subscription is already selected for us, because I created this from the resource group, and that's how I like to work. I like to create a resource group, my virtual networks, and then start adding in my resources.
Our location here is the East US 2. Click Create. It takes about 30 seconds or so for a virtual network to be created. It doesn't take long. Our deployment has now succeeded. I'm going to go ahead and open up that virtual network. I'm going to go ahead and close a few blades to get back to the resource group, and there is our Production virtual network. I'm going to go ahead and click on it, and there's not much in here right now. It's kind of boring. I'm going to go ahead and click on Subnet, because I still need to add in that second subnet. But what I want to point out here is that front end subnet that we just created, where we thought we were going to have eight usable IP addresses is actually only three.
Remember, we will lose five addresses immediately to Azure. We're going to leave this as-is. This isn't ideal, but I want to continue on. I'm going to go ahead and create my backend subnet. I'm going to call it BackEnd. Our address range has already been configured for us. We could go ahead and change this as necessary. I'm going to leave it. Click OK. I'll take a moment for the subnet to be added, and you'll see that we have 11 addresses available to us in that backend subnet. I want to show you what will happen if I want to change the number of usable addresses in the front end subnet.
Go ahead and click on it. After creating all this, I realize, oh no, three addresses is not going to be enough, because I forgot about the five that I was losing. So I want to go ahead and change this to 26, because I need those 64 addresses, but we're going to notice right away that this is erroring out. If I come over to the exclamation mark, it's going to tell us it's going to overlap. In this case, if I needed more addresses, my only course of action is to actually delete the backend subnet. You keep hearing me talk about planning. This is critical.
This is all part of your planning. And close that. So in order to increase our front end to have enough usable addresses for us, I'm going to delete the backend subnet. You may have to refresh the page. I'm going to close a couple of blades. I've gone back into the virtual network, and now I'm going to click on subnets again, and we now only have the front end subnet available to us. And now I can go ahead and increase the number of usable addresses, so I now have 64 addresses available to me. Now I'm going to click Save, and again, this will take a moment.
I'm going to go ahead and close the blades, and then refresh our subnet page. Click back in Production, back in Subnets, and now you'll notice that we have 59 usable addresses. Now I'm going to go ahead and continue creating that backend subnet. Again, click Subnet, provide a name. I'm going to go with the default here, and then click OK. That's all these is to it to create a virtual network. As you saw, it is a very simple process, but if you do not plan it out correctly, you will run into errors as you continue to build out your implementation further down the road.
When it comes to Azure, it's all about planning, and planning, and then more planning.
- Creating an Azure virtual network
- Creating a virtual network using PowerShell
- Deploying a VM into a virtual network
- Modifying IP addresses
- Working with Azure DNS
- Configuring NSGs
- Setting up load balancers
- Configuring Azure load balancers
- Creating an application gateway
- Setting up on-premises connectivity
- Adding gateway VPNs
- Validating VPN devices
- Configuring VNet
- Creating site connections