This section dicusses about the various resource limits to consider while integrating Microsoft Azure with Avi Load Balancer.

Microsoft Azure Load Balancer supports the following SKUs:

  • Standard

  • Basic

For a comparison between these two SKUs, see Microsoft Azure Load Balancer.

Microsoft Azure objects have predefined limits to the number of instances that can be instantiated.

These limits are based on the location of a given subscription. For instance, the total number of cores that can be used by the subscription in a particular location defines these limits.

The following limits must be increased appropriately to allow scaling Avi Load Balancer virtual service and object creation in Microsoft Azure:

  • Networking Limits

  • Load Balancer Limits

Networking Limits

Public IP addresses - Static. The default value is 20. This value should be increased if the deployment is expected to have more 20 public IPs.

Load Balancer Limit

  1. Frontend IP configuration - Basic

    The default value is 10. It is recommended to set this to a higher value. Each virtual service IP and port combination consumes one frontend IP configuration.

  2. Rules per resource - Basic

    The default value is 150. It is recommended to increase this to a higher value. Each virtual service IP and port combination consumes one rule.

  3. Load Balancers

    The default value is 100. This limit should be raised as required if more than 100 Service Engine groups are expected.

The above limits can be increased by submitting a request to Microsoft Azure using a support case. For more information, see Azure subscription and service limits, quotas, and constraints.

Note:

Azure Cloud in Avi Load Balancer starts to use Azure Standard Load Balancer by default instead of Azure Basic Load Balancer for Service Engine placements. Azure Basic Load Balancer will be retired on 30 September 2025.

Controller Cluster having Azure cloud will have the following warning message on the Controller:

Azure Basic LB will be discontinued on September 30, 2025. If you plan on continuing to use Azure, we recommend using Standard ALB.

A migration guide for moving virtual services to a new SE group with standard ALB will be provided via a separate knowledge base article. These guides would not be tied to any release, and customers can plan these in any of the Avi releases they are running.