Free guides, interview Q&As, and job responsibility breakdowns — curated by industry veterans to help you crack MNC interviews
Azure Virtual Network (VNet) Peering allows two Azure Virtual Networks to communicate with each other using the Azure backbone network. Once peering is established, resources such as Virtual Machines in one VNet can communicate with resources in another VNet as if they were connected to the same network.
VNet Peering is useful when an organization has multiple Virtual Networks and needs communication between them without creating a VPN connection or routing traffic through the public internet.
What is VNet Peering?
Definition
VNet Peering is a networking feature in Azure that connects two Virtual Networks so that resources in those VNets can communicate with each other using private IP addresses.
(VNet Peering Azure की दो Virtual Networks को आपस में connect करने की सुविधा है, जिससे दोनों VNets में मौजूद resources private IP addresses के माध्यम से communicate कर सकते हैं।)
Explanation
When two VNets are peered, Azure creates a direct network connection between them through the Microsoft Azure backbone network. The traffic does not need to travel through the public internet.
For example, suppose an organization has one VNet containing application servers and another VNet containing database servers. VNet Peering can be configured between the two VNets so that the application servers can communicate with the database servers using their private IP addresses.
Example
ABC Technologies has two VNets:
After configuring VNet Peering, the application servers in VNet-A can communicate with the database servers in VNet-B through their private IP addresses.
Why VNet Peering is Used
VNet Peering is mainly used when resources deployed in different Virtual Networks need to communicate with each other.
Without peering, two separate VNets do not automatically have direct connectivity between their private address spaces. VNet Peering provides a simple way to establish this connectivity.
Common reasons for using VNet Peering include:
Example
An organization keeps its development environment in one VNet and its shared services in another VNet. VNet Peering can allow the development resources to access the required shared services privately.
Benefits of VNet Peering
VNet Peering provides several benefits for Azure networking.
1. Private Communication
Resources in peered VNets can communicate using private IP addresses without requiring communication through the public internet.
2. Azure Backbone Network
Traffic between peered VNets travels through Microsoft's Azure backbone network, providing reliable connectivity between the networks.
3. Low Latency
Because communication uses the Azure backbone network, VNet Peering provides low-latency connectivity between resources in the connected VNets.
4. Simple Configuration
VNet Peering provides a straightforward way to connect VNets without requiring a VPN gateway for basic VNet-to-VNet connectivity.
5. Supports Different Network Architectures
Organizations can use VNet Peering to connect separate VNets for applications, databases, development, production, or shared services.
Example
ABC Technologies has separate VNets for its Web, Application, and Database workloads. By using VNet Peering where required, these VNets can communicate privately while remaining logically separated.
VNet Peering establishes a direct connection between two Azure Virtual Networks, allowing resources in those networks to communicate using private IP addresses. Once the peering is configured, Azure treats the peered VNets as connected networks while keeping them as separate Virtual Networks.
The communication takes place over the Azure backbone network, which provides private and low-latency connectivity between the connected VNets.
How VNet Peering Works
Definition
VNet Peering works by creating a network connection between two Virtual Networks. For communication to work correctly, peering must be configured between the VNets.
(VNet Peering में दो Virtual Networks के बीच connection establish किया जाता है, जिससे दोनों networks के resources private IP addresses के माध्यम से communicate कर सकते हैं।)
Explanation
Suppose an organization has VNet-A and VNet-B. After configuring peering, Azure creates a direct connectivity path between the two VNets.
Resources in VNet-A can then communicate with resources in VNet-B using their private IP addresses.
VNet Peering can be configured between:
Example
ABC Technologies has:
After peering is configured, a VM in VNet-A can communicate with a VM in VNet-B using the private IP address of the destination VM.
VNet-to-VNet Communication
VNet-to-VNet communication means communication between resources located in two different Azure Virtual Networks.
When two VNets are peered, resources such as Virtual Machines can communicate directly using private IP addresses, provided the required network and security rules allow the traffic.
Example
Suppose:
After VNet Peering is configured:
VM1 → VNet-A → VNet Peering → VNet-B → VM2
The communication uses the Azure backbone network rather than the public internet.
Important Point
VNet Peering does not automatically mean that every type of traffic will be allowed. Network Security Groups (NSGs), routing, and other network configurations can still control whether communication is permitted.
VNet Peering Requirements
Before creating VNet Peering, certain conditions should be considered.
1. Non-Overlapping Address Spaces
The address spaces of the two VNets should not overlap.
For example:
These address spaces are different and can be used for peering.
2. Access to Both VNets
The administrator must have the required permissions to configure peering on the Virtual Networks.
3. Peering Configuration
Peering needs to be configured between the two VNets. For a normal two-way communication scenario, the peering relationship needs to be established appropriately on both sides.
4. Network Security Rules
NSGs and other network security configurations should allow the required traffic between the VNets.
Example
ABC Technologies wants to connect two VNets. Before creating the peering, the administrator checks that their address spaces do not overlap and that the required permissions are available.
VNet Peering Limitations
Although VNet Peering provides simple and efficient connectivity, it has some limitations and considerations.
1. Address Spaces Should Not Overlap
VNets with overlapping IP address spaces cannot be directly peered in the normal way.
For example:
These networks have overlapping address spaces, which creates a problem for direct routing between them.
2. Peering is Not Transitive by Default
Suppose three VNets exist:
VNet-A ↔ VNet-B ↔ VNet-C
Even though VNet-A is peered with VNet-B and VNet-B is peered with VNet-C, VNet-A does not automatically communicate with VNet-C through VNet-B.
Additional network configuration may be required for such scenarios.
3. Peering is Configured Between Specific VNets
A peering connection connects specific Virtual Networks. If an organization has many VNets, the network design and required peering relationships should be planned carefully.
4. Network Security Still Applies
VNet Peering does not bypass NSGs or other network security controls. The required traffic must be allowed by the applicable security and routing configuration.
Global VNet Peering allows Azure Virtual Networks located in different Azure regions to communicate with each other using private network connectivity. It is useful when an organization has workloads distributed across multiple Azure regions.
What is Global VNet Peering?
Definition
Global VNet Peering is a networking feature that connects Azure Virtual Networks located in different Azure regions and allows resources in those VNets to communicate using private IP addresses.
Global VNet Peering Azure के अलग-अलग regions में मौजूद Virtual Networks को आपस में connect करने की सुविधा है। इसके द्वारा दोनों VNets में मौजूद resources private IP addresses का उपयोग करके आपस में communicate कर सकते हैं।
Explanation
Global VNet Peering creates a direct connection between Virtual Networks in different Azure regions. Communication between the peered VNets travels through the Microsoft Azure backbone network instead of the public internet.
Global VNet Peering अलग-अलग Azure regions की Virtual Networks के बीच direct connectivity establish करता है। दोनों VNets के बीच traffic public internet की बजाय Microsoft Azure backbone network के through travel करता है।
How Global VNet Peering Works
When two Virtual Networks are located in different Azure regions, Global VNet Peering can be configured to connect them. Once peering is established, resources in one VNet can communicate with resources in the other VNet using their private IP addresses.
The communication remains within Microsoft's Azure backbone network, providing private connectivity between the connected VNets.
जब दो Virtual Networks अलग-अलग Azure regions में होती हैं, तब उनके बीच Global VNet Peering configure किया जा सकता है। Peering establish होने के बाद एक VNet के resources दूसरी VNet के resources से private IP address के through communicate कर सकते हैं।
यह communication Microsoft के Azure backbone network के अंदर होता है, इसलिए दोनों VNets के बीच private connectivity मिलती है।
Important Point
The address spaces of the VNets should not overlap, and applicable Network Security Groups (NSGs) and routing rules must allow the required communication.
दोनों VNets के IP address spaces overlap नहीं करने चाहिए। साथ ही, required traffic को allow करने के लिए Network Security Groups और routing configuration भी सही होना चाहिए।
Regional vs Global VNet Peering
The main difference between Regional and Global VNet Peering is the location of the Virtual Networks.
| Regional VNet Peering | Global VNet Peering |
| Connects VNets in the same Azure region | Connects VNets in different Azure regions |
| Used for same-region connectivity | Used for cross-region connectivity |
| Uses the Azure backbone network | Uses the Azure backbone network |
| Suitable for workloads within one region | Suitable for multi-region workloads |
Hindi Explanation:
Regional VNet Peering का उपयोग तब किया जाता है जब दोनों VNets एक ही Azure region में हों। Global VNet Peering का उपयोग तब किया जाता है जब VNets अलग-अलग Azure regions में मौजूद हों।दोनों cases में Azure backbone network के माध्यम से private connectivity प्रदान की जाती है।
Benefits of Global VNet Peering
1. Cross-Region Connectivity
Global VNet Peering allows resources in different Azure regions to communicate with each other using private IP addresses.
यह अलग-अलग Azure regions में मौजूद resources के बीच private IP addresses के द्वारा communication allow करता है।
2. Azure Backbone Network
Traffic between the connected VNets travels through the Microsoft Azure backbone network.
Connected VNets के बीच traffic Microsoft Azure backbone network के through travel करता है, जिससे public internet पर dependency कम होती है।
3. Low-Latency Communication
Global VNet Peering provides direct connectivity between VNets, helping provide low-latency communication between resources in different regions.
VNets के बीच direct connectivity होने के कारण अलग-अलग regions में मौजूद resources के बीच low-latency communication प्राप्त किया जा सकता है।
4. Supports Multi-Region Applications
It allows organizations to deploy applications and services across multiple Azure regions while maintaining connectivity between them.
Organizations अपने applications और services को अलग-अलग Azure regions में deploy करके भी उनके बीच connectivity maintain कर सकती हैं।
5. Simplified Network Connectivity
Global VNet Peering provides a simple way to connect VNets across regions without requiring a VPN gateway for basic VNet-to-VNet connectivity.
Basic VNet-to-VNet connectivity के लिए Global VNet Peering एक simple networking option प्रदान करता है, जिससे अलग से VPN gateway की आवश्यकता नहीं होती।
9.4 Azure Bastion Overview
Azure Bastion is a fully managed Azure service that provides secure remote access to Virtual Machines through the Azure Portal. It allows administrators to connect to Windows VMs using RDP and Linux VMs using SSH without requiring a public IP address on the individual VM.
What is Azure Bastion?
Definition
Azure Bastion is a fully managed PaaS service that provides secure RDP and SSH connectivity to Azure Virtual Machines directly through the Azure Portal.
Azure Bastion एक fully managed Azure service है जो Azure Portal के through Virtual Machines को securely access करने की सुविधा देता है। इसके द्वारा Windows VM के लिए RDP और Linux VM के लिए SSH connection establish किया जा सकता है, बिना VM को public IP address दिए।
Explanation
Normally, remote access to a VM from the internet may require a public IP address and an exposed RDP or SSH port. Azure Bastion provides an alternative by acting as a secure connection point between the administrator and the VM.
The administrator connects to the VM through the Azure Portal, while the VM can remain without a public IP address.
Normally internet से VM को remotely access करने के लिए VM पर public IP और RDP/SSH port की आवश्यकता हो सकती है। Azure Bastion इस requirement को कम करता है और administrator को Azure Portal के through VM से connect करने देता है।
VM को directly internet पर expose करने के बजाय Bastion एक secure connection point के रूप में काम करता है।
Why Azure Bastion is Used
Azure Bastion is mainly used to provide secure and simplified remote access to Azure Virtual Machines.
Instead of exposing management ports such as RDP (3389) and SSH (22) directly to the internet, administrators can use Azure Bastion to connect to VMs through the Azure Portal.
Azure Bastion का उपयोग Azure VMs को securely manage और access करने के लिए किया जाता है। इससे RDP port 3389 और SSH port 22 को directly internet पर expose करने की आवश्यकता कम हो जाती है।
This is particularly useful for VMs that should not have public IP addresses, such as application servers and database servers.
यह उन VMs के लिए विशेष रूप से useful है जिन्हें public IP address नहीं देना है, जैसे application servers और database servers।
How Azure Bastion Works
Azure Bastion is deployed inside an Azure Virtual Network and provides a secure path for administrators to connect to VMs.
The administrator opens the required VM in the Azure Portal, selects the Connect option, and chooses RDP or SSH. The connection is established through Azure Bastion without requiring a public IP address on the VM.
Azure Bastion को Azure Virtual Network के अंदर deploy किया जाता है। Administrator Azure Portal में VM को open करके Connect option select करता है और RDP या SSH connection choose करता है।
इसके बाद connection Azure Bastion के through VM तक पहुंचता है और individual VM को public IP address की आवश्यकता नहीं होती।
Basic Flow
Administrator → Azure Portal → Azure Bastion → Azure VM
इस process में administrator पहले Azure Portal से connect करता है, फिर Azure Bastion connection को securely VM तक पहुंचाता है।
Benefits of Azure Bastion
1. Secure VM Access
Azure Bastion provides a secure method for accessing Azure VMs without directly exposing their management ports to the public internet.
Azure Bastion VMs को securely access करने की सुविधा देता है और RDP/SSH management ports को directly public internet पर expose करने की आवश्यकता कम करता है।
2. No Public IP Required on VM
VMs can be accessed without assigning a public IP address to each individual VM.
Individual VM को public IP address देने की आवश्यकता नहीं होती, जिससे VM को directly internet से accessible बनाने से बचा जा सकता है।
3. Browser-Based Access
Administrators can connect to VMs directly through the Azure Portal using a web browser.
Administrator Azure Portal और web browser के through सीधे VM से connect कर सकता है। अलग से internet-facing RDP/SSH connection setup करने की आवश्यकता नहीं होती।
4. RDP and SSH Support
Azure Bastion supports RDP for Windows VMs and SSH for Linux VMs.
Windows Virtual Machines के लिए RDP और Linux Virtual Machines के लिए SSH connection Azure Bastion के through किया जा सकता है।
5. Centralized Access
Azure Bastion provides a centralized way to manage remote access to VMs within the Virtual Network.
Azure Bastion Virtual Network के अंदर मौजूद VMs के remote access को एक centralized और controlled तरीके से manage करने में मदद करता है।
Remote access is required to manage Azure Virtual Machines from another computer. For Windows VMs, RDP is commonly used, while Linux VMs generally use SSH. Azure Bastion provides a secure way to establish these connections through the Azure Portal without requiring a public IP address on the VM.
What is RDP?
Definition
RDP (Remote Desktop Protocol) is a Microsoft protocol used to remotely connect to and manage a Windows computer or Windows Server through a graphical desktop interface.
RDP एक Microsoft protocol है जिसका उपयोग किसी Windows computer या Windows Server को remotely access और manage करने के लिए किया जाता है। RDP connection में administrator को remote Windows machine का graphical desktop दिखाई देता है।
Explanation
RDP allows an administrator to interact with a remote Windows VM almost as if they were sitting in front of the machine. The administrator can open applications, manage files, configure Windows settings, and perform administrative tasks.
The default RDP port is TCP 3389.
RDP के द्वारा administrator remote Windows VM पर applications, files और Windows settings को manage कर सकता है। RDP का default port TCP 3389 है।
What is SSH?
Definition
SSH (Secure Shell) is a secure network protocol used to remotely connect to and manage Linux-based computers and servers through a command-line interface.
Hindi Explanation:
SSH एक secure network protocol है जिसका उपयोग Linux computers और servers को remotely access और manage करने के लिए किया जाता है। इसमें सामान्यतः command-line interface के माध्यम से काम किया जाता है।
Explanation
SSH provides an encrypted connection between the administrator and the remote Linux VM. It is commonly used by administrators to execute commands, configure services, manage files, and perform system administration tasks.
The default SSH port is TCP 22.
SSH administrator और Linux VM के बीच encrypted connection provide करता है। इसके माध्यम से administrator commands execute कर सकता है, services configure कर सकता है और system को manage कर सकता है। SSH का default port TCP 22 है।
RDP vs SSH
RDP and SSH are both used for remote administration, but they are generally used with different operating systems and provide different types of interfaces.
| RDP | SSH |
| Commonly used for Windows VMs | Commonly used for Linux VMs |
| Provides a graphical desktop interface | Primarily provides a command-line interface |
| Default port: TCP 3389 | Default port: TCP 22 |
| Used for Windows remote administration | Used for Linux/Unix remote administration |
RDP मुख्य रूप से Windows systems को graphical desktop के साथ remotely manage करने के लिए use होता है, जबकि SSH Linux systems को command-line interface के through securely manage करने के लिए commonly used होता है।
Secure Remote Access using Azure Bastion
Definition
Azure Bastion provides secure RDP and SSH connectivity to Azure Virtual Machines through the Azure Portal without requiring direct internet access to the VM.
Azure Bastion Azure Portal के through Azure VMs को secure RDP और SSH access प्रदान करता है। इसके लिए VM को directly internet पर expose करने की आवश्यकता नहीं होती।
Explanation
With Azure Bastion, an administrator opens the VM in the Azure Portal and selects the Connect option. The administrator can then choose RDP for a Windows VM or SSH for a Linux VM.
The connection is handled through Azure Bastion, while the VM can remain without a public IP address.
Administrator Azure Portal में VM को open करके Connect option select करता है। Windows VM के लिए RDP और Linux VM के लिए SSH select किया जा सकता है।
Connection Azure Bastion के through establish होता है और VM को individual public IP address देने की आवश्यकता नहीं होती।
Connection Flow
Administrator → Azure Portal → Azure Bastion → Azure VM
इसमें administrator Azure Portal से connection शुरू करता है, Azure Bastion secure connection को VM तक पहुंचाता है और VM को directly public internet पर expose नहीं करना पड़ता।
RDP/SSH Without Public IP
Azure Bastion allows administrators to connect to Azure VMs without assigning a public IP address to the individual VM.
Normally, direct internet-based remote access may require a public IP and appropriate RDP or SSH connectivity. With Bastion, the administrator can access the VM through the Azure Portal.
Normally internet से VM को directly RDP या SSH करने के लिए public IP की आवश्यकता हो सकती है। Azure Bastion का उपयोग करने पर individual VM को public IP देने की आवश्यकता नहीं होती और administrator Azure Portal के through VM से connect कर सकता है।
Example
A Windows VM has only a private IP address and does not have a public IP.
The administrator opens the VM in the Azure Portal and selects Connect → Bastion. After authentication, the administrator can access the Windows VM through RDP.
मान लीजिए Windows VM के पास केवल private IP है और कोई public IP नहीं है। Administrator Azure Portal में VM को open करके Connect → Bastion select करता है। Authentication के बाद VM को RDP के through access किया जा सकता है।
9.6 Network Connectivity
Azure Virtual Network provides the networking foundation for Azure resources such as Virtual Machines. Proper network connectivity allows VMs to communicate with other resources within the same VNet, different VNets, Azure services, and connected networks.
Network connectivity depends on components such as Virtual Networks, Subnets, Network Interfaces, IP addresses, routing, and Network Security Groups (NSGs).
Azure Network Connectivity
Definition
Azure Network Connectivity refers to the communication between Azure resources and networks using Azure networking services and configurations.
Azure Network Connectivity का मतलब Azure resources के बीच network के through communication establish होना है। इसमें Virtual Network, Subnet, NIC, IP addresses, routing और security rules जैसे components important role play करते हैं।
Explanation
An Azure Virtual Network provides a private networking environment for Azure resources. Virtual Machines connect to the VNet through their Network Interfaces, which are attached to a specific subnet.
Network connectivity can be used for communication between:
Azure Virtual Machines
Different subnets
Different Virtual Networks
Azure services
On-premises networks
Azure VNet एक private networking environment provide करता है। VM का NIC किसी subnet से connected होता है और इसी के through VM network communication करता है।
Azure में connectivity का उपयोग VMs, subnets, different VNets, Azure services और on-premises networks के बीच communication के लिए किया जा सकता है।
Connectivity Between VNets
Definition
VNet-to-VNet Connectivity allows resources in different Azure Virtual Networks to communicate with each other.
VNet-to-VNet Connectivity का मतलब अलग-अलग Azure Virtual Networks में मौजूद resources के बीच communication establish करना है।
Explanation
Two VNets are separate networks by default. To allow resources in different VNets to communicate, an appropriate connectivity method must be configured.
VNet Peering is one of the common methods for connecting VNets. It allows resources in peered VNets to communicate using private IP addresses through the Azure backbone network.
दो अलग-अलग VNets by default एक-दूसरे से directly communicate नहीं करती हैं। Communication के लिए appropriate connectivity configure करनी पड़ती है।
VNet Peering एक common method है जिसके द्वारा VNets को connect किया जा सकता है। Peering के बाद resources private IP addresses का उपयोग करके Azure backbone network के through communicate कर सकते हैं।
Important Point
For communication to work, the VNets should have appropriate address spaces and the required traffic must be allowed by routing and security rules.
Communication के लिए VNets की addressing सही होनी चाहिए और required traffic को routing तथा security rules के द्वारा allow किया जाना चाहिए।
Connectivity to Azure VMs
Definition
Connectivity to an Azure VM means establishing network communication with the VM for application access or remote administration.
Azure VM Connectivity का मतलब VM के साथ network communication establish करना है, ताकि applications access की जा सकें या VM को remotely manage किया जा सके।
Explanation
An Azure VM connects to the Virtual Network through a Network Interface (NIC). The NIC is connected to a subnet and contains the VM's IP configuration.
A VM can be accessed using:
Private IP → For internal network connectivity
Public IP → For internet-facing connectivity when required
Azure Bastion → For secure RDP/SSH access without requiring a public IP on the VM
Azure VM अपने NIC के through Virtual Network से connect होता है। NIC किसी subnet से connected होता है और उसमें VM की IP configuration होती है।
VM को internal communication के लिए private IP, required होने पर internet connectivity के लिए public IP, और secure remote administration के लिए Azure Bastion के through access किया जा सकता है।
Security
Network connectivity to a VM can be controlled using Network Security Groups (NSGs), which can allow or deny specific network traffic.
VM की network connectivity को Network Security Groups के द्वारा control किया जा सकता है। NSG specific ports और traffic को allow या deny कर सकता है।
Verify Network Connectivity
Definition
Network Connectivity Verification is the process of checking whether two network resources can successfully communicate with each other.
Network Connectivity Verification का मतलब यह check करना है कि दो network resources के बीच communication successfully हो रहा है या नहीं।
Explanation
Connectivity can be verified using different network troubleshooting tools and methods depending on the type of connection.
For example, from a Windows VM, you can use:
ping → To test basic network reachability where ICMP is permitted
Test-NetConnection → To test connectivity to a specific IP address and port
ipconfig → To view the VM's IP configuration
For example:
Test-NetConnection 10.0.1.20 -Port 3389
This can help determine whether TCP port 3389 is reachable from the source VM.
Hindi Explanation:
Connectivity verify करने के लिए अलग-अलग tools का उपयोग किया जा सकता है। ping basic reachability check करने के लिए, Test-NetConnection specific IP और port की connectivity check करने के लिए और ipconfig VM की IP configuration देखने के लिए उपयोग किया जा सकता है।
Troubleshooting Checklist
If connectivity is not working, check:
VM's private or public IP address
Network Interface configuration
Subnet configuration
Network Security Group rules
Route configuration
VNet Peering status, if applicable
Whether the destination service is running
अगर connectivity काम नहीं कर रही है, तो सबसे पहले VM का IP address, NIC, subnet, NSG rules, routing और VNet Peering configuration check करनी चाहिए। इसके साथ यह भी verify करना चाहिए कि destination VM पर required service running है या नहीं।
9.7 Practical Labs
The following practical labs provide hands-on experience with VNet Peering and Azure Bastion. These exercises help you understand how to connect Virtual Networks and securely access Azure Virtual Machines without exposing them directly to the public internet.
Practical 1: Create VNet Peering
Objective
To create a VNet Peering connection between two Azure Virtual Networks and verify communication between resources in the connected VNets.
Steps
Log in to the Azure Portal and open Virtual Networks.
Create or select the first Virtual Network (VNet-A).
Create or select the second Virtual Network (VNet-B).
Make sure the address spaces of both VNets do not overlap.
Open VNet-A → Peerings and select Add.
Provide a suitable peering name and select VNet-B as the remote Virtual Network.
Enable the required options for allowing traffic between the VNets.
Create the peering connection.
Configure the peering from VNet-B to VNet-A, if required.
Verify that the peering status shows Connected.
Test communication between VMs in the two VNets using their private IP addresses.
Learning Outcome
After completing this lab, you should be able to create VNet Peering and verify private communication between resources in different Virtual Networks.
Practical 2: Configure Azure Bastion
Objective
To deploy Azure Bastion in a Virtual Network and configure it for secure remote access to an Azure Virtual Machine.
Steps
Log in to the Azure Portal and open the required Virtual Network.
Verify that the VNet contains the required subnet for Azure Bastion.
Open Bastions and select Create.
Select the required Subscription, Resource Group, and Virtual Network.
Configure the Azure Bastion name and required settings.
Configure or create the required Public IP address for Azure Bastion.
Review the configuration and select Create.
Wait for the Bastion deployment to complete.
Open the required Virtual Machine.
Select Connect → Bastion.
Enter the required VM credentials and establish the connection.
Learning Outcome
After completing this lab, you should be able to deploy Azure Bastion and use it to securely connect to an Azure Virtual Machine.
Practical 3: Connect to VM Without Public IP
Objective
To connect securely to an Azure Virtual Machine using Azure Bastion without assigning a public IP address to the VM.
Steps
Select an existing Azure Virtual Machine or create a new VM.
Verify that the VM has a private IP address.
Remove or avoid assigning a public IP address to the VM's Network Interface.
Make sure Azure Bastion is available in the VM's Virtual Network.
Open the VM in the Azure Portal.
Select Connect → Bastion.
Enter the required username and authentication details.
Establish the RDP connection for a Windows VM or SSH connection for a Linux VM.
Verify that the VM can be accessed successfully without a public IP address on the VM.
