In our last 2 examples we saw how to configure Point-To-Site. (Part1, Part2). Now in our current example we are going to create 2 virtual machines within this virtual network. Since I was unable to create a Virtual machine in North Europe region, I had to re-do Part 1 and Part 2 using Location as: West US 2.
Let me walk-through the code on how to Create a Virtual Machine. We will be creating 2 VM’s named,
Select the Size of the VM depending on your needs. I have selected the following,
SETTINGS ( Configure optional features )
- Setting up availability set (Create during 1st VM configuration and re-use it while configuring the 2nd VM).
- Selecting the Virtual Network selected in part 1.
- Select the default subnet created in Part 1
The availability set can only be configured when creating a virtual machine. You must recreate the virtual machine to move it in or out of an availability set.
Availability sets ensure that the VM’s you deploy on Azure are distributed across multiple isolated hardware nodes in a cluster. Doing this ensures that if a hardware or software failure within Azure happens, only a sub-set of your VM’s are impacted and that your overall solution remains available and operational.
Current fault domain
Virtual Machine in the same fault domain share a common power source and physical network switch.
Current update domain
Virtual Machine in the same update domain will be restarted together during planned maintenance. Azure never restarts more than one update domain at a time.
The final step is to Agree to necessary terms and policy and click submit for creation of Virtual machines.
In our next part we would create a Load Balancer with a Public IP address and 2 Virtual Machines in it’s back-end pool. Stay tuned !