Study guide
5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design
Designing and Implementing Microsoft Azure Networking Solutions AZ-700
Track your progress as you read
Finished sections get a check mark.
1 Introduction & AZ-700 Exam Overview
0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured
2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture
1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)
3 Chapter 2: Azure Name Resolution & Core Routing
2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange
4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway
3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter
5 Chapter 4: Azure ExpressRoute & Virtual WAN
4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting
6 Chapter 5: Regional Load Balancing & Application Gateway
5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design
7 Chapter 6: Global Traffic Management & Azure Front Door
6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door
8 Chapter 7: Azure Private Link & Service Endpoints
7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions
9 Chapter 8: Network Security Groups & Azure Bastion
8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules
10 Chapter 9: Azure Firewall & Security Policies
9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection
11 Chapter 10: Azure Network Observability & Troubleshooting
10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture
5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design
Key Takeaways Explain This Topic AI
An inbound NAT rule performs port forwarding from a load balancer frontend IP and port to a specific backend instance and port, and unlike a load balancing rule it does not require a health probe.
Inbound NAT rule V1 gives a 1:1 mapping between one frontend port and one backend virtual machine, which remains fully supported for single-VM RDP or SSH access.
Inbound NAT rule V2 references the entire backend pool and preallocates a frontend port range from a start port and a maximum backend pool size, creating and removing per-instance mappings automatically as the pool scales.
Inbound NAT Pools, the scale-set feature of inbound NAT rule V1, are retiring on September 30, 2027, and new pools cannot be created after November 15, 2026; single-VM V1 rules are unaffected.
Every Azure Load Balancer health probe originates from 168.63.129.16, so an NSG or host firewall that blocks that address marks every backend instance unhealthy and the load balancing rule stops delivering traffic.
Last updated: August 2026
Inbound NAT Rules, Port Forwarding & Health Probe Design
A load balancing rule spreads traffic on one frontend port across many backend instances. An inbound NAT rule does the opposite: it forwards traffic arriving on one frontend port to one specific backend instance on a chosen backend port. It is Azure's port-forwarding primitive, and it is the standard way to reach individual virtual machines for management without giving each one a public IP address.
Construct Purpose Health probe required?
- Load balancing rule Distribute a flow across all healthy backend instances Yes
- Inbound NAT rule Port-forward to a specific backend instance No
- Outbound rule Explicit SNAT for backend-initiated internet flows No
Important
Inbound NAT rules do not need a health probe attached. This is stated explicitly in the documentation and is a reliable exam discriminator: an option that claims a NAT rule failed because its health probe was misconfigured is describing a load balancing rule, not a NAT rule.
1. Inbound NAT Rule V1 — Single Virtual Machine
V1 provides a straightforward 1:1 port mapping between a load balancer frontend IP and port, and one specific backend virtual machine and port.
- Element Example
- Frontend IP / port 20.51.x.x:50001
- Backend VM / port 10.10.1.4:3389
- Typical use RDP or SSH to an individual VM through the load balancer
The classic pattern is one NAT rule per VM — 50001 to VM1:3389, 50002 to VM2:3389, and so on — so a jump-host-free administrative path exists without publishing a public IP per machine. Microsoft states that for a single virtual machine port, inbound NAT rule V1 continues to be fully supported .
2. Inbound NAT Rule V2 — Backend Pool with a Port Range
V2 is the recommended option for Standard Load Balancer deployments that target multiple virtual machines or virtual machine scale sets . Instead of naming one VM, a V2 rule references the entire backend pool .
- Setting What it does
- Frontend port range start The first frontend port Azure will allocate
Maximum number of machines in the backend pool Determines how many ports Azure preallocates from the start port
Backend port The single port on each instance that traffic is forwarded to, for example 3389
Azure preallocates the frontend port range when the rule is created and then creates per-instance port mappings from within it.
Scaling behaviour
Scale down — existing port mappings for the remaining VMs persist . Instance-to-port assignments are stable.
Scale up — new port mappings are created automatically for the new instances. No update to the NAT rule is required.
Warning
Undersizing the port range blocks scaling. If the predefined frontend port range does not have enough free ports, scaling up the backend pool is blocked, which can leave new instances with no network connectivity. Size the "maximum number of machines" setting for the pool's eventual ceiling, not its current size.
You can retrieve the actual per-VM port mappings in the portal from the load balancer's inbound NAT rule view.
3. Inbound NAT Pools Are Retiring
Inbound NAT Pools are a feature of inbound NAT rule V1 that automatically create a NAT rule per virtual machine scale set instance from a frontend port range.
- Date Event
- November 15, 2026 You can no longer create new inbound NAT pools
- September 30, 2027 Inbound NAT Pools are retired
The documented migration path is to move scale-set deployments to inbound NAT rule V2 . Single-VM inbound NAT rule V1 configurations are explicitly not affected by this retirement.
4. Health Probes: What They Actually Gate
Health probes determine which backend instances a load balancing rule will deliver new flows to. They do not gate inbound NAT rules.
- Probe protocol Success condition Typical use
- TCP The TCP handshake completes on the probe port Generic services with no HTTP endpoint
- HTTP The probe path returns HTTP 200 within the timeout Web tiers where a real health endpoint exists
- HTTPS The probe path returns HTTP 200 over TLS Standard SKU only; web tiers requiring encrypted probing
- The probe source address
All Azure Load Balancer health probes originate from the Azure infrastructure address 168.63.129.16 . Three practical consequences:
The AzureLoadBalancer service tag must be permitted inbound on the backend NSG. It is allowed by an NSG default rule, so problems appear only when someone writes a higher-priority deny.
A host firewall on the guest OS — Windows Defender Firewall, iptables , nftables — must also allow the probe port from 168.63.129.16 .
If every instance fails its probe, Standard Load Balancer stops delivering new flows entirely. Note the asymmetry: existing management access through an inbound NAT rule keeps working , because NAT rules do not consult the probe. "I can still RDP to the VMs through the load balancer, but the application VIP returns nothing" is the textbook signature of a probe failure.
Tip
Prefer an HTTP or HTTPS probe against a purpose-built health endpoint over a bare TCP probe for web tiers. A TCP probe only proves the listener socket is open; it will happily report a web server as healthy while every request returns HTTP 500.