If you want to load balance between your servers in a region at the application layer, review Application Gateway.If you are looking to do DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination ('SSL offload'), per-HTTP/HTTPS request or application-layer processing, review Traffic Manager.

A load balancer frontend can be accessed from an on-premises network in a hybrid scenario.įigure: Balancing multi-tier applications by using both public and internal Load Balancerįor more information on the individual load balancer components, see Azure Load Balancer components.Īzure provides a suite of fully managed load-balancing solutions for your scenarios. Internal load balancers are used to load balance traffic inside a virtual network. Public Load Balancers are used to load balance internet traffic to your VMs.Īn internal (or private) load balancer is used where private IPs are needed at the frontend only. These connections are accomplished by translating their private IP addresses to public IP addresses. The backend pool instances can be Azure Virtual Machines or instances in a Virtual Machine Scale Set.Ī public load balancer can provide outbound connections for virtual machines (VMs) inside your virtual network. These flows are according to configured load-balancing rules and health probes. Load balancer distributes inbound flows that arrive at the load balancer's front end to backend pool instances. It's the single point of contact for clients. Load balancing refers to evenly distributing load (incoming network traffic) across a group of backend resources or servers.Īzure Load Balancer operates at layer 4 of the Open Systems Interconnection (OSI) model.

Waf load balancer