---
title: "Azure Integration: Advanced Load Balancer Statistics"
slug: "azure-integration-load-balancer-statistics"
description: "New load balancer introduced for our Azure Integration which allows to better handle Azure API rate limits. Add multiple credentials to the connection settings"
updated: 2025-07-02T16:44:24Z
published: 2025-07-02T16:44:24Z
canonical: "support.controlup.com/azure-integration-load-balancer-statistics"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.controlup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Integration: Load Balancer Statistics

ControlUp Real-Time DX Console comes with an **AIP** feature which allows you to automatically distribute API calls across credentials that you should add to your [Azure connection in ControlUp](https://support.controlup.com/tim-reorg/docs/azure-integration-getting-started#create-the-azure-connection-in-controlup).

The maximum number of reading operations that can be performed on a credential at a subscription level is 12 000. Using only one credential can easily exhaust this limit in larger environments with many virtual machines or user sessions. You can read more about rate limits in the [official Microsoft documentation](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/request-limits-and-throttling).

          Important

          

Don't use the same credentials across different solutions. As best practice, create dedicated credentials for ControlUp.

## How to Identify Remaining Requests

The new **AZ AIP Stats** metric shows which credentials (service principals) are used to serve the communication with the corresponding Azure subscription. In the screenshot below you can see a number next to the *Friendly Name* of the service principal that calls the Azure API. This number represents the remaining read operations per credential. ![AZ AIP Stats column in the Folders view in the Console.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-Z8J1KAOE.png)

You can see the percentage utilization of API calls at the subscription level with the **AZ % Rate Limit Usage** metric. For example, a displayed value of 40% means that 40% of available API calls are utilized, with 60% left. In the example below, we show you an automation example that you can use to get notified if this value crosses the critical threshold of 95%. ![AZ% Rate Limit Usage column highlighted in the Folders view in the Console.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-GPJJ5G4W.png)

The **AZ % AIP Variance** is another important metric that is calculated as a percentage ratio of total remaining reads reduced by the lowest read count compared to the allowed read request count (usually 12 000).

Consider the scenario where two credentials are connected in ControlUp. The screenshot displays that one credential has 11,969 remaining requests while the other has 11,978. ![AZ AIP Stats column shows '119691' and '11978'.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-0T8LTZAS.png)

Taken the maximum number of allowed read request of 12 000 this would be (11 978 - 11 969) / 12 000 * 100 = 0.075 = **0.08%**

## Techniques to Mitigate API Rate Limitations

ControlUp will not be to request any further data from your Azure subscription once the request limit has been reached. Typically, there are two methods available to keep track of the request limit:

- Automatically [trigger an action](/tim-reorg/docs/azure-integration-load-balancer-statistics#create-automated-actions) when *AZ % Rate Limit Usage* exceeds a certain threshold
- Monitor the *AZ % Rate Limit Usage* metric manually

### Create Automated Actions

We recommend to set up an [Advanced Trigger](/tim-reorg/docs/triggers-and-alerts) for the **AZ % Rate Limit Usage** column with a specified threshold of 95%. When this threshold is exceeded, it should activate a follow-up action, such as sending an email or [Webhooks](/tim-reorg/docs/using-webhooks-as-follow-up-action). ![Automated Action editor using the condition AZ % Rate Limit Usage is greater than or equal to 95%.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-8EKP9UXN.png)