Author: Michael Bender

articles/load-balancer/load-balancer-nat-pool-migration.md

@@ -1,6 +1,6 @@
 ---
 title: Migrate from Inbound NAT rules version 1 to version 2 
-description: Learn how to migrate from Inbound NAT rules version 1 to version 2 in Azure Load Balancer.
+description: Learn how to migrate Azure Load balancer from inbound NAT rules version 1 to version 2.
 services: load-balancer
 author: mbender-ms
 ms.service: azure-load-balancer
@@ -13,12 +13,11 @@ ms.author: mbender
 
 An [inbound NAT rule](inbound-nat-rules.md) is used to forward traffic from a load balancer’s frontend to one or more instances in the backend pool. These rules provide a 1:1 mapping between the load balancer’s frontend IP address and backend instances. There are currently two versions of Inbound NAT rules, version 1 and version 2.
 
-:::image type="content" source="media/load-balancer-nat-pool-migration/load-balancer-inbound-nat-rule-flow.png" alt-text="Diagram of load balancer inbound nat rules":::
-## Version 1 
+## NAT rule version 1 
 
-[Version 1](inbound-nat-rules.md) is the legacy approach for assigning an Azure Load Balancer’s frontend port to each backend instance. Rules are applied to the backend instance’s network interface card (NIC). For Virtual Machine Scale Sets (VMSS) instances, inbound NAT rules are automatically created/deleted as new instances are scaled up/down.  
+[Version 1](inbound-nat-rules.md) is the legacy approach for assigning an Azure Load Balancer’s frontend port to each backend instance. Rules are applied to the backend instance’s network interface card (NIC). For Azure Virtual Machine Scale Sets instances, inbound NAT rules are automatically created/deleted as new instances are scaled up/down.  
 
-## Version 2 
+## NAT rule version 2 
 
 [Version 2](inbound-nat-rules.md) of Inbound NAT rules provide the same feature set as version 1, with extra benefits.  
 
@@ -48,19 +47,21 @@ The following three steps need to be performed to migrate to version 2 of inboun
 1. Delete the version 1 of inbound NAT rules on the load balancer’s configuration.
 2. Remove the reference to the NAT rule on the virtual machine or virtual machine scale set configuration.
    1. All virtual machine scale set instances need to be updated.
-3. Deploy version 2 of Inbound NAT rules  
+3. Deploy version 2 of Inbound NAT rules.
 
 ### Virtual Machine
 
+The following steps are used to migrate from version 1 to version 2 of Inbound NAT rules for a virtual machine.
+
 # [Azure CLI](#tab/azure-cli)
 
 ```azurecli
 
-az network lb inbound-nat-rule delete -g MyResourceGroup --lb-name MyLoadBalancer --name NATRule 
+az network lb inbound-nat-rule delete -g MyResourceGroup --lb-name MyLoadBalancer --name NATruleV1
 
-az network nic ip-config inbound-nat-rule remove -g MyResourceGroup --nic-name MyNic -n MyIpConfig --inbound-nat-rule MyNatRul 
+az network nic ip-config inbound-nat-rule remove -g MyResourceGroup --nic-name MyNic -n MyIpConfig --inbound-nat-rule MyNatRule 
 
-az network lb inbound-nat-rule create -g MyResourceGroup --lb-name MyLoadBalancer -n MyNatRule --protocol Tcp --frontend-port-range-start 201 --frontend-port-range-end 500 --backend-port 80 
+az network lb inbound-nat-rule create -g MyResourceGroup --lb-name MyLoadBalancer -n MyNatRule --protocol Tcp --frontend-port-range-start 201 --frontend-port-range-end 500 --backend-port 22 
 
 ```
 
@@ -80,12 +81,20 @@ $nic.IpConfigurations[0].LoadBalancerInboundNatRule  = $null
 
 Set-AzNetworkInterface -NetworkInterface $nic
 
+$slb | Add-AzLoadBalancerInboundNatRuleConfig -Name "NewNatRuleV2" -FrontendIPConfiguration $slb.FrontendIpConfigurations[0] -Protocol "Tcp" -FrontendPortRangeStart 201-FrontendPortRangeEnd 500 -BackendAddressPool $slb.BackendAddressPools[0] -BackendPort 22
+$slb | Set-AzLoadBalancer
+
+
 ```
 ---
 
 
 ### Virtual Machine Scale Set
 
+The following steps are used to migrate from version 1 to version 2 of Inbound NAT rules for a virtual machine scale set. It assumes the virtual machine scale set's upgrade mode is set to Manual. For more information, see [Orchestration modes for Virtual Machine Scale Sets in Azure](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes)
+
+
+
 # [Azure CLI](#tab/azure-cli)
 
 ```azurecli
@@ -96,7 +105,7 @@ az vmss update -g MyResourceGroup -n MyVMScaleSet --remove virtualMachineProfile
 
 az vmss update-instances --instance-ids '*' --resource-group MyResourceGroup --name MyVMScaleSet 
 
-az network lb inbound-nat-rule create -g MyResourceGroup --lb-name MyLoadBalancer -n MyNatRule --protocol Tcp --frontend-port-range-start 201 --frontend-port-range-end 500 --backend-port 80 
+az network lb inbound-nat-rule create -g MyResourceGroup --lb-name MyLoadBalancer -n MyNatRule --protocol Tcp --frontend-port-range-start 201 --frontend-port-range-end 500 --backend-port 22 
 
 ```
 
@@ -122,13 +131,16 @@ Update-AzVmss -ResourceGroupName $resourceGroupName -Name $vmssName -VirtualMach
 
 # Upgrade all instances in the VMSS 
 
-Update-AzVmssInstance -ResourceGroupName $resourceGroupName -VMScaleSetName $vmssName -InstanceId "*" 
+Update-AzVmssInstance -ResourceGroupName $resourceGroupName -VMScaleSetName $vmssName -InstanceId "*"
+
+$slb | Add-AzLoadBalancerInboundNatRuleConfig -Name "NewNatRuleV2" -FrontendIPConfiguration $slb.FrontendIpConfigurations[0] -Protocol "Tcp" -FrontendPortRangeStart 201-FrontendPortRangeEnd 500 -BackendAddressPool $slb.BackendAddressPools[0] -BackendPort 22
+$slb | Set-AzLoadBalancer
+ 
 ```
 ---
 
 ## Migration with automation script for Virtual Machine Scale Set 
 
-> [!NOTE] This script is designed to work if there is only one VMSS instance attached to your load balancer.  
 
 ### Prerequisites