Azure Load Balancer
- Distributes incoming network traffic across multiple targets.
- Allows you to route traffic based on source IP address and port to a destination IP address and port.
- The load balancer supports TCP/UDP-based protocols.
- Scales automatically as traffic increases.
- The load-balancing decision is based on the following tuple connection:
- Source IP address and port
- Destination IP address and port
- NAT allows you to control the inbound and outbound network traffic.
- Inbound rules – traffic allowed to a specific virtual machine or instance in the backend pool.
- Outbound rules – enable all resources to communicate to the Internet.
- Control the flow of traffic inside your private virtual network using an internal load balancer.
- You can use a public load balancer to allow outbound connections for your virtual machines.
- Azure Load Balancer supports IPv6.
- Load balancer tiers: Basic and Standard
- A group of VMs or instances in a VM scale set serving the incoming request is called backend pool.
- Determine the health status of backend pool instances with health probes.
- Health probe down behavior – if the probes in a backend pool fail, it will stop receiving traffic until it starts passing health probes again.
- Standard load balancer availability zones:
- Zonal = single zone
- Zone-redundant = multiple zones
Basic Load Balancer
Standard Load Balancer
Backend pool size
Supports up to 300 instances.
Supports up to 1000 instances.
Backend pool endpoints
A single availability set for VMs or VM scale set.
A single virtual network for any VMs or VM scale sets.
TCP, HTTP, HTTPS
Health probe down behavior
TCP connections stay alive on an instance probe down. All TCP connections terminate when all probes are down.
TCP connections stay alive on an instance probe down and on all probes down.
Zone-redundant and zonal frontends for inbound and outbound traffic.
Azure Monitor logs
Azure Monitor multi-dimensional metrics
Available for Internal Load Balancer
Secure by default
Open by default. Network security group optional.
Closed to inbound flows unless allowed by a network security group. Please note that internal traffic from the VNet to the internal load balancer is allowed.
Declarative outbound NAT configuration
TCP Reset on Idle
Available on any rule
Inbound and outbound
60-90+ seconds typical
Most operations < 30 seconds
- You are charged based on the number of outbound rules.
- You are billed for the first five rules of load balancing.
- You are not charged for the NAT rules.
Azure Load Balancer vs App Gateway vs Traffic Manager:
How to Create a Load Balancer
Want to learn more about Azure? Watch the official Microsoft Azure YouTube channel’s video series called Azure Tips and Tricks.