Create virtual machine inside subnet?

In previous post we have seen, how to create virtual network (VNET) in azure. In this post we will create Virtual Machine inside FrontEnd subnet which is part of DJBlogsVNet VNET. These we have created in last post (What isVPN?). Now will see how many components involved when create VM inside VNET.

As in above example we will create “DJBlogsVM” virtual machine. You have to follow below steps to create it. Go to azure portal  

URL: https://portal.azure.com/

 

Create new resource just click in plus sign as above and search for virtual machine image you want to create. I am using “Microsoft Machine Learning Server 9.3.0 on Windows Server 2016” image for my VM. You can choose based on your requirement, if have selected Standard B1s machine size.

It has below configurations

RAM: 1 GB

vCPUs: 1

Once you click on create button as above it will open below screen for virtual machine basic information’s

 

Click on ok button in next step we need to select the machine image size. Based on our requirement will choose VM size. I have selected B1s as told above.

Once we have selected size then we need to choose virtual machines other settings like

1.       Availability zone

2.       Availability set

3.       Disk Type

4.       Network Security Group

5.       Diagnostics storage account

What is Availability Zone?

Azure Availability Zones are separate data center units within Microsoft Azure, each with its own power, cooling and networking. By running services on multiple availability zones, you can make your applications resilient to failure or disruption in your primary data center.

An Azure Region is a complex of Azure data centers located in a specific geographic location. Azure Region complex of several buildings; typically, each availability zone is in a separate building.

As we have chosen 2 Availability zone for our VM “DJBlogsVM”

 

What is Availability set?

Consisting of logical groups that protect the VMs against hardware failures and also allow back-end updates. To ensure high availability of any cloud hosted application, Azure places VMs in to logical grouping called as Availability set. Availability sets allows workloads to be spread over multiple hosts, racks but remain at the same data center.

An Availability set is a combination of a fault domain and an update domain.

Fault domains

Fault domains define the group of virtual machines that share a common power source and network switch with in same Availability Zone. By default, the virtual machines configured within your availability set are separated across up to three fault domains.

Update domains

Update domains being rebooted may not proceed sequentially during planned maintenance, but only one update domain is rebooted at a time. A rebooted update domain is given 30 minutes to recover before maintenance is initiated on a different update domain.

Disks

Managed disks provide better reliability for Availability Sets by ensuring that the disks of VMs in an Availability Set are sufficiently isolated from each other to avoid single points of failure. It does this by automatically placing the disks in different storage fault domains (storage clusters) and aligning them with the VM fault domain. If a storage fault domain fails due to hardware or software failure, only the VM instance with disks on the storage fault domain fails.

Here is service level agreement (SLA) comparison based on Availability Zone, Availability Set and Disk Type  

We have selected Standard HDD for our VM

After creating our VM “DJBlogsVM_OsDisk_1_af9587d9711c4360b711b35c5ab1db75” this is disk name. It is used by our VM as harddisk as our own computer.

 

Virtual Network

This is virtual network name.Where we want to create our VM. As I told above we will choose “DJBlogsVNet” as VNET for this Virtual Machine and “FrontEnd” as Subnet.  

Now select subnet inside VNET

Public IP Address

We will not select any public IP because it will be inside subnet and it will not be exposed directly to public internet.

Network Security Group

A network security group (NSG) contains a list of security rules that allow or deny network traffic to resources connected to virtual machine.Here we have created “DJBlogsVM-nsg” and it will attached with our VM.

Diagnostics storage account

Azure Monitor that collects monitoring data from the guest operating system of Azure compute resources including virtual machines. It store all collected data into diagnostic storage account.

Once your VM created. You can see it storage account associated with VM by going into VM boot diagnostic settings.

Once you have selected all these options it will validate and show you the summary of all options you have selected as below.

If everything looks good to you check the checkbox and click on create button. It will create VM for us inside targeted subnet.

Hope it will help you to understand how we can create VM side subnet.  

Keep sharing keep learning