Creation of article on outbound rules using Azure PowerShell

Author: asudbring

articles/load-balancer/TOC.yml

@@ -85,7 +85,7 @@
     href: load-balancer-standard-public-zonal-cli.md
   - name: Configure outbound rules
     items:
-    - name: Configure outbound rules - Cli
+    - name: Configure outbound rules - CLI
       href: configure-load-balancer-outbound-cli.md
     - name: Configure outbound rules - PowerShell
       href: configure-load-balancer-outbound-powershell.md

articles/load-balancer/configure-load-balancer-outbound-powershell.md

@@ -128,7 +128,7 @@ If you do not want to use a separate outbound pool, you can change the address p
 Create a Load Balancer with the inbound IP address using [New-AzLoadBalancer](https://docs.microsoft.com/powershell/module/az.network/new-azloadbalancer?view=azps-2.6.0) named *lb* that includes an inbound frontend IP configuration and a backend pool *bepoolinbound* that is associated with the public IP address *mypublicipinbound* that you created in the preceding step.
 
 ```azurepowershell-interactive
-New-AzLoadBalancer -Name lb -ResourceGroupName myresourcegroupoutbound -Location eastus -FrontendIpConfiguration $frontendIPin,$frontendIPout -BackendAddressPool $bepoolin,$bepoolout -Probe $probe -LoadBalancingRule $inboundrule -OutboundRule $outboundrule 
+New-AzLoadBalancer -Name lb -Sku Standard -ResourceGroupName myresourcegroupoutbound -Location eastus -FrontendIpConfiguration $frontendIPin,$frontendIPout -BackendAddressPool $bepoolin,$bepoolout -Probe $probe -LoadBalancingRule $inboundrule -OutboundRule $outboundrule 
 ```
 
 At this point, you can proceed with adding your VM's to the backend pool *bepoolinbound* __and__ *bepooloutbound* by updating the IP configuration of the respective NIC resources using [Add-AzNetworkInterfaceIpConfig](https://docs.microsoft.com/cli/azure/network/lb/rule?view=azure-cli-latest).