Scribd
Upload
9 views3 pages

Types of Inbound NAT Rules in Azure

The document outlines the types of Inbound NAT Rules in Azure Load Balancer, categorizing them into four main types: Basic NAT Rule, Floating IP Enabled NAT Rule, Multiple NAT Rules with Same Backend Port, and Internal NAT Rule. Each type has specific use cases, such as remote access, Direct Server Return, and private network access. Configuration options for these rules include frontend IP, protocol, and port settings.

Uploaded by

math48647
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views3 pages

Types of Inbound NAT Rules in Azure

The document outlines the types of Inbound NAT Rules in Azure Load Balancer, categorizing them into four main types: Basic NAT Rule, Floating IP Enabled NAT Rule, Multiple NAT Rules with Same Backend Port, and Internal NAT Rule. Each type has specific use cases, such as remote access, Direct Server Return, and private network access. Configuration options for these rules include frontend IP, protocol, and port settings.

Uploaded by

math48647
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

When you ask "type of that?

" in the context of Inbound NAT Rules in


Azure Load Balancer, it likely refers to the types or variations of inbound
NAT rules you can configure.

Let me explain the types and configurations available.

🔄 Types of Inbound NAT Rules in Azure Load


Balancer
There are no official named types like "Type A" or "Type B," but based on
configuration and use case, you can categorize them as:

1. ✅ Basic NAT Rule (Per-VM Port Mapping)

Use case: Remote access like RDP or SSH


Example: External port 50001 → VM1 port 3389 (RDP)

 Frontend: Public or internal IP


 Protocol: TCP or UDP
 Frontend Port: Custom (e.g., 50001)
 Backend Port: Actual service port (e.g., 3389)
 Target: Specific VM and NIC in backend pool

This is the most common type used for:

 RDP to Windows VMs


 SSH to Linux VMs
 Direct VM services

2. 🧠 Floating IP Enabled NAT Rule

Use case: For scenarios requiring Direct Server Return (DSR) —


especially NVAs (firewalls, packet brokers)
 Same as a basic rule, but with Floating IP enabled
 Ensures symmetrical traffic (entry and exit through same path)
 Preserves source/destination IPs

Used in:

 Gateway Load Balancer


 Appliance insertion (e.g., firewall or DPI tools)

3. 🔁 Multiple NAT Rules with Same Backend Port (Port


Translation)

Use case: Accessing multiple VMs on the same port using different
frontend ports

Example:

Public Target Target


Port VM Port
50001 VM1 3389
50002 VM2 3389

This setup allows multiple VMs to be accessible through unique external


ports, even if they all use the same internal service port.

4. Internal NAT Rule (Private Load Balancer)

Use case: When the load balancer is internal (no public IP)

 Useful in hub-spoke networks or private management networks


 Same port forwarding applies, but traffic comes from inside the VNet

Example: Bastion or jumpbox scenarios.


📌 Configuration Options That Define Type
Setting Options
Frontend
Public or Private
IP
Protocol TCP, UDP, or All
Floating IP Enabled or Disabled
Frontend
Any custom port
Port
Backend
Target VM's port
Port
Idle
Customizable
Timeout
Optional — sends reset on idle
TCP Reset
timeout

Summary Table
"Type" Description Use Case
RDP, SSH, service
Basic NAT Rule One-to-one port forwarding to VM
access
NVAs, Gateway Load
NAT Rule with Floating IP Enables DSR, symmetric flows
Balancer
Port Translation for Use different frontend ports for same Access many VMs
Multiple VMs service port individually
Internal NAT Rule NAT on private frontend IP Private VNet access

You might also like