Free guides, interview Q&As, and job responsibility breakdowns — curated by industry veterans to help you crack MNC interviews
Azure Virtual Networking provides the basic networking foundation for resources running in Microsoft Azure. It allows resources such as Virtual Machines, databases, application servers, and other Azure services to communicate with each other and with external networks in a controlled and secure manner.
What is Azure Virtual Network (VNet)?
Definition
An Azure Virtual Network (VNet) is a logically isolated virtual network in Microsoft Azure that enables Azure resources to communicate securely with each other, the Internet, and on-premises networks.
(Azure Virtual Network (VNet) Azure में बनाया गया एक Virtual Network है, जिसमें Azure के अलग-अलग Resources को आपस में सुरक्षित तरीके से जोड़ा जा सकता है। यह Network Resources के बीच Communication को नियंत्रित करने और उन्हें Internet या On-Premises Network से जोड़ने में भी मदद करता है।)
Explanation
A VNet works similar to a traditional network in an organization, but instead of physical switches, routers, and cables, the network is created and managed using Azure.
When you create a VNet, you define an IP Address Space for the network. You can then divide this address space into smaller Subnets.
Azure resources can be connected to these Subnets and communicate using Private IP Addresses.
For example, an organization can create separate Subnets for:
This allows the organization to organize its network and control communication between different parts of an application.
Main Components of a VNet
Example
A company creates a VNet with the address space:
Web servers are placed in the Web Subnet, application servers in the Application Subnet, and databases in the Database Subnet.
Why Azure Virtual Networks are Used
Definition
Azure Virtual Networks are used to provide secure, controlled, and isolated network connectivity for Azure resources.
(Azure में अलग-अलग Resources के बीच सुरक्षित Network Communication बनाने और यह नियंत्रित करने के लिए कि कौन-सा Resource किससे communicate कर सकता है, VNet का उपयोग किया जाता है।)
Explanation
When organizations deploy applications in Azure, their resources need to communicate with each other.
For example: User Web Server Application Server Database
The Web Server needs to communicate with the Application Server, and the Application Server needs to communicate with the Database.
A VNet provides the network environment required for this communication.
It also allows administrators to control which resources can communicate with each other and how traffic enters or leaves the network.
Common Uses of Azure VNet :-
1. Connecting Azure Resources : Virtual Machines, databases, and application services can communicate through a VNet.
2. Network Isolation : Resources can be placed inside a private network instead of exposing everything directly to the Internet.
3. Network Segmentation : The VNet can be divided into multiple Subnets according to the requirements of the application.
4. Internet Connectivity : Resources can be provided controlled access to the Internet when required.
5. On-Premises Connectivity : An Azure VNet can be connected to an organization's On-Premises Network using technologies such as VPN Gateway or ExpressRoute.
6. Traffic Control : Network traffic can be controlled using Network Security Groups (NSGs) and routing.
Benefits of Azure Virtual Network
1. Network Isolation
A VNet provides a logically isolated network environment for Azure resources.
This helps organizations keep their resources separated from other networks and control how they communicate.
(VNet Azure Resources के लिए एक अलग Network Environment प्रदान करता है, जिससे Resources को व्यवस्थित और सुरक्षित तरीके से रखा जा सकता है।)
2. Secure Communication
Resources within a VNet can communicate using Private IP Addresses.
For example, an application server can communicate with a database using its private IP without exposing the database directly to the Internet.
(Private IP की सहायता से Resources आपस में सीधे Internet के माध्यम से जुड़े बिना communicate कर सकते हैं। इससे Communication अधिक सुरक्षित रहता है।)
3. Network Segmentation
A VNet can be divided into multiple Subnets.
Different types of resources can be placed in different Subnets.
For example:
4. Traffic Control
Azure provides networking features such as Network Security Groups (NSGs) that allow administrators to control network traffic.
For example, an administrator can allow HTTP traffic to a Web Server while blocking unnecessary traffic.
(Network Traffic को नियमों के अनुसार allow या block किया जा सकता है। इससे केवल आवश्यक Communication को अनुमति दी जाती है।)
5. Connectivity with On-Premises Networks
Azure VNets can connect cloud resources with an organization's existing On-Premises Network.
For example, a company may keep its Active Directory servers in its office while running application servers in Azure.
The VNet can provide connectivity between these environments.
6. Scalability
VNets can support applications as they grow.
Organizations can create additional Subnets and connect additional resources according to their requirements.
(Scalability का मतलब है कि Application या Network के बढ़ने पर उसमें नए Resources और Network Components को जोड़ना आसान होना।)
7. Flexible Network Design
Administrators can design the VNet according to application requirements by selecting appropriate:
This allows organizations to build different network architectures for different applications.
Example of Azure Virtual Network
Suppose an organization is hosting an online shopping application in Azure.
It creates one VNet with three Subnets:
All these resources are connected through the Azure VNet, while network security rules control which communication is allowed between them.
Azure VNet and Traditional Network
| Traditional Network | Azure VNet |
| Physical network | Virtual network |
| Physical switches and routers | Azure-managed networking |
| Physical servers | Azure resources |
| Physical network segments | Subnets |
| Physical network security | NSGs and other Azure security features |
| Private IP addressing | Private IP addressing |
The basic networking concepts remain similar, but Azure provides the infrastructure and networking components as cloud services.
An Azure VNet uses IP Addressing to identify resources and organize network communication. The VNet has an overall Address Space, which can be divided into smaller Subnets according to the requirements of the application.
What is an IP Address?
Definition
An IP Address (Internet Protocol Address) is a numerical address used to identify a device or network interface on a network and allow it to communicate with other devices.
Explanation
When Azure resources such as Virtual Machines communicate with each other, they need IP Addresses to identify the source and destination of network traffic.
In Azure, a resource connected to a VNet can have a Private IP Address.
For example: Web VM → 10.0.1.4
Here, 10.0.1.4 identifies the VM within the private network.
Example : Suppose a company has three VMs:
| Resource | Private IP |
| Web VM | 10.0.1.4 |
| Application VM | 10.0.2.4 |
| Database VM | 10.0.3.4 |
Each resource has an IP Address that can be used for network communication.
IP Address Network में किसी Resource या Network Interface की पहचान करने के लिए इस्तेमाल होने वाला Address है। इसके माध्यम से Network को पता चलता है कि Traffic कहाँ से आ रहा है और कहाँ जाना है।
What is Address Space?
Definition
An Address Space is the range of IP Addresses available for a network.
In Azure, when creating a VNet, you define an IP Address Space that determines which IP Address ranges can be used inside that VNet.
Explanation
Azure can have multiple Virtual Networks (VNets), and each VNet can have one or more Address Spaces. These Address Spaces are divided into smaller Subnets.
VNet A
Address Spaces: 10.1.0.0/16, 10.0.0.0/16
Subnets:
VNet B
Address Space: 10.2.0.0/16
Subnets:
VNet C
Address Spaces: 10.1.0.0/16, 10.6.0.0/16
Subnets:
Explanation
The diagram shows that an Azure VNet can have one or more Address Spaces, and each Address Space can be divided into smaller Subnets.
For example, VNet B has the Address Space 10.2.0.0/16. This Address Space is divided into:
Similarly, VNet A and VNet C contain multiple Address Spaces and Subnets.
Address Space VNet के लिए available IP range होता है। इस range को छोटे network segments यानी Subnets में divide किया जाता है।
What is a Subnet?
Definition
A Subnet is a smaller network segment created within an Azure VNet Address Space.
Explanation
A Subnet divides the VNet into smaller logical sections. Different types of Azure resources can be placed in different Subnets according to their requirements.
For example:
| Subnet | Purpose |
| Web Subnet | Web Servers |
| Application Subnet | Application Servers |
| Database Subnet | Database Resources |
This makes the network easier to organize and allows different security and routing requirements to be applied.
Example :
If the VNet has: 10.0.0.0/16
It can contain:
Subnet VNet का एक छोटा network section है। बड़े VNet को अलग-अलग काम के अनुसार छोटे हिस्सों में divide करने के लिए Subnet का उपयोग किया जाता है।
VNet Address Space vs Subnet
The VNet Address Space is the overall IP range of the VNet, while a Subnet is a smaller IP range taken from that Address Space.
| VNet Address Space | Subnet |
| Defines the overall IP range of the VNet | Defines a smaller network range inside the VNet |
| Larger network range | Smaller network segment |
| Contains multiple Subnets | Contains Azure resources |
| Example: 10.0.0.0/16 | Example: 10.0.1.0/24 |
| Defines the network's available address range | Organizes resources into separate network sections |
Simple Example
Think of a VNet as a large building and Subnets as different departments inside that building.
Azure VNet
The VNet Address Space is the overall network, while each Subnet represents a smaller section of that network.
Creating Multiple Subnets
Definition
Creating Multiple Subnets means dividing a VNet's Address Space into multiple smaller network segments for different resources or application components.
Explanation
When designing an Azure network, it is common to create separate Subnets for different parts of an application.
For example, an organization can create:
| Subnet | Address Range | Resources |
| Web Subnet | 10.0.1.0/24 | Web Servers |
| Application Subnet | 10.0.2.0/24 | Application Servers |
| Database Subnet | 10.0.3.0/24 | Database |
Why Create Multiple Subnets?
To make network management easier.
एक ही VNet में अलग-अलग प्रकार के Resources को अलग रखने के लिए Multiple Subnets बनाए जाते हैं। जैसे Web Servers, Application Servers, और Database Servers को अलग-अलग Subnets में रखा जा सकता है।
Example: Complete VNet Address Structure
Suppose an organization creates a VNet:
It creates three Subnets:
| Network | Address Range | Purpose |
| VNet | 10.0.0.0/16 | Overall network |
| Web Subnet | 10.0.1.0/24 | Web Servers |
| Application Subnet | 10.0.2.0/24 | Application Servers |
| Database Subnet | 10.0.3.0/24 | Database |
The structure can be understood as: VNet Address Space → Subnets → Azure Resources
This approach allows the organization to create a well-organized and manageable Azure network.
IP Addresses are used to identify Azure resources and enable network communication. Azure resources can use Public IP or Private IP depending on their connectivity requirements.
What is a Public IP Address?
Definition
A Public IP Address is an IP address used to provide connectivity between an Azure resource and the public Internet.
Explanation
A Public IP can be associated with supported Azure resources that need Internet-facing connectivity. External users or systems can reach the resource when the required network and security rules allow access.
Example: A Web Server hosting a public website can use a Public IP.
Public IP का उपयोग तब किया जाता है जब किसी Azure Resource को Internet से connect या access करना हो।
What is a Private IP Address?
Definition
A Private IP Address is an IP address used for communication within a private network, such as an Azure VNet.
Explanation
Private IPs are assigned to resources connected to a VNet and are commonly used for communication between Azure resources.
Example: An Application Server can communicate with a Database Server using the Database's Private IP.
Private IP का उपयोग मुख्य रूप से VNet के अंदर Resources के बीच communication के लिए किया जाता है।
Public IP vs Private IP
| Public IP | Private IP |
| Used for Internet connectivity | Used for private network communication |
| Used by public-facing services | Used mainly by internal resources |
| Can be reachable from the Internet when access is allowed | Not directly reachable from the public Internet |
| Example: 20.50.10.25 | Example: 10.0.1.4 |
When Public and Private IPs are Used
Public IP
Used when a resource needs public Internet connectivity.
Private IP
Used when communication should remain within a private network.
Example
A Web Server may use both Public and Private IP:
| Communication | IP Used |
| Internet User → Web Server | Public IP |
| Web Server → Database | Private IP |
A Network Interface Card (NIC) is an important networking component that connects a computer or Virtual Machine to a network. In Azure, a Network Interface (NIC) connects an Azure Virtual Machine to a Virtual Network (VNet) and provides network connectivity.
What is a Network Interface Card (NIC)?
Definition
A Network Interface Card (NIC) is a hardware or virtual networking component that allows a computer or server to connect to a network and communicate with other devices.
Explanation
In a physical computer, a NIC is usually a physical network adapter that connects the computer to a wired or wireless network.
In Azure, networking is virtualized. Therefore, Azure uses a Virtual Network Interface Card (vNIC), commonly called a Network Interface (NIC), to connect resources such as Virtual Machines to a VNet.
A NIC acts as the connection point between the Virtual Machine and the Azure Virtual Network.
NIC किसी computer या Virtual Machine को Network से connect करने का काम करता है। Azure में NIC एक Virtual Network Interface होता है, जो VM को VNet और Subnet से जोड़ता है।
NIC in Azure
Definition
An Azure Network Interface (NIC) is a virtual networking component that connects an Azure Virtual Machine to a Subnet within a Virtual Network.
Explanation
When an Azure VM is created, a NIC is normally created and attached to the VM. The NIC connects the VM to a specific Subnet and provides the networking information required for communication.
The NIC can be associated with:
This means the VM uses the NIC to communicate with the network.
Components of an Azure NIC
An Azure NIC contains or can be associated with several important networking components.
1. Virtual Network : The NIC must be connected to a VNet through a Subnet.
2. Subnet : The NIC is connected to a specific Subnet within the VNet.
3. Private IP Address : The NIC receives a Private IP Address from the Subnet's IP Address range. This is commonly used for communication inside the VNet.
4. Public IP Address : A Public IP Address can be associated with the NIC when the VM needs Internet-facing connectivity.
5. Network Security Group (NSG) : An NSG can be associated with the NIC to control Inbound and Outbound Network Traffic according to security rules.
6. IP Configuration : The NIC contains IP configuration information, such as the Private IP and, when required, Public IP association.
NIC and Azure Virtual Machine
A NIC is essential for providing network connectivity to an Azure Virtual Machine.
When a VM is created, its NIC connects it to the selected VNet and Subnet.
Example
Suppose a company creates:
The relationship is:
| Component | Example |
| Virtual Machine | Web-VM |
| NIC | Web-VM-NIC |
| VNet | Production-VNet |
| Subnet | Web-Subnet |
| Private IP | 10.0.1.4 |
The VM uses its NIC to communicate with other resources in the network.
Multiple NICs
Azure also supports attaching multiple NICs to certain VM sizes.
This can be useful when a VM needs connectivity to different Subnets or network configurations.
Creating and Managing a NIC
Creating a NIC
An Azure NIC can be created as part of creating a Virtual Machine or separately when required.
While creating a NIC, important networking options include:
Create the NIC.
Managing a NIC
After creating a NIC, administrators can manage its networking configuration, such as:
NIC Azure VM और VNet के बीच connection का important part है। NIC के माध्यम से VM को Subnet, Private IP, Public IP और NSG जैसी networking settings मिलती हैं।
Example
Suppose a company creates a Web VM in Azure.
| Component | Configuration |
| VM | Web-VM |
| NIC | Web-VM-NIC |
| VNet | Production-VNet |
| Subnet | Web-Subnet |
| Private IP | 10.0.1.4 |
| Public IP | 20.50.10.25 |
| NSG | Web-NSG |
The NIC connects the Web-VM to the Web-Subnet, provides its Private IP, and can be associated with a Public IP and NSG when required.
DNS is an important part of networking because it allows users and applications to access resources using names instead of IP Addresses. Azure provides Azure DNS to host and manage DNS domains and records.
What is DNS?
Definition
DNS (Domain Name System) is a naming system that translates domain names into IP Addresses, allowing users and applications to access network resources using easy-to-remember names.
Explanation
Computers communicate using IP Addresses, but remembering IP Addresses for every website or service is difficult.
For example: www.example.com → 203.0.113.10
DNS performs this name-to-IP resolution.
DNS का काम Domain Name को IP Address में resolve करना है, ताकि users को IP Address याद रखने की जरूरत न पड़े।
Example
When a user enters: www.example.com
The DNS system finds the corresponding IP Address, and the user's device can then connect to that server.
What is Azure DNS?
Definition
Azure DNS is a DNS hosting service in Microsoft Azure that allows organizations to host and manage DNS domains and DNS records using Azure.
Explanation
Azure DNS can be used to manage DNS records such as:
Azure DNS provides DNS management through the Azure Portal, Azure CLI, PowerShell, and APIs.
Azure DNS Azure के अंदर DNS Zones और DNS Records को manage और host करने के लिए इस्तेमाल किया जाता है।
How Azure DNS Works
When a user requests a domain name, DNS resolution is performed to find the IP Address associated with that name.
Example
| Domain Name | DNS Record | IP Address |
| www.example.com | A Record | 20.50.10.25 |
The process is:
User requests domain → DNS resolves the name → IP Address is returned → Resource is accessed
Azure DNS stores and manages the required DNS records so that domain names can be resolved to the appropriate resources.
Azure DNS Use Cases
1. Hosting DNS Zones : Organizations can host their domain's DNS records in Azure.
2. Azure Resource Name Resolution : DNS can be used to resolve names associated with applications and Azure resources.
3. Website Hosting : Organizations can configure DNS records for websites hosted in Azure.
4. Application Connectivity : DNS names can be used instead of IP Addresses when applications communicate with network resources.
5. Domain Management : Organizations can manage different DNS records such as A, AAAA, CNAME, MX, and TXT from Azure.
Azure DNS का उपयोग mainly DNS Zones और DNS Records को manage करने तथा Domain Names को सही IP Address या service तक resolve करने के लिए किया जाता है।
Azure Virtual Network Security helps protect Azure resources from unauthorized network access and unwanted traffic. Azure provides features such as Network Security Groups (NSGs) and security rules to control network communication.
Why Azure Network Security is Required
Definition
Azure Network Security is the process of protecting Azure networks and resources by controlling network traffic and preventing unauthorized access.
Explanation
Azure resources such as Virtual Machines and applications may receive network traffic from other resources, users, or the Internet. Without proper security controls, unwanted traffic could reach sensitive resources.
Network security helps organizations:
Azure में Network Security का उपयोग यह control करने के लिए किया जाता है कि कौन-सा Network Traffic Azure Resources तक पहुंच सकता है और कौन-सा Traffic block किया जाना चाहिए।
Network Security Group (NSG)
Definition
A Network Security Group (NSG) is an Azure networking feature that contains security rules used to allow or deny inbound and outbound network traffic.
Explanation
An NSG evaluates network traffic based on rules such as:
An NSG can be associated with a Subnet or Network Interface (NIC).
Example
Suppose a Web Server should allow HTTP traffic on Port 80, but other unnecessary traffic should be blocked.
An NSG rule can be configured to: Allow → TCP → Port 80
NSG का उपयोग Network Traffic को allow या deny करने के लिए किया जाता है। इससे administrator यह control कर सकता है कि कौन-सा Traffic Resource तक पहुंच सकता है।
Inbound and Outbound Traffic
Inbound Traffic
Inbound Traffic is network traffic coming into an Azure resource or network.
Example: Internet User → Web Server
If a user accesses a website hosted on an Azure VM, the request is inbound traffic for the VM.
Outbound Traffic
Outbound Traffic is network traffic going from an Azure resource or network to another destination.
Example:
Azure VM → Internet
If a VM connects to an external website, the traffic leaving the VM is outbound traffic.
| Inbound Traffic | Outbound Traffic |
| Traffic coming into a resource | Traffic leaving a resource |
| Internet → VM | VM → Internet |
| Client → Server | Server → External Service |
Network Security Rules
Definition
Network Security Rules are rules in an NSG that determine whether specific network traffic should be allowed or denied.
Important Rule Components
| Component | Example |
| Source | Internet |
| Destination | Web VM |
| Protocol | TCP |
| Port | 80 |
| Action | Allow |
| Priority | 100 |
Example
A rule can be created:
This allows HTTP traffic to the Web Server.
Another rule can deny unnecessary traffic.
Network Security Rules यह तय करते हैं कि किसी particular Source से आने वाला Traffic, किसी particular Destination और Port तक पहुंच सकता है या नहीं।
Basic Azure Network Security Practices :-
1. Allow Only Required Traffic : Only necessary ports and services should be allowed.
2. Block Unnecessary Access : Unnecessary network connections should be denied.
3. Use NSGs : Use Network Security Groups to control inbound and outbound traffic.
4. Protect Sensitive Resources : Database and other sensitive resources should not be directly exposed to the Internet unless required.
5. Use Private IPs Where Appropriate : Use Private IP Addresses for internal communication whenever public connectivity is not required.
6. Follow Least Privilege : Provide only the network access that is actually required by a resource or application.
Azure Network Security का मुख्य उद्देश्य unnecessary access को रोकना और केवल required Network Traffic को allow करना है।
An Azure Virtual Machine requires network connectivity to communicate with other Azure resources, users, the Internet, and On-Premises networks. Azure uses Virtual Networks (VNet), Subnets, Network Interfaces (NIC), IP Addresses, and Network Security Groups (NSGs) to provide and control this connectivity.
How Azure VMs Connect to a VNet
Definition
An Azure Virtual Machine connects to a Virtual Network (VNet) through a Network Interface (NIC). The NIC is connected to a specific Subnet, and the Subnet belongs to the VNet.
Explanation
When an Azure VM is created, a NIC is normally created and attached to the VM. During VM creation, the NIC is connected to a selected VNet and Subnet. The NIC then provides the VM with its network configuration, including its Private IP Address.
This allows the VM to communicate with other resources connected to the same VNet or to networks that are properly connected to the VNet.
VM → NIC → Subnet → VNet
The network communication is then controlled using Network Security Groups (NSGs) and routing configurations.
Azure VM को VNet से connect करने के लिए NIC का उपयोग होता है। NIC किसी specific Subnet से जुड़ा होता है और वह Subnet VNet का हिस्सा होता है।
VM and Subnet
Definition
A Subnet is a smaller network segment created inside an Azure VNet. Azure resources such as Virtual Machines can be connected to a specific Subnet.
Explanation
A VNet can contain multiple Subnets for different purposes. For example, an organization may create separate Subnets for Web Servers, Application Servers, and Database Servers.
When creating a VM, the administrator selects the VNet and Subnet where the VM's NIC will be placed.
For example:
The VM is therefore connected to the Web-Subnet through its NIC.
This allows the VM to communicate with other resources in the VNet according to the configured networking and security rules.
VM का NIC एक specific Subnet से जुड़ा होता है। Subnet VM को VNet के अंदर एक specific network segment प्रदान करता है।
VM and NIC
Definition
A Network Interface (NIC) is the virtual networking component that connects an Azure VM to a VNet.
Explanation
The NIC acts as the connection point between the VM and Azure networking. It contains the network configuration required by the VM.
The NIC can be associated with a Private IP Address, Public IP Address, and Network Security Group (NSG).
For example, when a VM needs to communicate with another VM, the communication can take place through the Private IP configured on its NIC.
The NIC can also be managed separately from the VM, allowing administrators to modify certain networking configurations without changing the VM itself.
NIC VM और Azure Network के बीच connection प्रदान करता है और VM की network identity तथा connectivity को manage करने में important role निभाता है।
VM Private IP
Definition
A Private IP Address is an IP Address used by an Azure VM for communication within a private network such as an Azure VNet.
Explanation
The Private IP is assigned to the VM's NIC from the Address Space of the Subnet.
For example:
The VM can use 10.0.1.4 to communicate with other Azure resources through private networking.
For example, a Web VM can communicate with an Application VM, and the Application VM can communicate with a Database VM using their Private IP Addresses.
Private IP communication is commonly used for internal applications because these resources do not need to be directly exposed to the public Internet.
Private IP का उपयोग VM के internal communication के लिए किया जाता है। यह VM को VNet के अंदर दूसरे Resources के साथ communicate करने में मदद करता है।
VM Public IP
Definition
A Public IP Address is an IP Address that provides Internet-facing connectivity to an Azure VM when required.
Explanation
A VM does not necessarily need a Public IP. It is assigned or associated when the VM needs to communicate directly with or be accessed from the public Internet.
For example, a Web Server hosting a public website may require a Public IP so that Internet users can access the service.
However, assigning a Public IP does not automatically mean that all Internet traffic is allowed. Network Security Groups and other security controls determine which traffic is permitted.
For security reasons, internal resources such as Database Servers generally do not need direct Public IP connectivity.
Public IP का उपयोग VM को Internet-facing connectivity देने के लिए किया जाता है। Internal Resources को सामान्यतः Public IP की आवश्यकता नहीं होती।
Configuring Network Connectivity for Azure VMs
Definition
Network Connectivity Configuration means setting up the networking components required for a VM to communicate with other resources or networks.
Explanation
When configuring networking for an Azure VM, the administrator needs to consider the VNet, Subnet, NIC, IP Addresses, and NSG.
The VNet provides the overall network environment, while the Subnet provides the network segment where the VM is connected. The NIC connects the VM to the Subnet and provides its IP configuration.
A Private IP is normally used for internal communication. If the VM needs Internet-facing connectivity, a Public IP can be associated with the NIC. An NSG can then be used to control which inbound and outbound traffic is allowed.
Example
Suppose a company creates a Web Server in Azure:
| Component | Configuration |
| VNet | Production-VNet |
| Subnet | Web-Subnet |
| VM | Web-VM |
| NIC | Web-VM-NIC |
| Private IP | 10.0.1.4 |
| Public IP | 20.50.10.25 |
| NSG | Web-NSG |
The Web-VM is connected to the Web-Subnet through its NIC. Its Private IP is used for internal communication, while the Public IP allows Internet-facing connectivity when required. The NSG controls which network traffic can reach the VM.
Important Relationship
Virtual Machine → Network Interface → Subnet → Virtual Network
The VM uses the NIC for network connectivity, the NIC connects to the Subnet, and the Subnet belongs to the VNet.
Designing an Azure Virtual Network involves planning the VNet, Address Space, Subnets, IP Addresses, and Network Security according to the requirements of an application. A good network design should be organized, secure, scalable, and easy to manage.
Designing a VNet
Definition
VNet Design is the process of planning the structure of an Azure Virtual Network so that Azure resources can communicate securely and efficiently.
Explanation
Before creating a VNet, an administrator should understand the application's requirements, such as the number of resources, required Subnets, IP Address ranges, Internet connectivity, and security requirements.
A VNet should be designed so that resources can be separated into appropriate network segments and additional resources can be added in the future.
For example, an organization may create separate Subnets for Web Servers, Application Servers, and Database Servers.
VNet Design करते समय Network की requirements, IP ranges, Subnets, Security और future growth को पहले plan किया जाता है।
Choosing Address Space
Definition
Address Space is the range of IP Addresses available within a VNet.
Explanation
When creating a VNet, an administrator selects an appropriate IP Address range, such as: 10.0.0.0/16
This range provides the IP Address space from which Subnets can be created.
The selected Address Space should be large enough for the current resources as well as future expansion. It should also avoid overlapping with networks that may need to connect to the VNet, such as an On-Premises Network.
Address Space ऐसा select करना चाहिए जिसमें वर्तमान और future Resources के लिए पर्याप्त IP Addresses हों और connected networks के साथ IP range overlap न हो।
Designing Subnets
Definition
A Subnet is a smaller network segment created from the VNet's Address Space.
Explanation
Subnets are used to organize resources according to their roles or requirements. For example, a three-tier application can use separate Subnets for different components.
| Subnet | Purpose |
| Web Subnet | Web Servers |
| Application Subnet | Application Servers |
| Database Subnet | Database Resources |
Separating resources into Subnets makes the network easier to manage and allows different security rules to be applied where required.
Subnets का उपयोग VNet को छोटे network segments में divide करने और अलग-अलग प्रकार के Resources को व्यवस्थित रखने के लिए किया जाता है।
Assigning IP Addresses
Definition
IP Address Assignment is the process of providing appropriate IP Addresses to Azure network resources for communication.
Explanation
Azure resources connected to a Subnet use IP Addresses from the Subnet's Address range. Private IP Addresses are commonly used for communication between resources within the VNet.
For example:
When planning IP Addresses, administrators should ensure that sufficient addresses are available for current and future resources.
IP Address planning करते समय यह ध्यान रखना चाहिए कि Resources के लिए पर्याप्त addresses available हों और IP ranges properly organized हों।
Securing Network Traffic
Definition
Network Traffic Security is the process of controlling and protecting the traffic entering, leaving, and moving within an Azure network.
Explanation
Azure provides features such as Network Security Groups (NSGs) to control inbound and outbound traffic.
For example, a Web Server may allow required HTTP/HTTPS traffic while unnecessary ports remain blocked. A Database Subnet can be restricted so that only required application traffic can reach the database.
Security should follow the Principle of Least Privilege, allowing only the network access that is actually required.
Network Traffic Security का उद्देश्य केवल required traffic को allow करना और unnecessary या unauthorized traffic को block करना है।
Basic Azure Network Architecture
A basic Azure application can be designed using separate network segments for different application layers.
| Component | Example |
| VNet | Production-VNet |
| Address Space | 10.0.0.0/16 |
| Web Subnet | 10.0.1.0/24 |
| Application Subnet | 10.0.2.0/24 |
| Database Subnet | 10.0.3.0/24 |
The Web, Application, and Database resources are placed in their respective Subnets. Network Security Groups and other networking controls can then be used to control communication between these components.
This type of design provides organization, security, and scalability for Azure applications.
