Microsoft Azure is a cloud computing service developed by Microsoft in the early 2000s. It is used to manage, test, build, and deploy applications via Microsoft’s very own datacenters. It offers various services, such as SaaS (Software as a service), IaaS (Infrastructure as a service), and PaaS (Platform as a service).
Now that we are familiar with what Microsoft Azure is, we will explore the different types of virtual machines and provide a step-by-step guide to Azure Virtual Machine learning.
Table of Contents
- Azure Virtual Machine
- Different Types of Azure Virtual Machines
- Why Use Virtual Machines?
- Step-by-Step Guide to Azure Virtual Machine
Azure Virtual Machine
Azure Virtual Machine is one of the most sought-after virtual machines or computing resources created by Microsoft Azure. It is based on the IaaS and enables the users to get more control over the environment to help them customize the hosting.
Azure Virtual Machine is a vital part of hardware visualization. These machines are pre-made systems designed on the basis of visualization concepts. The concept behind Azure Virtual Machine is the same as cloud platform visualization. One of the main benefits of using Azure VM or Azure Virtual Machine is that the users can open and shut down whenever they like. It provides an ample amount of visualization flexibility without having to use the maintenance of physical hardware.
However, users have to configure, patch, and install applications that run on it. Also, users can create SQL databases, directory domain services, Linux virtual machines, application services, and so on. Now you might be thinking about Azure virtual machine types.
Different Types of Azure Virtual Machines
Here are the different types of Azure Virtual Machines:
This type of VM has a high memory-to-CPU ratio. It is great for medium-traffic web servers, application servers, and network equipment.
General purpose boasts a balanced memory-to-CPU ratio. It is mostly suitable for the deployment of databases from small or medium.
This VM possesses high IO and disk throughput, which is excellent for NoSQL databases, Big Data, SQL, big transactional databases, and data warehousing.
This type of VM leans towards a high memory-to-CPU ratio. It is ideal for medium-to-large caches, memory analytics, and relational database servers.
These VMs are the most powerful and the fastest VMs that are equipped with RDMA (high-throughput network interfaces).
It is a type of VM that is specialized and targets video editing and heavy graphics rendering. It can also be used for differencing with deep learning and modern training. The users can either have multiple GPUs or a single one.
In the world of cloud computing, the workload is the amount of processing time that a computer gives to complete a certain task. The workload has application programs processing in the computers. Some users connect and interact with the computer’s applications as well. The workload in the Azure Virtual Machine is divided into two categories.
The services or applications not suitable for Azure VM workload IaaS are:
- Controlled environment workloads that are unable to move to the cloud due to the rules
- Small businesses that can run the service at a lesser cost compared to using the cloud
The services and applications suitable for Azure VM workloads are:
- Workloads such as online commercial stores
- Businesses with an unpredictable growth rate, such as a short-term increase in sales and development in the organization
- Workloads for retail sales in festival holidays
Why Use Virtual Machines?
Virtual machines are used so that you can operate many operating systems at the same time from a single piece of hardware. Without virtualization, users wanting to work on different operating systems like Linux and Windows would have to operate them from two separate physical units. Here is an example:
David works as a freelancer and designs computer games. One of his clients wants the game to be able to run on all operating systems like Windows, Ubuntu, and macOS. However, David only has one PC that runs on Windows. He will need Ubuntu and Windows to test the game. Instead of getting two separate physical units, he chooses Virtual Machines as an option. He can now deploy two VMs for each system to test his game. Once the game is tested, the client is happy, and so is David.
Another example is related to operating systems. If David’s client wants a high-end game requiring a lot of power that his computer can’t handle, he has two options. He can buy a new PC, upgrade the existing one, or he could create a virtual machine to help him with the computing power. The cost will be lower, and it will be much more effective compared to buying a new PC. He can decrease or increase computing power or memory anytime he likes.
Azure Virtual Network or VNet is where your network is represented in the cloud platform. It allows different types of resources, such as Azure VM, to communicate effectively with each other, the internet, and network more securely. It functions as a highly secure and isolated environment to run the applications and machines. Here are some features of VNet.
- When you launch instances, Azure VM can access the internet
- You can access specific resources
- All the networks work independently
- You can divide virtual networks into segments
- Configuration of the virtual network can be done to use your DNA servers
- Resources fall under the umbrella of Azure VNet and can communicate with each other with the help of IP addresses, regardless of being from different subnets.
- They offer routing between on-premise networks and subnets, so you don’t have to manage or configure the routes.
Filtering the Traffic
- Network traffic is filtered from resources by port and source IP address
Any resource can connect with each other, and a virtual network can communicate with resources in other VNets.
This means the VNet can connect to a network on-premise and enable the resources to interact with each other.
You can override routing by configuring Azure VM with your own routes or by generating BGP routes via a network gateway. It is responsible for routing the traffic. A route table for subnets is automatically created within Azure VNet, and system default routes are added.
Azure Virtual Network Subnet
Azure VNet subnets divide the virtual network into small IPs to ensure the resources organized in these subnets are separated logically. Each subnet consists of a range of IP addresses that has a subset of virtual network space.
Network Security Group
These groups function as a firewall that limits and monitors network traffic. They also consist of a range of security rules that deny or allow outbound or inbound network traffic based on the destination or source of IP addresses, protocol, and port. The security rules apply to all the resources in the subnet.
Step-by-Step Guide to Azure Virtual Machine
Now that we have explored the basics, let’s move on to our step-by-step guide to Azure Virtual Machine. This guide will help you with the step and deployment of VM in Azure.
Step # 1
The first step involves the process of setting up an Azure Virtual Machine. You would need to log into the management portal via www.portal.azure.com. Make sure you have an Azure subscription so you can use the portal. If you don’t have a subscription, you can easily sign up for a free trial.
After signing up and logging into the account, go to the “Navigation” section and click “New.” After that, click “Marketplace” and then “Compute.”
Step # 2
You will see the “Virtual Machines Marketplace” tab. This is where you will find different VM pre-configured images and configurations. The images in the tab will consist of official images from ISVs, Microsoft partners, and Microsoft. You can find images from selected partners like Red Hat or Canonical. The images are used for Windows-based deployments only.
Select the image you like from the various options. For instance, if you create an Azure VM using Windows Server 2016, after choosing the image, you would be able to see all the information related to Windows Server 2016 image.
Now, it’s time for you to choose a suitable deployment model. Let’s use the example of Windows Server 2016. The recommended deployment model for Windows Servers 2016 is “Resource Manager.” Select “Resource Manager” after clicking on “Select a deployment model.”
Once that is done, click “Create,” which will initiate the process of Azure Virtual Machine creation.
After following the steps to deploy a virtual machine, the next steps cover the configuration of settings for Azure VM.
Step # 3
This step involves creating a virtual machine. Click on the “Create Virtual Machine” tab. You will find four tabs on the left side of your screen, “Basics,” “Size,” “Settings,” and “Summary.”
Let’s start with the Basics
This is the first configuration. In this configuration, you must provide all the important details about the VM you want to create, such as:
- VM disk type
- Name of VM
- User name of the administrator
- Password for the admin user
- The subscription that you want to use
- Resource group to get a logical container for Azure resources
There will be two options in the field “Create new” and “Use existing.” You can choose which one is applicable in your case. This field is important for the management of resources on your VM.
The final entry in the basics setting is adding the location of the Azure region. The virtual machine would be placed in that location.
Once all the fields are filled up, click “Ok.” You will be moved to the next tab, which will include:
This tab helps the user configure the Azure Virtual Machine size. There will be various VM size options depending on your basic configurations. It is essential to remember that not all VM sizes will be available, in all Azure regions. If a particular size of VM isn’t available the size option is automatically disabled. This section will consist of the description of minimum memory and vCPU for VM. The most important information you will find in this section is the estimated monthly cost of the size of the VM. Once all the options have been reviewed, proceed to select the right one by clicking on “Select.”
After selecting the size of the VM, go on to the next tab, which is “Settings.” This tab will allow you to configure settings for availability, networking, storage, and monitoring.
This is how you will configure each setting:
- Availability Set
Configuring availability is an important step when it comes to creating a VM in Azure. In the “Settings” tab you will be given an option to choose “Availability Set.” You can choose the Availability Set as an option if you want. It will help you determine the availability set for placing a VM. However, it is important to note that the configuration can’t be changed once the VM is created.
This setting is for your Azure Virtual Machine storage. Here, you will have to choose storage for the OS disk in the VM. You will find two options, “Managed Disks,” and the second is “Storage Account.”
The first option, Managed Disks, helps in managing the storage account which simplifies disk management on IaaS virtual machines.
The second option, “Storage Account,” is typically selected for placing the OS disk. Depending on which option suits you the best, you can choose either a new storage account or an existing one.
Setting up the Network is the next step in Azure Virtual Machine. In this section, you have to choose the “Subnet,” “Network Security Group,” “Virtual Network” type and “Public IP Address.” In the “Virtual Network” section, you can either create a new VNet or choose an existing one. After that, select the subnet you want your VM to be placed on. Now, it’s time to choose the “Public IP address.” You have the option of creating a new public IP address or choosing “None” to obtain a publicly accessible IP address. In the “Network Security Group,” you will configure the outbound and inbound firewall rules to control the traffic. The default “Network Security Group” for Windows is Remote Desktop Protocol or RDP and SSH in Linux.
The last step in the configuration of your Azure VM is “Monitoring.” This option is the “Settings” tab that gives you three monitoring configurations to choose from: “Boot Diagnostics,” “Guest OS Diagnostics,” and lastly, “Diagnostics Storage Account.” The “Boost Diagnostics” option allows you to view the console output and take screenshots. In the “Guest OS Diagnostics,” you disable or enable the Guest OS Diagnostic metrics for the VM. It helps you stay updated on applications and create alerts. The last element of the monitoring settings is “Diagnostics Storage Account”. In this, you have the option of either creating a new or choosing an existing Azure storage account. This is where the diagnostic metrics will be written.
After selecting the appropriate configuration for “Settings,” you click “OK.”
Step # 4
To create the VM, accept the terms and conditions and then click “Create.” The deployment process will be initiated immediately. Keep in mind, the VM will take a few minutes before it is ready to use. You would be able to find the status on the notification board.
Check out the complete steps with screen shots on How to Create Azure VM (Virtual Machine).
You may also like following the below Articles
- How to reset password in Azure virtual machine
- How to enable Azure virtual machine encryption
- Azure virtual machine auto shutdown
- How to remove an Azure Virtual Machine (VM)
- How to access Azure VM (Virtual Machine)
- How to Create Azure Free Account (Step by Step tutorial)
- How To Create Azure Windows Virtual Machine From A Snapshot PowerShell
In conclusion, the process of creating an Azure Virtual Machine is not difficult. We hope the step-by-step guide to Azure Virtual Machine above proves helpful. We have reflected on various factors that need to be considered when setting up the VM. The steps required to successfully create an Azure VM highlighted in this article will ensure you have all the details down to a tee.