Free guides, interview Q&As, and job responsibility breakdowns — curated by industry veterans to help you crack MNC interviews
Azure Virtual Machines are one of the most commonly used services in Microsoft Azure. They allow organizations to create and run virtual computers in the Azure Cloud without purchasing and maintaining physical servers.
An Azure Virtual Machine can run operating systems such as Windows Server, Windows 11, and various Linux distributions. Users can install applications, configure software, and manage the virtual machine according to their requirements.
Azure Virtual Machines are mainly used when an organization needs more control over the operating system, applications, and server configuration.
What is an Azure Virtual Machine?
Definition
An Azure Virtual Machine (VM) is a virtualized computer created and hosted in Microsoft Azure that provides computing resources such as CPU, memory, storage, and networking.
An Azure VM behaves like a physical computer or server, but instead of running on physical hardware owned by the organization, it runs on Azure's cloud infrastructure.
(Azure Virtual Machine एक Virtual Computer होता है जिसे Microsoft Azure के Cloud में बनाया और चलाया जाता है। इसमें CPU, Memory, Storage और Networking जैसी resources उपलब्ध होती हैं। यह एक Physical Computer या Server की तरह काम करता है, लेकिन इसका hardware Azure के Data Centers में होता है।)
Explanation
When an organization creates an Azure Virtual Machine, Azure provides the required computing resources from its cloud infrastructure.
The administrator can select:
After the VM is created, the administrator can connect to it and use it like a normal computer or server.
For example, a Windows Server VM can be created in Azure and used to host applications, run services, or perform administrative tasks.
Example
ABC Technologies needs a Windows Server for running an internal application.
Instead of purchasing a physical server, the company creates a Windows Server Virtual Machine in Azure.
The VM is configured with:
The administrator can then connect to the VM and install the required application.
Azure VM as IaaS
Definition
Azure Virtual Machines are an example of Infrastructure as a Service (IaaS).
IaaS provides virtualized infrastructure such as compute, storage, and networking through the cloud. The cloud provider manages the underlying physical infrastructure, while the customer manages the operating system, applications, and configurations inside the virtual machine.
(IaaS यानी Infrastructure as a Service में Cloud Provider हमें Virtual Infrastructure provide करता है। Azure Physical Hardware और Data Center को manage करता है, जबकि Customer VM के Operating System, Applications और Configuration को manage करता है।)
Explanation
In a traditional data center, an organization needs to purchase and maintain:
With Azure IaaS, organizations can create virtual servers in the cloud without purchasing the physical hardware themselves.
Microsoft manages the underlying Azure infrastructure, while the customer is responsible for the resources and configurations inside the VM.
Responsibility in Azure VM
Microsoft manages:
Customer manages:
Example
Suppose ABC Technologies creates a Windows Server VM in Azure.
Microsoft is responsible for the physical server on which the VM runs.
ABC Technologies is responsible for:
This is why Azure Virtual Machines are considered an IaaS service.
Why Azure Virtual Machines are Used
Azure Virtual Machines provide organizations with flexible and scalable computing resources.
Instead of purchasing a physical server, an organization can create a VM whenever it requires additional computing capacity.
Azure VMs are used because they provide:
Integration with Azure networking and storage services
(Azure VM का उपयोग इसलिए किया जाता है क्योंकि इससे organization अपनी आवश्यकता के अनुसार Cloud में Server बना सकती है। Physical Server खरीदने की आवश्यकता नहीं होती और जरूरत के अनुसार VM की resources को select किया जा सकता है।)
Example
A company needs a temporary server for testing an application.
Instead of purchasing a physical server, the company can create an Azure VM, install the application, perform testing, and remove the VM when it is no longer required.
This provides flexibility and helps avoid unnecessary physical infrastructure.
Common Azure VM Use Cases
Azure Virtual Machines can be used for many different workloads depending on the organization's requirements.
1. Application Hosting
Organizations can host applications on Azure Virtual Machines.
For example, a company can deploy an internal business application on a Windows Server VM.
2. Web Server
An Azure VM can be configured as a web server to host websites or web applications.
For example:
3. Database Server
Azure VMs can be used to run database software when an organization requires control over the operating system and database environment.
For example:
4. Development and Testing
Developers can create VMs for developing and testing applications.
Different VMs can be created for:
This allows development teams to create separate environments for different purposes.
5. Migration of On-Premises Servers
Organizations that are moving their workloads from an on-premises data center to Azure can migrate suitable server workloads to Azure Virtual Machines.
For example, an organization has a physical Windows Server running an application in its data center. The organization can migrate that workload to an Azure VM.
6. Remote Desktop Services
Windows-based Azure VMs can be used for remote desktop scenarios where users need access to a Windows environment from different locations.
7. Disaster Recovery
Azure Virtual Machines can also be part of disaster recovery solutions.
Organizations can use Azure to host or recover workloads when their primary infrastructure becomes unavailable.
8. Specialized Applications
Some applications require specific operating systems, software configurations, or administrative control.
Azure VMs are useful for such workloads because administrators have significant control over the VM environment.
Example
ABC Technologies has the following requirements:
Instead of purchasing four physical servers, the organization can create separate Azure Virtual Machines according to the requirements of each workload.
Real-Life Example
Suppose an organization named ABC Technologies has an application that currently runs on a physical Windows Server.
The company wants to move this application to Azure.
The organization can:
The physical server is replaced by a cloud-based virtual server hosted on Azure.
Key Points to Remember
Azure Virtual Machines are available in different sizes so that organizations can select computing resources according to their workload requirements. Different applications require different amounts of CPU, memory, storage performance, and network capacity.
For example, a small development server may require only a few vCPUs and a limited amount of memory, while a database server may require significantly more memory and processing power. Therefore, selecting the appropriate VM size is important for achieving the required performance while controlling costs.
What are VM Sizes?
Definition
A VM Size defines the amount and type of computing resources available to an Azure Virtual Machine. It determines the processing power, memory, storage capabilities, and networking capabilities available to the VM.
(VM Size का मतलब है कि Azure Virtual Machine को कितनी Computing Resources उपलब्ध कराई जाएंगी। VM Size के आधार पर VM को कितने vCPUs, कितनी Memory, कितनी Storage और कितनी Networking Capacity मिलेगी, यह निर्धारित होता है।)
Explanation
When an administrator creates an Azure VM, one of the important decisions is selecting its size. The selected size provides a specific combination of resources.
A small application may work properly with a smaller VM, while a large database or high-performance application may require a larger or specialized VM. Therefore, VM size should always be selected according to the workload rather than simply choosing the largest available option.
Example
ABC Technologies wants to create a VM for a small internal application. Since the application has low CPU and memory requirements, a smaller VM size may be sufficient. If the application later grows and requires more resources, the administrator can select a more appropriate VM size.
VM Size Categories
Azure provides different VM size categories because different workloads have different resource requirements. The major categories are General Purpose, Compute Optimized, Memory Optimized, Storage Optimized, GPU, and High Performance Computing (HPC).
General Purpose
General Purpose VM sizes provide a balanced combination of CPU, memory, networking, and other computing resources. They are suitable for general workloads that do not have an unusually high requirement for one specific resource.
Common uses:
Example: A company needs a VM to host an internal business application with normal CPU and memory requirements. A General Purpose VM can be suitable for this workload.
Compute Optimized
Compute Optimized VM sizes are designed for workloads that require higher CPU performance compared with memory. They are useful when processing power is the primary requirement.
Common uses:
Example: An application that performs continuous calculations but does not require a large amount of RAM may benefit from a Compute Optimized VM.
Memory Optimized
Memory Optimized VM sizes are designed for workloads that require large amounts of memory. They provide a higher memory-to-CPU ratio and are suitable when RAM is an important factor in application performance.
Common uses:
Example: A database that needs a large amount of RAM for processing frequently accessed data may require a Memory Optimized VM.
Storage Optimized
Storage Optimized VM sizes are designed for workloads that require high storage performance and frequent input/output operations. These workloads continuously read and write large amounts of data.
Common uses:
High-performance databases
Data processing
High disk I/O applications
Storage-intensive workloads
Example: A database performing a large number of read and write operations may require a Storage Optimized VM.
GPU
GPU-enabled VM sizes provide Graphics Processing Units along with CPU resources. GPUs are useful for workloads that require parallel processing and specialized computing.
Common uses:
Artificial Intelligence
Machine Learning
Graphics processing
Video processing
3D rendering
Example: A Machine Learning application that requires GPU acceleration can use a GPU-enabled VM.
High Performance Computing (HPC)
High Performance Computing (HPC) VM sizes are designed for workloads that require very high computational performance. They are generally used for complex calculations and specialized computational workloads.
Common uses:
Scientific simulations
Engineering
Research
Complex calculations
Example: A research organization performing complex scientific calculations may use an HPC VM.
Selecting an Appropriate VM Size
Selecting the correct VM size is an important part of Azure VM deployment. The administrator should understand the workload requirements and select a VM that provides sufficient resources without unnecessary over-provisioning.
A VM that is too small may cause performance problems, while a VM that is much larger than required may increase costs without providing significant benefits.
Example
Suppose ABC Technologies has a small internal application with low CPU and memory requirements. A smaller General Purpose VM may be sufficient.
If the application later receives more users and its resource requirements increase, the administrator can evaluate the workload and select a larger or more appropriate VM size.
Factors for Choosing VM Size
Several factors should be considered before selecting a VM size.
CPU Requirements
CPU requirements should be considered based on how much processing the application performs. CPU-intensive workloads may require more vCPUs or a Compute Optimized VM.
Memory Requirements
Memory requirements are important for databases, analytics, and in-memory applications. Workloads that require large amounts of RAM may benefit from Memory Optimized VMs.
Storage Requirements
The administrator should consider both the amount of storage required and the required disk performance. Applications with frequent read and write operations may require higher storage performance.
Network Requirements
Network requirements should be evaluated for applications that handle large amounts of network traffic. A busy web application, for example, may require higher network capacity than a small internal application.
Workload Type
The workload type helps determine the appropriate VM category:
General application → General Purpose
CPU-intensive workload → Compute Optimized
Memory-intensive workload → Memory Optimized
High disk I/O workload → Storage Optimized
AI/Machine Learning → GPU
Scientific or computational workload → HPC
Application Performance
The expected performance of the application should be considered. If the VM does not provide sufficient resources, the application may become slow or unresponsive during periods of high workload.
Cost
VM size also affects the cost of running the VM. Larger VM sizes provide more resources but generally cost more.
(अगर किसी Application को कम resources की आवश्यकता है, तो बहुत बड़ा VM Size select करने से unnecessary cost बढ़ सकती है। इसलिए VM Size को workload की requirement के अनुसार select करना चाहिए।)
Future Growth
Future workload growth should also be considered. An application may have a small number of users initially but require more resources as usage increases.
The administrator should monitor the workload and adjust the VM size when additional resources are required.
Example: Selecting VM Sizes for Different Workloads
ABC Technologies has three workloads:
Internal Web Application: General Purpose VM
Large Database: Memory Optimized VM
Machine Learning Application: GPU VM
This example shows that there is no single VM size suitable for every workload. The appropriate VM size depends on the CPU, memory, storage, networking, and processing requirements of the application.
Key Points to Remember
VM Size determines the computing resources available to an Azure VM.
Azure provides different VM categories for different workloads.
General Purpose VMs provide a balanced combination of resources.
Compute Optimized VMs are suitable for CPU-intensive workloads.
Memory Optimized VMs are suitable for memory-intensive workloads.
Storage Optimized VMs are suitable for high disk I/O workloads.
GPU VMs are suitable for AI, Machine Learning, graphics, and specialized processing.
HPC VMs are designed for highly computational workloads.
CPU, memory, storage, network, performance, cost, and future growth should be considered when selecting a VM size.
Avoid selecting a VM that is unnecessarily large because it can increase costs.
10.3 Availability Sets
Azure Virtual Machines can be configured for higher availability by placing multiple VMs in an Availability Set. An Availability Set helps protect applications from planned maintenance events and certain hardware failures by distributing VMs across different physical locations within an Azure data center.
Instead of placing all application VMs on the same underlying infrastructure, Azure distributes them across different Fault Domains and Update Domains. This reduces the possibility of all VMs becoming unavailable at the same time.
What is an Availability Set?
Definition
An Availability Set is a logical grouping of Azure Virtual Machines that helps ensure that the VMs are distributed across different fault and update domains.
(Availability Set Azure Virtual Machines का एक logical grouping है, जिसमें VMs को अलग-अलग Fault Domains और Update Domains में distribute किया जाता है ताकि एक ही समय पर सभी VMs के unavailable होने का risk कम हो।)
Explanation
Availability Sets are mainly useful when an application has multiple VMs that need to remain available. For example, an application may have two or more VMs running the same workload.
If all these VMs were running on the same underlying hardware or were updated at the same time, a single failure or maintenance event could affect the entire application.
With an Availability Set, Azure distributes the VMs across different fault and update domains. This helps maintain application availability when planned maintenance or certain hardware failures occur.
Example
ABC Technologies has an application running on two Azure VMs.
Instead of placing both VMs on the same infrastructure, the administrator places them in an Availability Set. Azure distributes the VMs across different fault and update domains.
If one domain is affected, the other VM can continue serving users.
Fault Domains
Definition
A Fault Domain represents a group of virtual machines that share a common source of physical hardware failure.
(Fault Domain का मतलब ऐसे physical infrastructure का group है जिसमें कुछ common hardware components होते हैं। अगर उस infrastructure में hardware failure होता है, तो उस Fault Domain की VMs प्रभावित हो सकती हैं।)
Explanation
Azure uses Fault Domains to reduce the impact of hardware failures.
For example, suppose multiple VMs are running in an Availability Set. Azure can place them in different Fault Domains so that they do not all depend on the same physical hardware.
If a hardware failure affects one Fault Domain, VMs running in other Fault Domains can continue operating.
Example
Suppose an application has three VMs:
VM1 → Fault Domain 1
VM2 → Fault Domain 2
VM3 → Fault Domain 3
If a hardware failure affects Fault Domain 1, VM1 may become unavailable, but VM2 and VM3 can continue running.
Update Domains
Definition
An Update Domain is a logical grouping of VMs that can be restarted or updated together during planned maintenance.
(Update Domain का मतलब VMs का ऐसा logical group है जिसे Azure planned maintenance के दौरान एक साथ update या restart कर सकता है।)
Explanation
Azure periodically performs planned maintenance on its infrastructure. If all VMs of an application were updated or restarted at the same time, the entire application could become unavailable.
Availability Sets distribute VMs across different Update Domains. Azure can then perform maintenance on one Update Domain while VMs in other Update Domains continue running.
Example
Suppose an application has three VMs distributed across different Update Domains.
During planned maintenance, Azure may update one Update Domain at a time. The remaining VMs can continue serving users while maintenance is performed.
This helps reduce application downtime during planned maintenance.
Benefits of Availability Sets
Availability Sets provide several benefits for applications running on multiple Azure VMs.
1. Improved Availability
VMs are distributed across different Fault Domains and Update Domains, reducing the possibility of all VMs becoming unavailable at the same time.
2. Protection from Hardware Failures
Fault Domains help protect applications from certain physical hardware failures by distributing VMs across different physical infrastructure.
3. Reduced Impact of Planned Maintenance
Update Domains allow Azure to perform planned maintenance on groups of VMs separately rather than affecting all VMs at the same time.
4. Support for Multi-VM Applications
Availability Sets are useful when an application requires multiple VMs to provide continuous service.
Example
ABC Technologies has a web application running on three Azure VMs.
The administrator places all three VMs in an Availability Set. Azure distributes them across Fault Domains and Update Domains.
If one physical hardware failure occurs or Azure performs planned maintenance on one Update Domain, the remaining VMs can continue handling application requests.
Therefore, Availability Sets help improve the availability and resilience of multi-VM applications.
10.4 Availability Zones
Azure provides Availability Zones to help organizations design applications that can continue running even if there is a failure affecting part of an Azure region. Availability Zones provide additional protection by placing resources in physically separate locations within the same Azure region.
Availability Zones are especially useful for applications where high availability is important and downtime can have a significant impact on business operations.
What are Availability Zones?
Definition
An Availability Zone is a physically separate location within an Azure region that has its own independent power, cooling, and networking infrastructure.
(Availability Zone Azure Region के अंदर एक physically separate location होती है, जिसकी अपनी independent power, cooling और networking infrastructure होती है।)
Explanation
An Azure region can contain multiple Availability Zones. Each zone is designed to be isolated from failures in the other zones.
For example, if an application has multiple VMs, the VMs can be deployed across different Availability Zones. If one zone experiences a power, cooling, or networking failure, VMs running in other zones can continue operating.
This provides a higher level of protection compared with placing all VMs in the same location.
Example
ABC Technologies runs a critical application using three Azure VMs.
The administrator deploys:
VM1 → Availability Zone 1
VM2 → Availability Zone 2
VM3 → Availability Zone 3
If Availability Zone 1 experiences an infrastructure failure, VM2 and VM3 can continue providing the application service.
Availability Zones vs Availability Sets
Both Availability Sets and Availability Zones are used to improve the availability of Azure Virtual Machines, but they provide protection at different levels.
An Availability Set distributes VMs across different Fault Domains and Update Domains within the Azure data center infrastructure. It mainly helps protect against hardware failures and planned maintenance.
An Availability Zone, on the other hand, places resources in physically separate locations within an Azure region. This provides protection against failures affecting an entire zone.
| Availability Sets | Availability Zones |
| Distribute VMs across Fault Domains and Update Domains | Distribute resources across physically separate zones |
| Protection against certain hardware failures and planned maintenance | Protection against zone-level infrastructure failures |
| VMs remain within the same physical region infrastructure | Zones are separate locations within the same Azure region |
| Suitable for multi-VM applications requiring availability | Suitable for applications requiring higher availability and zone-level protection |
Example
If an application has two VMs in an Availability Set, Azure distributes them across different Fault and Update Domains.
If the application uses Availability Zones, the VMs can be deployed in separate zones, providing greater isolation from infrastructure failures.
Benefits of Availability Zones
Availability Zones provide several benefits for applications that require high availability.
1. Protection from Zone-Level Failures
Because each Availability Zone has independent infrastructure, a failure affecting one zone does not necessarily affect resources running in other zones.
2. Higher Application Availability
Deploying application components across multiple zones can help keep the application available even when one zone becomes unavailable.
3. Independent Infrastructure
Each zone has separate power, cooling, and networking infrastructure, reducing the impact of failures in one location.
4. Support for Business-Critical Applications
Availability Zones are useful for applications where downtime can significantly affect business operations.
Example
Suppose an organization runs a critical online application. If all application servers are deployed in a single zone and that zone becomes unavailable, the application may stop working.
If the servers are distributed across multiple Availability Zones, the remaining servers can continue serving users when one zone is affected.
When to Use Availability Zones
Availability Zones should be considered when an application requires a higher level of availability and protection from zone-level failures.
They are particularly useful for:
Business-critical applications
Production workloads requiring high availability
Applications that cannot tolerate significant downtime
Multi-tier applications
Applications requiring redundancy across separate infrastructure
Example
ABC Technologies runs an important production application that is accessed by customers throughout the day. Even a short outage can affect business operations.
The organization can deploy application components across multiple Availability Zones so that if one zone becomes unavailable, the application can continue operating through resources in other zones.
For a simple development or testing environment where downtime is acceptable, using Availability Zones may not always be necessary.
10.5 Azure Virtual Disks
Azure Virtual Disks provide storage for Azure Virtual Machines. Just like a physical computer or server requires disks to store the operating system, applications, and data, an Azure VM also requires virtual disks for these purposes.
Azure provides different types of disks for different requirements. The main disks associated with an Azure VM are the OS Disk, Data Disk, and Temporary Disk. Each disk has a different purpose and should be used appropriately.
What is an Azure Virtual Disk?
Definition
An Azure Virtual Disk is a virtual storage device used by an Azure Virtual Machine to store the operating system, applications, and data.
(Azure Virtual Disk एक virtual storage device है जिसका उपयोग Azure VM में Operating System, Applications और Data को store करने के लिए किया जाता है।)
Explanation
When an Azure VM is created, Azure provides an OS disk for the operating system. Additional data disks can be attached when more storage is required.
Azure Virtual Disks are managed separately from the VM, which allows administrators to add, remove, or manage storage according to workload requirements.
For example, a Windows Server VM may use one disk for the operating system and an additional data disk for storing application files or business data.
OS Disk
Definition
The OS Disk contains the operating system of the Azure Virtual Machine.
It is created when the VM is deployed and contains the files required to boot and run the operating system.
(OS Disk में Azure VM का Operating System installed होता है। VM इसी disk से boot होकर operating system को run करता है।)
Explanation
For a Windows VM, the OS disk contains the Windows operating system. For a Linux VM, it contains the selected Linux distribution.
The OS disk is essential for the VM because it contains the operating system required for the machine to start and operate.
Example
If ABC Technologies creates a Windows Server VM, the Windows Server operating system is stored on the VM's OS Disk.
Data Disk
Definition
A Data Disk is an additional disk that can be attached to an Azure VM for storing applications and user data.
(Data Disk एक additional disk है जिसे VM से attach करके Applications, Files और User Data को store किया जा सकता है।)
Explanation
The OS disk should generally be used for the operating system, while additional application or business data can be stored on Data Disks.
Multiple data disks can be attached to a VM depending on the VM size and supported limits.
Using separate data disks can help organize application data and provide additional storage capacity.
Example
ABC Technologies has a Windows Server VM running a business application. The operating system is stored on the OS disk, while the application's database files are stored on an attached Data Disk.
Temporary Disk
Definition
A Temporary Disk is storage provided with certain Azure VM sizes that is intended for temporary data and does not provide persistent storage.
(Temporary Disk ऐसी temporary storage होती है जिसका उपयोग temporary data के लिए किया जाता है। इसमें stored data को permanent storage के रूप में rely नहीं करना चाहिए।)
Explanation
The Temporary Disk is commonly used for temporary files, cache, page files, or other data that can be recreated if lost.
The important point to remember is that data stored on the Temporary Disk should not be considered permanent or critical data.
Example
A Windows VM can use the Temporary Disk for temporary system files or page file operations. Important business data should instead be stored on appropriate persistent storage such as the OS Disk or Data Disks.
Disk Performance
Disk performance determines how quickly a VM can read from and write data to its disks. This is particularly important for applications such as databases and data-processing workloads that perform frequent disk operations.
Disk performance can affect the overall performance of an application. Therefore, selecting an appropriate disk type and configuration is important based on the workload.
Important disk performance factors include:
IOPS: Number of input/output operations the disk can perform.
Throughput: Amount of data that can be transferred over a period of time.
Latency: Time required to complete a storage operation.
Example
Suppose ABC Technologies runs a database application that performs thousands of read and write operations. If the storage performance is insufficient, the database may respond slowly even when the VM has sufficient CPU and memory.
Therefore, storage performance should be considered along with CPU and memory when designing an Azure VM.
10.6 Managed Disks
Azure Managed Disks are the default and recommended disk storage option for Azure Virtual Machines. They simplify storage management by allowing Azure to handle the underlying storage infrastructure instead of requiring the administrator to manually manage storage accounts for VM disks.
Managed Disks can be used for OS disks and Data Disks and are available in different performance levels to support different workload requirements.
What are Managed Disks?
Definition
A Managed Disk is a virtual disk in Azure where Azure manages the underlying storage infrastructure, including the storage account management required for the disk.
(Managed Disk एक Azure virtual disk है जिसमें underlying storage infrastructure को Azure खुद manage करता है। Administrator को manually storage accounts manage करने की आवश्यकता नहीं होती।)
Explanation
With Managed Disks, the administrator simply specifies the required disk type and size when creating or attaching a disk. Azure takes care of placing and managing the disk on the underlying storage infrastructure.
Managed Disks can be used as:
OS Disks
Data Disks
They can also be attached to Azure Virtual Machines according to the supported VM configuration.
Example
ABC Technologies creates a Windows Server VM in Azure. The administrator selects a Managed Disk for the OS disk.
Azure automatically handles the underlying storage infrastructure. The administrator does not need to create and manage a separate storage account for the VM disk.
Benefits of Managed Disks
Managed Disks provide several benefits that make VM storage easier to manage.
1. Simplified Management : Azure manages the underlying storage infrastructure, reducing the administrative work required to manage VM disks.
2. Scalability : Managed Disks can be created in different sizes and performance levels according to the workload requirements.
3. High Availability : Azure provides built-in availability and redundancy capabilities for Managed Disks, depending on the selected disk configuration.
4. Security : Managed Disks support Azure security features such as encryption, helping protect data stored on the disks.
5. Backup and Recovery Support :Managed Disks integrate with Azure services and features used for backup, snapshots, and disaster recovery.
Example
Suppose an organization has multiple Azure VMs. With Managed Disks, administrators do not need to manually manage separate storage accounts for each VM's disks. Azure handles the underlying storage, making the environment easier to manage.
Managed Disk Types
Azure provides different Managed Disk types to support different performance and cost requirements.
1. Standard HDD
Standard HDD provides cost-effective storage and is suitable for workloads that do not require high disk performance.
Common uses:
Development and testing
Less frequently accessed workloads
Backup or low-performance applications
2. Standard SSD
Standard SSD provides better performance and lower latency than Standard HDD while remaining suitable for cost-conscious workloads.
Common uses:
Web servers
General applications
Development and testing
3. Premium SSD
Premium SSD provides higher performance and lower latency and is suitable for applications that require faster storage.
Common uses:
Production applications
Databases
Performance-sensitive workloads
4. Premium SSD v2
Premium SSD v2 is designed for workloads requiring high-performance storage with more flexible control over performance characteristics.
It is suitable for demanding workloads such as databases and other performance-sensitive applications.
5. Ultra Disk
Ultra Disk is designed for workloads requiring extremely high disk performance and low latency.
Common uses:
High-performance databases
I/O-intensive applications
Mission-critical workloads
Example
A development VM may work well with Standard SSD, while a production database with high storage requirements may require Premium SSD or another high-performance disk type.
Managed Disks vs Unmanaged Disks
Before Managed Disks were introduced, Azure Virtual Machine disks could be stored as VHD files in Azure Storage Accounts. These were known as Unmanaged Disks.
With Managed Disks, Azure manages the underlying storage infrastructure automatically.
| Managed Disks | Unmanaged Disks |
| Azure manages the underlying storage | Administrator manages storage accounts |
| Easier to manage | Requires more storage management |
| Designed for simpler VM deployment | VHD files are stored in storage accounts |
| Supports different disk types and performance levels | Storage account limits need to be considered |
| Recommended approach for modern Azure VM deployments | Legacy approach |
Example
Suppose ABC Technologies has an older Azure environment where VM disks are stored as VHD files inside storage accounts. The administrators need to manage those storage accounts themselves.
If the organization uses Managed Disks, Azure handles the underlying storage infrastructure, making disk management much simpler.
10.7 Multiple IP Addresses
Azure Virtual Machines use network interfaces to communicate with other resources and services. Normally, a VM can have a private IP address through its network interface, and a public IP address can also be associated when internet access is required.
In some situations, a single IP address is not enough. Azure allows multiple private IP addresses to be configured on a network interface by using multiple IP configurations. This can be useful when a VM needs to host multiple services, applications, or network identities.
IP Addresses in Azure VMs
Definition
An Azure VM communicates through a Network Interface (NIC), which is connected to a subnet in an Azure Virtual Network. The NIC contains IP configurations that define the IP addresses used by the VM.
(Azure VM network के through communicate करने के लिए Network Interface का उपयोग करता है। NIC को Azure Virtual Network के subnet से connect किया जाता है और इसके IP configuration में VM के IP addresses define किए जाते हैं।)
An Azure VM can have:
A private IP address for communication within the Azure network
A public IP address when external connectivity is required
Multiple private IP addresses when additional IP configurations are needed
The private IP address is mainly used for communication with resources such as other VMs, applications, and services inside the virtual network.
Multiple Private IP Addresses
Azure allows multiple private IP addresses to be assigned to a VM through its network interface.
A VM can have a primary private IP address and additional private IP addresses. These addresses are associated with the NIC rather than being directly configured as separate physical network cards.
Example
Suppose ABC Technologies has a Windows Server VM that hosts two different applications.
The administrator can configure:
Primary private IP → Application 1
Secondary private IP → Application 2
Both IP addresses can be associated with the same network interface.
This allows different services or applications to use different IP addresses while running on the same VM.
Multiple IP Configuration on a NIC
Definition
An IP configuration is a configuration on an Azure Network Interface that contains an IP address and related networking information.
A NIC can have multiple IP configurations, allowing multiple private IP addresses to be associated with the same VM.
(NIC पर multiple IP configurations configure करके एक ही VM को multiple private IP addresses दिए जा सकते हैं।)
The first IP configuration is normally the primary IP configuration, while additional configurations can be added as secondary IP configurations.
Example
A VM has one NIC named NIC-VM01.
The administrator can configure:
ipconfig1 → 10.0.1.10
ipconfig2 → 10.0.1.20
ipconfig3 → 10.0.1.30
The VM can then have multiple private IP addresses associated with the same NIC.
The number of IP configurations that can be used depends on the capabilities and limits of the VM size and network interface.
Use Cases for Multiple IP Addresses
Multiple IP addresses can be useful in several situations.
1. Hosting Multiple Applications
A single VM may host multiple applications that need separate IP addresses.
For example, different applications can be associated with different private IP addresses.
2. Network Virtual Appliances
Network appliances or specialized networking workloads may require multiple IP addresses for different network connections or functions.
3. Multiple Services
A VM running multiple services may use additional IP addresses when each service needs a separate network identity.
4. Load Balancing
Multiple IP configurations can be used in certain load-balancing and application deployment scenarios where different IP addresses are required.
5. Network Isolation and Configuration
Additional IP addresses can help configure applications or services that have different networking requirements while running on the same VM.
Example
ABC Technologies runs a VM that hosts a web application and an internal application.
Instead of deploying two separate VMs, the organization can configure multiple private IP addresses on the NIC:
10.0.1.10 → Web application
10.0.1.20 → Internal application
This allows both applications to have separate IP identities while running on the same VM.
10.8 Azure VM Networking
Networking is an important part of an Azure Virtual Machine because a VM needs network connectivity to communicate with other Azure resources, users, applications, and the internet when required.
An Azure VM does not connect directly to the network. It uses a Network Interface (NIC), which is connected to a Subnet, and the subnet is part of an Azure Virtual Network (VNet). IP addresses are then assigned through the network interface to provide communication.
VM and Virtual Network
Definition
An Azure Virtual Network (VNet) is a private network in Azure that provides network connectivity for Azure resources such as Virtual Machines.
(Virtual Network Azure में एक private network है जिसमें Azure VMs और अन्य resources को network connectivity प्रदान की जाती है।)
Explanation
When an Azure VM is created, it is connected to a Virtual Network. The VNet provides the overall network environment in which the VM communicates with other resources.
A VNet can contain multiple subnets, and different VMs can be placed in different subnets according to the organization's network design.
Example
ABC Technologies creates a VNet named ABC-VNet for its Azure environment. The company then deploys its application VMs inside this VNet so that they can communicate with each other and with other Azure services.
VM and Subnet
Definition
A Subnet is a logical division of an Azure Virtual Network used to organize and segment resources within the network.
(Subnet एक Virtual Network का logical division है, जिसका उपयोग network को अलग-अलग segments में divide करने और resources को organize करने के लिए किया जाता है।)
Explanation
A VM is connected to a subnet through its Network Interface. The subnet provides the IP address range from which the VM's private IP address is assigned.
Organizations can create multiple subnets for different purposes, such as separating web servers, application servers, and database servers.
Example
ABC Technologies creates:
Web-Subnet → Web servers
App-Subnet → Application servers
DB-Subnet → Database servers
This provides a logical separation between different workloads within the same Virtual Network.
VM and Network Interface
Definition
A Network Interface (NIC) is the Azure resource that connects a Virtual Machine to a Virtual Network.
(Network Interface या NIC वह Azure resource है जो Virtual Machine को Azure Virtual Network से connect करता है।)
Explanation
The NIC is responsible for the VM's network connectivity. It is associated with a subnet and contains the VM's IP configurations.
Through the NIC, a VM can have:
Private IP address
Public IP address, when required
Multiple IP configurations
Network Security Group association
Example
When ABC Technologies creates a VM, Azure creates or associates a NIC with the VM. The NIC is then connected to the required subnet, allowing the VM to communicate with other resources in the Virtual Network.
Private IP and Public IP
Azure VMs can use Private IP addresses and, when required, Public IP addresses for different types of communication.
Private IP Address
A Private IP is used for communication within the Azure Virtual Network and connected networks.
For example, one VM can communicate with another VM using its private IP address.
Public IP Address
A Public IP provides an externally reachable IP address when a VM needs to communicate with or be accessed from the internet.
For example, a public-facing web server may require a public IP address so that users can access the application from the internet.
(Private IP का उपयोग internal network communication के लिए होता है, जबकि Public IP का उपयोग internet-facing connectivity के लिए किया जा सकता है।)
Example
ABC Technologies has a web server VM.
The VM uses:
Private IP: Communication with application and database servers
Public IP: External users accessing the web application
This allows the VM to communicate both internally and externally according to its requirements.
Network Connectivity for VMs
Azure VMs can communicate with different resources depending on the configured network architecture and security rules.
A VM can communicate with:
Other VMs in the same Virtual Network
Resources in different connected networks
Azure services
On-premises networks through appropriate connectivity
The internet, when required and permitted
Network connectivity is controlled and secured using Azure networking features such as Network Security Groups (NSGs), routing, and network configurations.
Example
Suppose ABC Technologies has a three-tier application:
Web VM → Application VM → Database VM
All three VMs are connected to the appropriate subnets within the Virtual Network. Network rules can then be configured to allow only the required communication between these tiers.
For example, the web server may communicate with the application server, while the database server accepts connections only from the application server.
10.9 Practical Labs
The following practical labs provide hands-on experience with Azure Virtual Machines, disks, and networking. These exercises help understand how to create and configure a VM, attach additional storage, configure multiple IP addresses, and initialize a newly attached disk.
Practical 1: Create Windows VM
Objective
To create a Windows Virtual Machine in Azure and configure its basic settings.
Steps
Sign in to the Azure Portal and open Virtual Machines.
Select Create → Azure Virtual Machine.
In the Basics section, configure the required settings such as:
Azure Subscription
Resource Group
Virtual Machine Name
Region
Availability options
Image
VM Size
Configure the administrator account by providing a username and authentication method.
Configure the required networking settings, including the Virtual Network, Subnet, and Public IP.
Review the configuration and select Create to deploy the VM.
After deployment is completed, open the VM and verify that its status is Running.
Connect to the Windows VM using RDP (Remote Desktop Protocol) and verify that the Windows operating system is working correctly.
Learning Outcome
After completing this lab, you should be able to create a Windows VM in Azure and configure its basic compute, storage, and networking settings.
Practical 2: Attach Data Disk
Objective
To create and attach an additional Data Disk to an existing Azure Virtual Machine.
Steps
Open the Azure Portal and navigate to the required Virtual Machine.
Under Settings, open Disks.
Select Create and attach a new disk.
Provide the required disk name, disk type, and size.
Save the configuration to attach the disk to the VM.
Connect to the Windows VM and open Disk Management.
Locate the newly attached disk. It may initially appear as Offline or Uninitialized.
Bring the disk Online and initialize it.
Create a new volume and assign a drive letter.
Format the volume using the required file system.
Learning Outcome
After completing this lab, you should be able to create and attach a Data Disk to an Azure VM and make the disk available for storing data.
Practical 3: Configure Multiple IP Addresses
Objective
To configure multiple private IP addresses on an Azure VM by adding multiple IP configurations to its Network Interface.
Steps
Open the Azure Portal and navigate to the VM.
Open the VM's Networking settings.
Select the associated Network Interface (NIC).
Open IP configurations under the NIC settings.
Select Add to create an additional IP configuration.
Provide a name for the new IP configuration.
Select the required private IP allocation method and assign a private IP address.
Save the configuration.
Repeat the process if additional private IP addresses are required.
Connect to the VM and verify the configured IP addresses.
Example
A VM has the following IP configurations:
Primary IP → 10.0.1.10
Secondary IP → 10.0.1.20
Secondary IP → 10.0.1.30
All these private IP addresses are associated with the same Network Interface.
Learning Outcome
After completing this lab, you should be able to add multiple IP configurations to a NIC and assign multiple private IP addresses to an Azure VM.
Practical 4: Disk Initialization
Objective
To initialize a newly attached Data Disk, create a volume, format it, and verify that it is available inside the Windows VM.
Steps
Connect to the Windows VM using RDP.
Open Disk Management by using:
Right-click Start → Disk Management
Locate the newly attached disk.
If the disk is offline, bring it Online.
Right-click the uninitialized disk and select Initialize Disk.
Select the appropriate partition style, such as GPT, and initialize the disk.
Right-click the unallocated space and select New Simple Volume.
Specify the volume size and assign a drive letter.
Format the volume using NTFS and provide a suitable volume label.
Open File Explorer and verify that the newly created drive is visible.
Create a test file or folder on the new drive to confirm that the disk is working correctly.
Learning Outcome
After completing this lab, you should be able to initialize a newly attached disk, create a volume, format it, assign a drive letter, and verify the disk from inside the Windows VM.
10.10 Azure VM Best Practices
When deploying and managing Azure Virtual Machines, following best practices helps maintain performance, availability, security, and cost efficiency. VM configuration should be based on the workload requirements rather than using the same configuration for every application.
Select VM Size According to Workload
The VM size should be selected according to the application's CPU, memory, storage, and network requirements. A small application may require a smaller General Purpose VM, while a database or CPU-intensive workload may require a specialized VM size.
Before selecting a size, consider:
CPU and memory requirements
Application workload
Expected network traffic
Current and future resource requirements
Selecting the appropriate size helps maintain performance without unnecessarily increasing costs.
Use Appropriate Disk Types
The disk type should be selected according to the workload's storage and performance requirements. Different applications may require different levels of IOPS, throughput, and latency.
For example, a development environment may work with a Standard SSD, while a performance-sensitive production database may require Premium SSD or another high-performance disk type.
(Disk type हमेशा workload की requirement के अनुसार select करना चाहिए। High-performance applications के लिए higher-performance disks की आवश्यकता हो सकती है।)
Plan Availability Requirements
Availability requirements should be considered before deploying production VMs. Critical applications may require additional protection against hardware failures, planned maintenance, or zone-level failures.
Azure provides options such as Availability Sets and Availability Zones to improve VM availability.
For example:
Less critical workload → Basic availability design may be sufficient
Multi-VM application → Availability Set can be considered
Business-critical workload → Availability Zones may be appropriate
The availability design should match the application's business requirements and acceptable downtime.
Secure VM Network Access
VM network access should be restricted to only the traffic that is actually required. Unnecessary exposure of management ports or application ports can increase security risks.
Security measures can include:
Use Network Security Groups (NSGs)
Allow only required ports
Restrict administrative access
Avoid unnecessary public IP exposure
Use secure remote-access methods
For example, instead of allowing Remote Desktop access from any internet address, access can be restricted to trusted sources or secured through appropriate network connectivity.
Monitor VM Performance
VM performance should be monitored regularly to identify resource bottlenecks and determine whether the selected VM size is appropriate.
Important resources to monitor include:
CPU utilization
Memory usage
Disk I/O
Network activity
Application performance
Monitoring helps identify situations where a VM is under-provisioned or where resources are being unnecessarily allocated.
Example
If a VM regularly reaches very high CPU utilization, the administrator can investigate the workload and consider resizing the VM if additional CPU resources are required.
Avoid Unnecessary Resource Usage
Azure resources should be used efficiently to avoid unnecessary costs. Administrators should regularly review VM sizes, disks, IP addresses, and other associated resources.
For example, a VM that consistently uses only a small portion of its available CPU and memory may be oversized. The administrator can evaluate whether a smaller VM size would provide sufficient performance.
Similarly, unused development or testing VMs can be stopped when they are not required.
(Unnecessary resources को continuously running रखने से Azure cost बढ़ सकती है। इसलिए resources को regularly review और optimize करना चाहिए।)
