What's new in Azure Load Balancer?

Azure Load Balancer is updated regularly. Stay up to date with the latest announcements. This article provides you with information about:

  • The latest releases
  • Known issues
  • Bug fixes
  • Deprecated functionality (if applicable)

You can also find the latest Azure Load Balancer updates and subscribe to the RSS feed here.

Recent releases

Type Name Description Date added
SKU Basic Load Balancer is retiring on 30 September 2025 Basic Load Balancer will retire on 30th September 2025. Make sure to migrate to Standard SKU before this date. September 2022
SKU Gateway Load Balancer now generally available Gateway Load Balancer is a new SKU of Azure Load Balancer targeted for scenarios requiring transparent NVA (network virtual appliance) insertion. Learn more about Gateway Load Balancer or our supported third party partners. July 2022
SKU Gateway Load Balancer public preview Gateway Load Balancer is a fully managed service enabling you to deploy, scale, and enhance the availability of third party network virtual appliances (NVAs) in Azure. You can add your favorite third party appliance whether it is a firewall, inline DDoS appliance, deep packet inspection system, or even your own custom appliance into the network path transparently – all with a single click. November 2021
Feature Support for IP-based backend pools (General Availability) Azure Load Balancer supports adding and removing resources from a backend pool via an IPv4 or IPv6 addresses. This enables easy management of containers, virtual machines, and virtual machine scale sets associated with Load Balancer. It will also allow IP addresses to be reserved as part of a backend pool before the associated resources are created. Learn more here March 2021
Feature Instance Metadata support for Standard SKU Load Balancers and Public IPs Metadata of Standard Public IP addresses and Standard Load Balancer can now be retrieved through Azure Instance Metadata Service (IMDS). The metadata is available from within the running instances of virtual machines (VMs) and virtual machine scale sets instances. You can leverage the metadata to manage your virtual machines. Learn more here February 2021
Feature Public IP SKU upgrade from Basic to Standard without losing IP address As you move from Basic to Standard Load Balancers, retain your public IP address. Learn more here January 2021
Feature Support for moves across resource groups Standard Load Balancer and Standard Public IP support for resource group moves. October 2020
Feature Cross-region load balancing with Global tier on Standard LB Azure Load Balancer supports Cross Region Load Balancing. Previously, Standard Load Balancer had a regional scope. With this release, you can load balance across multiple Azure regions via a single, static, global anycast Public IP address. September 2020
Feature Azure Load Balancer Insights using Azure Monitor Built as part of Azure Monitor for Networks, customers now have topological maps for all their Load Balancer configurations and health dashboards for their Standard Load Balancers preconfigured with metrics in the Azure portal. Get started and learn more June 2020
Validation Addition of validation for HA ports A validation was added to ensure that HA port rules and non HA port rules are only configurable when Floating IP is enabled. Previously, this configuration would go through, but not work as intended. No change to functionality was made. You can learn more here June 2020
Feature IPv6 support for Azure Load Balancer (generally available) You can have IPv6 addresses as your frontend for your Azure Load Balancers. Learn how to create a dual stack application here April 2020
Feature TCP Resets on Idle Timeout (generally available) Use TCP resets to create a more predictable application behavior. Learn more February 2020

Known issues

The product group is actively working on resolutions for the following known issues:

Issue Description Mitigation
IP based LB outbound IP IP based LB leverages Azure's Default Outbound Access IP for outbound In order to prevent outbound access from this IP, please leverage NAT Gateway for a predictable IP address and to prevent SNAT port exhaustion
numberOfProbes, "Unhealthy threshold" Health probe configuration property numberOfProbes, otherwise known as "Unhealthy threshold" in Portal, is not respected. Load Balancer health probes will probe up/down immediately after 1 probe regardless of the property's configured value To reflect the current behavior, please set the value of numberOfProbes ("Unhealthy threshold" in Portal) as 1
Cross region balancer in West Europe Currently, there are a limited amount of IP addresses available in West Europe for Azure's cross region Load Balancer. This may impact customers' ability to deploy cross region load balancers in the West Europe region. We recommend that customers use another home region as part of their cross region deployment.

Next steps

For more information about Azure Load Balancer, see What is Azure Load Balancer? and frequently asked questions.