Azure Documentation

Microsoft Learn

Azure Load Balancer

Introduction to Azure Load Balancer

Azure Load Balancer is a highly available and scalable cloud service that provides Layer 4 (TCP/UDP) load balancing. It distributes incoming traffic among a pool of backend resources, such as virtual machines or virtual machine scale sets, to ensure application availability and responsiveness.

Load balancing is crucial for building resilient and performant applications in the cloud. It helps in:

  • Improving Availability: By distributing traffic across multiple instances, it prevents a single point of failure. If one instance becomes unavailable, the load balancer redirects traffic to healthy instances.
  • Enhancing Scalability: As demand grows, you can add more backend instances, and the load balancer will automatically distribute traffic to them, allowing your application to scale seamlessly.
  • Increasing Performance: By distributing the load, it prevents any single instance from being overwhelmed, leading to faster response times and a better user experience.
Key Features

Azure Load Balancer offers a range of features to meet diverse load balancing needs:

  • High Availability: Built into the Azure platform for automatic failover.
  • SKUs: Standard and Basic SKUs offer different capabilities and pricing. Standard SKU is recommended for production workloads due to its enhanced features like availability zones and inbound NAT rules.
  • Health Probes: Monitor the health of backend instances and remove unhealthy instances from the load balancing pool.
  • Session Persistence (Sticky Sessions): Direct subsequent requests from the same client to the same backend instance.
  • Direct Server Return (DSR): An optional configuration for advanced scenarios.
  • Network Address Translation (NAT): Supports inbound NAT rules for direct access to specific services on backend instances.

Types of Azure Load Balancers

Azure provides several load balancing solutions, with Azure Load Balancer being a foundational service for Layer 4 load balancing.

Azure Load Balancer (Layer 4)

This is the core service described in this article. It operates at the transport layer and distributes traffic based on IP address and port.

Azure Application Gateway (Layer 7)

For HTTP/HTTPS traffic, Azure Application Gateway provides advanced Layer 7 load balancing capabilities, including SSL termination, Web Application Firewall (WAF), and URL-based routing.

Azure Front Door

A global, scalable entry-point that uses the Microsoft global edge network to create fast, secure, and widely scalable web applications and APIs. It offers global load balancing, SSL offloading, CDN capabilities, and WAF.

While Azure Load Balancer is a robust Layer 4 solution, choosing the right service depends on your application's requirements.

Configuring Azure Load Balancer

Setting up an Azure Load Balancer typically involves the following steps:

1. Create a Load Balancer Resource

You can create a load balancer through the Azure portal, Azure CLI, Azure PowerShell, or ARM templates.

# Example using Azure CLI
az network lb create \
    --resource-group myResourceGroup \
    --name myLoadBalancer \
    --sku Standard \
    --frontend-ip-name myFrontendIP \
    --public-ip-address myPublicIP

2. Define a Backend Pool

A backend pool contains the virtual machines or scale sets that will receive traffic. You associate Network Interfaces (NICs) with the backend pool.

3. Configure Health Probes

Health probes are essential for the load balancer to determine the health of backend instances. You can use TCP, HTTP, or HTTPS probes.

# Example using Azure CLI for HTTP health probe
az network lb probe create \
    --resource-group myResourceGroup \
    --lb-name myLoadBalancer \
    --name myHealthProbe \
    --protocol Http \
    --port 80 \
    --path /health

4. Create Load Balancing Rules

Load balancing rules define how traffic is distributed. They map a frontend IP address and port to a backend pool and port, and specify the health probe to use.

# Example using Azure CLI for a load balancing rule
az network lb rule create \
    --resource-group myResourceGroup \
    --lb-name myLoadBalancer \
    --name myHTTPRule \
    --protocol Tcp \
    --frontend-port 80 \
    --backend-port 80 \
    --frontend-ip-name myFrontendIP \
    --backend-pool-name myBackendPool \
    --probe-name myHealthProbe

5. (Optional) Configure Inbound NAT Rules

If you need direct access to specific services on backend VMs, you can configure inbound NAT rules.

Use Cases

Azure Load Balancer is ideal for a wide range of scenarios:

  • Web Applications: Distributing incoming web traffic across multiple web servers.
  • N-Tier Applications: Load balancing traffic between different tiers of an application (e.g., web tier, application tier, data tier).
  • High-Performance Computing (HPC): Distributing computational tasks across a cluster of machines.
  • Internet of Things (IoT): Managing high volumes of incoming device telemetry data.
  • Microservices: Providing a stable endpoint for distributed microservice architectures.

Best Practices

To maximize the benefits of Azure Load Balancer:

  • Use the Standard SKU: For production workloads, the Standard SKU offers superior features and reliability.
  • Implement Health Probes: Configure comprehensive health probes to ensure only healthy instances receive traffic.
  • Leverage Availability Zones: For zone-redundant applications, deploy load balancer resources across multiple availability zones.
  • Monitor Performance: Utilize Azure Monitor to track load balancer metrics and backend instance health.
  • Secure Your Application: Consider using Network Security Groups (NSGs) and potentially Azure Firewall or Azure WAF in conjunction with your load balancer.

Related Documentation