- [Male Instructor] Now that we know which objects can be created to deploy networking solution with Azure, let's go ahead and create some of those objects and actually deploy our networking configurations. So I'm going to click on my new icon and browse down to networking to select my networking objects. The first object that we will create, we discussed it earlier, the virtual network. When I create the virtual network like all of my objects in Azure using the new portal, I have the choice to use the resource management deployment model or the classic deployment model.
I'm going to use resource manager to be able to manage this virtual network with all my other objects. The next configuration that I'm going to set is going to be the name of my virtual network. I'm going to want to pick a name that's going to be unique in my environment. I'm going to call it LinkedInNetwork1 and it's going to be the first network in my environment. The next setting is going to be my address space. The address space, we discussed earlier as well, is going to be the all-encompassing address range that is going to be used for the devices that will be found within this network.
Remember that within my address space I can have one or multiple subnets as long as their ip address is within that range. Also remember that once I set my address space at the moment of creation of my virtual network I can not change it later on. So it's important to pick the right one. Next I'm going to define the name of my subnet. Again, my subnet is going to be found within my address space. My subnet name here I'm going to call it LinkedInSubnet1 and note that my ip address range again is within my address space range for my subnet.
I have my subscription like all my other objects and then my resource group name. My resource group name I'm going to select LinkedInGroup1 and then I'm going to click on create in order to create my virtual network. It will take a few seconds for the virtual network to be created. I will then move ahead to the next object that I want to create while this happens. By the way I will be notified as soon as my virtual network has been completely created.
The virtual network gateway will be next. The virtual network gateway will actually depend on my virtual network. I will actually associate it with my virtual network. I'll have to have my virtual network complete its creation by the time I'm done creating my virtual network gateway which should be around the same time. I'm going to click on my virtual network gateway. You'll remember that the virtual network gateway is going to be the object that will allow the connection from a remote server or remote client into my virtual network.
Essentially creating an entry point into my virtual network. Let's give it a name. I'm going to call it LinkedInGateway1. I have two types of virtual network gateway that I can create. One is VPN and one is ExpressRoute. You'll remember that an ExpressRoute gateway will provide a dedicated through a service provider which has some additional costs that are incurred with that. I'm going to create a VPN virtual network gateway which will be a entry point through VPN.
So using a secure link into my network. I have two types of VPNs. I can have a route-based or a policy-based. If I select policy-based I only have a choice of basic. If I select route-based then I have multiple choices such as basic, standard and high performance. Standard and high performance essentially give me more bandwidth into my connection but also comes at a higher cost. I'm going to pick route-based and I'm going to make it basic.
I'm going to click on choose virtual network to actually select the virtual network that will be associated with my virtual network gateway. Here it is, LinkedInNetwork1 that I created just a couple minutes ago. I'm going to pick LinkedInNetwork1. You'll notice that automatically the ip address range that I defined for my virtual network gets populated for the gateway subnet address range. Automatically I have a new subnet that is being used for my gateway and that is within the subnet range of my virtual network.
Next I have an ip address. Because this is an entry point from the internet into my virtual network I need an ip address which is going to be a publicly routed ip address to act as that entry point into my virtual network. I can choose a public ip address. Since I have none that have been pre-created I'm actually going to create one. Actually you'll notice that I have one over here that is grayed out and that is because it is already associated to another virtual network.
I'm going to click on create new to create a new ip address. Then I'm going to give it a name of IP and then click OK. Now my new ip address has been created as easy as that. You may wonder what is that actual ip address? Well the ip address is dynamically managed and dynamically provided by Microsoft Azure to my gateway device. We'll be able to actually see which ip address has been given to my device a little bit later on when we manage the virtual network gateway.
Notice a little message here at the bottom which says "Provisioning a virtual network gateway "may take up to 45 minutes." From experience it really does take that long. The reason for that is that there are many objects that must be created within Azure to support this gateway. Even though it looks like a software configuration on our end that we are creating through the portal in reality what is happening on the back end in Azure is there are several components that are being deployed in Azure to actually provide all of those networking functionalities.
So I'm going to click on create and allow that process to complete.
- Understanding Azure subscriptions
- Managing Azure with portals and PowerShell
- Configuring Azure web apps
- Deploying virtual machines
- Configuring virtual machines for high availability
- Managing Azure Active Directory
- Creating Azure virtual networks
- Implementing a VPN
- Performing Azure backups