Merge pull request #230169 from rdeltcheva/ilb-out-smallfix

Change NAT GW to outbound ILB rules

Author: prmerger-automator[bot]

articles/sap/workloads/high-availability-guide-standard-load-balancer-outbound-connections.md

@@ -13,7 +13,7 @@ ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 12/01/2020
+ms.date: 3/9/2023
 ms.author: radeltch
 
 ---
@@ -95,7 +95,11 @@ The configuration would look like:
 2. Create Backend pool **MyBackendPoolOfPublicILB** and add the VMs.  
    1. Select the Virtual network  
    1. Select the VMs and their IP addresses and add them to the backend pool  
-3. Create a NAT gateway for outbound internet access. For more information see [Quickstart: Create a NAT gateway - Azure CLI](../../virtual-network/nat-gateway/quickstart-create-nat-gateway-cli.md).
+3. Create [outbound rules](../../load-balancer/egress-only.md#create-a-public-load-balancer-outbound-rule).  
+
+   ```azurecli
+    az network lb outbound-rule create --address-pool MyBackendPoolOfPublicILB --frontend-ip-configs MyPublicILBFrondEndIP --idle-timeout 30 --lb-name MyPublicILB --name MyOutBoundRules  --outbound-ports 10000 --enable-tcp-reset true --protocol All --resource-group MyResourceGroup
+
 4. Create Network Security group rules to restrict access to specific Public End Points. If there is existing Network Security Group, you can adjust it. The example below shows how to enable access to the Azure management API: 
    1. Navigate to the Network Security Group
    1. Click Outbound Security Rules