Sharon demonstrates how to create an Azure virtual machine within the virtual network, outlining the benefits of provisioning the vm this way.
- [Narrator] Now that we've created our virtual network, let's go ahead and deploy a virtual machine into this virtual network. I've already logged in to Azure and I am in the Virtual Networks Resource Group and you can see we have our production virtual network already available to us. This is the one we've already created. I'm going to go ahead and add a virtual machine. To do so, I'm going to click add and then I'm going to take Server 2012 R2. You can go ahead and search for it in my case it's already available to me. I'm going to create it in a Resource Manager so I'm going to go ahead and click create. I'm going to go ahead and deploy a domain controller I'm going to provide the name of DC.
I'm going to go ahead and use a standard disk. I'm going to provide the username and password. This is the administrator username and password. And below, we're going to deploy this into the existing Virtual Networks Resource Group. Our location's already specified for us and click ok. For our demonstration, I'm going to go ahead and choose an A1 standard virtual machine. I know that this virtual machine only comes with one network interface card or NIC. If you need more than one NIC, you are going to need to choose a virtual machine that best meets your requirements.
I'm going to go ahead and click select. We have covered off creating virtual machines in another course. Please refer to that course for some of the other parameters. For our demo here, we're going to focus on network only. In this case, I only have the production network available to us within that resource group. I could go ahead and create a new one. So, if I hadn't created a virtual network this is now the time to do so. I'm going to go ahead and click create new. And now I have the option to create a new network within that resource group.
I'm going to go ahead and close this. I'm going to go ahead and use the network we've already created. Remembering that network, we created a front end and back end subnet. This is a DC so I'm going to pop it into the back end. Next, we have a public IP address. We're going to talk a little bit more about IP addresses little later in the course but for now, I'm going to go ahead and create new and I'm going to leave it as dynamic. Next is our network security group, we're going to cover off network security groups a little later in the course but for now I'm just going to create a basic network security group.
We'll call it test for the time being. And that's it. I am not going to worry about any of the other options at this point. I'm going to go ahead and click ok. Our virtual machine will now be created. It takes about seven minutes or so for a virtual machine to be created within Azure and that's all there is to it. My general rule of thumb when deploying virtual machines into Azure is to create the resource group first then create the network with all of your subnets and then deploy the virtual machines choosing the appropriate network and/or subnet that that virtual machine must sit in.
Again, you can do it on the fly as you create that virtual machine but as I keep saying planning is the key to either implementation and taking the time to plan your virtual networks before deploying your virtual machines will make your implementation go so much easier.
- 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