Player traffic source
Remember LB
Full name: Azure Load Balancer
Memory aid: Load is Balanced among the Azure backends.
Azure Load Balancer is different from an HTTP-aware application gateway.
Study area: Azure & hybrid migration · Batch 9
Relevant study for: CompTIA Cloud+ · Azure Fundamentals AZ-900 · ISC2 CCSP · Azure Administrator AZ-104 · Azure Solutions Architect AZ-305 · Azure Network Engineer AZ-700
Practice with exam flashcards →Cloud / Knowledge library
Azure Load Balancer
Provides Layer 4 load balancing for public and private Azure endpoints
Why learn Azure Load Balancer?
Teams use Azure Load Balancer to adopt managed load balancing without building the complete underlying platform themselves.
The problem it solves
Distributes traffic across healthy application endpoints
Where it came from
Azure Load Balancer is Microsoft Azure's offering for managed load balancing. Its closest catalog counterparts are Elastic Load Balancing and Google Cloud Load Balancing; they address the same broad need but are not feature-for-feature identical.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Explain the main responsibility of Azure Load Balancer.
- Choose a workload that fits Azure Load Balancer.
- Identify one operational tradeoff of Azure Load Balancer.
- Compare Azure Load Balancer with Elastic Load Balancing.
- Compare Azure Load Balancer with Google Cloud Load Balancing.
Documentation and sources
- Microsoft Azure product catalog (azure.microsoft.com)
Connect the ideas
Alternatives
Real World Example
High-Availability Gaming Backend Distribution
Online gaming companies requiring consistent, low-latency connectivity for thousands of concurrent players connecting to stateful game servers.
The business problem
Individual game server instances are prone to unexpected termination, leading to player disconnection and loss of session state during peak traffic.
How this topic solves it
Azure Load Balancer provides Layer 4 load balancing to distribute incoming UDP/TCP traffic across a pool of backend virtual machines, ensuring traffic is only routed to healthy instances.
- Create a backend pool containing the IP addresses of the game server virtual machines.
- Define health probes that periodically check the status of each game server instance.
- Configure load balancing rules to map frontend IP ports to the backend pool ports.
- Associate the load balancer with a public IP or internal virtual network endpoint.
Shows how external traffic is routed through the load balancer to backend resources.
Entry point for traffic
Layer 4 distribution logic
Group of game server VMs
- Internet → requests → Frontend IP
- Frontend IP → forwards → Load Balancer
- Load Balancer → distributes → Backend Pool
Expected business outcome
Improved service availability where player traffic is automatically rerouted away from unresponsive server instances without manual intervention.
Limitations and checks
Azure Load Balancer operates at Layer 4 and does not inspect application-layer (HTTP/HTTPS) content; to verify if the application is truly processing requests correctly, you must rely on port-based health probes rather than deep content inspection.