Articles → MICROSOFT AZURE → Inbound NAT Rules In Load Balancer

Inbound NAT Rules In Load Balancer

In this article, we will discuss inbound NAT rules in the load balancer.

Purpose

Consider a scenario where a load balancer has 2 virtual machines i.e., "vmone" and "vmtwo" in its backend pool. As public IP addresses of both the virtual machines are dissociated. So, we need a mechanism for the administrator to log into the virtual machine.

Inbound NAT rules give you an option by using port mapping.

Virtual Machines And Load Balancer

For this example, we will use the following virtual machine.

Picture showing the IP address of the load balancer mapped to the virtual machines

Click to Enlarge

And the following load balancer.

Picture showing the public IP address of the load balancer

Click to Enlarge

Create Inbound NAT Rules

To create the inbound NAT rules, you can go to the "Inbound NAT rules" submenu inside the load balancer. Click on the "+ Add" button to add the rules.

Picture showing the Add button for adding the inbound NAT rules in load balancer

Click to Enlarge

Here, we will create 2 rules: -

Map port 4000 with 3389 for virtual machine "vmone"

Picture showing the rule 1 for mapping port 4000 with the virtual machine one

Click to Enlarge

Map port 4001 with 3389 for virtual machine "vmtwo"

Picture showing the rule 1 for mapping port 4001 with the virtual machine two

Click to Enlarge

How To Login To A Virtual Machine Using RDP?

To login to the virtual machine, you can use the IP address in the following format: -

<public ip of load balancer>:<port number mapped>

Picture showing the login screen for virtual machines logged in using port 4000 and 4001

Click to Enlarge

Posted By -	Karan Gupta

Posted On -	Monday, May 17, 2021

Query/Feedback

Your Email Id		**

Subject		*

Query/Feedback	Characters remaining 250	**