Connector Release 2.13

November 17, 2025

Connector 2.13 introduces changes to tokens and the Azure connector.

Improved Resilience to Azure API Throttling

With this release, we have enhanced our Azure connector to provide increased resilience to API throttling. Azure APIs enforce rate limits on a per-application identity basis. When these limits are exceeded, Azure responds with an HTTP 429 - Too Many Requests error. Although retry logic was previously in place, it did not fully mitigate high-volume throttling scenarios.

To address this issue, we have introduced a fallback mechanism that uses multiple Azure App Registrations.

With this enhancement:

The system automatically detects throttling (HTTP 429) on the primary App Registration.
When a throttling scenario occurs, it retries the failed API request with a secondary App Registration, bypassing the rate limit of the original identity.
The system maintains seamless API access, even during high load scenarios.

As part of this enhancement, we have introduced new APIs to register and modify your Secondary Azure application. You can learn more about the APIs at the Connector Release 2.13 API Release Notes.

Implementation of QQL Token Standardization

We have now implemented Qualys Query Language (QQL) token standardization across all Qualys applications. As part of this enhancement, both common and TotalCloud-specific tokens are updated with new token names that follow a standard, consistent nomenclature.

The new token format follows the syntax provider.entity. attribute. For example, in the new token, aws.account.status, AWS is the provider, account is the entity, and status is the attribute.

Key Enhancements:

Standardized Token Naming: The tokens, such as insights, inventory, investigate, and controls, now adhere to a standardized naming convention. The tokens common to all Qualys applications have also been updated.
Search Bar Updates: Only the new tokens are displayed in the auto-suggestion in the search bars within the UI. However, if you type the old token name manually, the QQL query still works. The old tokens will not be visible in the auto-suggestions on the UI.
Backward Compatibility: The existing Dashboard widgets and Saved Search Queries will continue to support the old tokens in edit mode.
Improved Interoperability: The standardized tokens make it easier to copy and reuse the search query from one application to another, eliminating the need to remember multiple token names for different applications and similar searches.