Azure Virtual Machine is a great tool for migrating mission-critical and business-critical workloads to Azure infrastructure. It also helps improve operational efficiency. These are just a few of the many types of scalable, on-demand computing resources that Azure offers. VM’s are often needed when we need more control over our computing environment.
Azure VM also allows virtualization without the need to purchase and maintain the physical hardware. It is essential to maintain the VM by performing tasks such as configuring, patching and installing the software. Azure virtual machines can be used for many purposes:
Firstly, Development and testing
Second, Applications in the Cloud
Let’s get to the point. In this blog, we’ll learn how to create an Azure Portal virtual machine. Before we get started, let’s first understand what you need to know before creating a VM.
Before creating a VM, here are some things to consider:
When creating an Azure application infrastructure, there are many design considerations. These aspects of a VM should be considered before you start:
Things to Consider1. Consider the location
All Azure resources are distributed across multiple geographic regions worldwide. When you create a VM, the region is called the location. The location is what determines where virtual hard disks will be stored for a VM. Here are some ways to find a list of locations.
Azure portalSelecting a place from the list when creating a VM.
Azure PowerShellUsing Get-AzLocation
REST APIUsing List locations operation.
Azure CLI Using the az-account list-locations operation.
Azure offers a 99.9% industry-leading single-instance virtual machine Service Level Agreement for deploying VMs with premium storage for all drives. To qualify for the 99.95% VM Service Level Agreement, you must deploy at least two VMs to run your workload within an availability set. An availability set ensures that your VMs are distributed across multiple fault domains within the Azure data centers. It also allows for deployment onto hosts with different maintenance windows.
3. VM size
The workload you run will determine the size of the VM you use. The size you choose will affect factors such as storage capacity, memory, processing power, and memory. Azure supports many different types of uses and offers many sizes.
Azure charges an hourly rate depending on the VM’s operating system and size. Azure charges for partial hours only, and not for the actual minutes used. Storage is charged separately and priced.
4. VM Limits
There are default quota limits that can be applied to your subscription. This could limit the deployment of many VMs to your project. The current limit per subscription is 20 VMs for each region. You can request an increase by submitting a support ticket.
Images and operating system disks:
Virtual machines use virtual hard drives (VHDs), which are used to store operating systems (OS), and data. VHDs can also be used to store the images that you can choose from when installing an OS. Azure also offers many marketplace images that can be used with different versions and types Windows Server operating systems. Images from the Marketplace are identified by their image publisher, offer, SKU and version.
VM extensions give VM additional capabilities via post-deployment configurations and automated tasks. Extensions can be used to accomplish these common tasks:
First, running custom scripts. The Custom Script Extension allows you to configure workloads on a VM by running scripts when the VM has been provisioned.
Secondly, Configuration deployment and management. The PowerShell Desired State Configuration Extension (DSC) helps you set up DSC on a VM