Skip to content

Commit 373d0af

Browse files
authored
Update inbound-nat-rules.md
1 parent 046bc9a commit 373d0af

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/load-balancer/inbound-nat-rules.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,17 @@ An inbound NAT rule is used for port forwarding. Port forwarding lets you connec
2121

2222
## Types of inbound NAT rules
2323

24-
There are two types of inbound NAT rule available for Azure Load Balancer, single virtual machine and multiple virtual machines.
24+
There are two types of inbound NAT rule available for Azure Load Balancer, version 1 and version 2.
25+
>[!NOTE]
26+
> The recommendation is to use Inbound NAT rule V2 for Standard Load Balancer deployments.
2527
26-
### Single virtual machine
28+
### Inbound NAT rule V1
2729

28-
A single virtual machine inbound NAT rule is defined for a single target virtual machine. The load balancer's frontend IP address and the selected frontend port are used for connections to the virtual machine.
30+
Inbound NAT rule V1 is defined for a single target virtual machine. Inbound NAT pools are feature of Inbound NAT rules V1 and automatically creates Inbound NAT rules per VMSS intance. The load balancer's frontend IP address and the selected frontend port are used for connections to the virtual machine.
2931

3032
:::image type="content" source="./media/inbound-nat-rules/inbound-nat-rule.png" alt-text="Diagram of a single virtual machine inbound NAT rule.":::
3133

32-
### Multiple virtual machines and virtual machine scale sets
34+
### Inbound NAT rule V2
3335

3436
A multiple virtual machines inbound NAT rule references the entire backend pool in the rule. A range of frontend ports are preallocated based on the rule settings of **Frontend port range start** and **Maximum number of machines in the backend pool**.
3537

0 commit comments

Comments
 (0)