Configure load balancing and outbound rules in Standard Load Balancer using Azure CLI
This quickstart shows you how to configure outbound rules in Standard Load Balancer using Azure CLI.
When you are done, the Load Balancer resource contains two frontends and rules associated with them: one for inbound and another for outbound. Each frontend has a reference to a public IP address and this scenario uses a different public IP address for inbound versus outbound. The load balancing rule provides only inbound load balancing and the outbound rule controls the outbound NAT provided for the VM. This quickstart uses two separate backend pools, one for inbound and one for outbound, to illustrate capability and allow for flexibility for this scenario.
Use Azure Cloud Shell
Azure hosts Azure Cloud Shell, an interactive shell environment that you can use through your browser. Cloud Shell lets you use either
PowerShell to work with Azure services. You can use the Cloud Shell pre-installed commands to run the code in this article without having to install anything on your local environment.
To launch Azure Cloud Shell:
|Select Try It in the upper-right corner of a code block. Selecting Try It doesn't automatically copy the code to Cloud Shell.|
|Go to https://shell.azure.com or select the Launch Cloud Shell button to open Cloud Shell in your browser.|
|Select the Cloud Shell button on the top-right menu bar in the Azure portal.|
To run the code in this article in Azure Cloud Shell:
Launch Cloud Shell.
Select the Copy button on a code block to copy the code.
Paste the code into the Cloud Shell session with Ctrl+Shift+V on Windows and Linux, or Cmd+Shift+V on macOS.
Press Enter to run the code.
If you choose to install and use the CLI locally, this tutorial requires that you are running a version of the Azure CLI version 2.0.28 or later. To find the version, run
az --version. If you need to install or upgrade, see Install Azure CLI 2.0.
Create resource group
Create a resource group with az group create. An Azure resource group is a logical container into which Azure resources are deployed and managed.
The following example creates a resource group named myresourcegroupoutbound in the eastus2 location:
az group create \ --name myresourcegroupoutbound \ --location eastus2
Create virtual network
Create a virtual network named myvnetoutbound with a subnet named mysubnetoutbound in the myresourcegroupoutbound using az network vnet create.
az network vnet create \ --resource-group myresourcegroupoutbound \ --name myvnetoutbound \ --address-prefix 192.168.0.0/16 \ --subnet-name mysubnetoutbound --subnet-prefix 192.168.0.0/24
Create inbound Public IP address
To access your web app on the Internet, you need a public IP address for the load balancer. A Standard Load Balancer only supports Standard Public IP addresses. Use az network public-ip create to create a Standard Public IP address named mypublicipinbound in myresourcegroupoutbound.
az network public-ip create --resource-group myresourcegroupoutbound --name mypublicipinbound --sku standard
Create outbound public IP address
Create a Standard IP address for Load Balancer's frontend outbound configuration using az network public-ip create.
az network public-ip create --resource-group myresourcegroupoutbound --name mypublicipoutbound --sku standard
Create Azure Load Balancer
This section details how you can create and configure the following components of the load balancer:
- A frontend IP that receives the incoming network traffic on the load balancer.
- A backend pool where the frontend IP sends the load balanced network traffic.
- A backend pool for outbound connectivity.
- A health probe that determines health of the backend VM instances.
- A load balancer inbound rule that defines how traffic is distributed to the VMs.
- A load balancer outbound rule that defines how traffic is distributed from the VMs.
Create Load Balancer
Create a Load Balancer with the inbound IP address using az network lb create 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.
az network lb create \ --resource-group myresourcegroupoutbound \ --name lb \ --sku standard \ --backend-pool-name bepoolinbound \ --frontend-ip-name myfrontendinbound \ --location eastus2 \ --public-ip-address mypublicipinbound
Create outbound pool
Create an additional backend address pool to define outbound connectivity for a pool of VMs with az network lb address-pool create with the name bepooloutbound. Creating a separate outbound pool provides maximum flexibility, but you can omit this step and only use the inbound bepoolinbound as well.
az network lb address-pool create \ --resource-group myresourcegroupoutbound \ --lb-name lb \ --name bepooloutbound
Create outbound frontend IP
Create the outbound frontend IP configuration for the Load Balancer with az network lb frontend-ip create that includes and outbound frontend IP configuration named myfrontendoutbound that is associated to the public IP address mypublicipoutbound
az network lb frontend-ip create \ --resource-group myresourcegroupoutbound \ --name myfrontendoutbound \ --lb-name lb \ --public-ip-address mypublicipoutbound
Create health probe
A health probe checks all virtual machine instances to make sure they can send network traffic. The virtual machine instance with failed probe checks is removed from the load balancer until it goes back online and a probe check determines that it's healthy. Create a health probe with az network lb probe create to monitor the health of the virtual machines.
az network lb probe create \ --resource-group myresourcegroupoutbound \ --lb-name lb \ --name http \ --protocol http \ --port 80 \ --path /
Create load balancing rule
A load balancer rule defines the frontend IP configuration for the incoming traffic and the backend pool to receive the traffic, along with the required source and destination port. Create a load balancer rule myinboundlbrule with az network lb rule create for listening to port 80 in the frontend pool myfrontendinbound and sending load-balanced network traffic to the backend address pool bepool also using port 80.
This load balancing rule disables automatic outbound (S)NAT as a result of this rule with the --disable-outbound-snat parameter. Outbound NAT is only provided by the outbound rule.
az network lb rule create \ --resource-group myresourcegroupoutbound \ --lb-name lb \ --name inboundlbrule \ --protocol tcp \ --frontend-port 80 \ --backend-port 80 \ --probe http \ --frontend-ip-name myfrontendinbound \ --backend-pool-name bepoolinbound \ --disable-outbound-snat
Create outbound rule
An outbound rule defines the frontend public IP, represented by the frontend myfrontendoutbound, which will be used for all outbound NAT traffic as well as the backend pool to which this rule applies. Create an outbound rule myoutboundrule for outbound network translation of all virtual machines (NIC IP configurations) in bepool backend pool. The command below also changes the outbound idle timeout from 4 to 15 minutes and allocates 10000 SNAT ports instead of 1024. Review outbound rules for more details.
az network lb outbound-rule create \ --resource-group myresourcegroupoutbound \ --lb-name lb \ --name outboundrule \ --frontend-ip-configs myfrontendoutbound \ --protocol All \ --idle-timeout 15 \ --outbound-ports 10000 \ --address-pool bepooloutbound
If you do not want to use a separate outbound pool, you can change the address pool argument in the preceding command to specify bepoolinbound instead. We recommend to use separate pools for flexibility and readability of the resulting configuration.
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 az network nic ip-config address-pool add.
Clean up resources
When no longer needed, you can use the az group delete command to remove the resource group, load balancer, and all related resources.
az group delete --name myresourcegroupoutbound
In this article, you created Standard Load Balancer, configured both inbound load balancer traffic rules, configured and health probe for the VMs in the backend pool. To learn more about Azure Load Balancer, continue to the tutorials for Azure Load Balancer.