Azure AD Full Group Aggregation Failure (429 Too Many Requests)

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Hi All,

We are encountering a persistent failure during our Azure AD full group aggregation process. The task consistently terminates with an HTTP 429 (Too Many Requests) error, indicating that the Microsoft Graph API is throttling our requests due to high volume.

Please suggest If you have come across this issue and found any solution.

2

@aniketnegi There is no configuration available for auto retries in case of 429 errors or to add a jitter while making connector is making api calls. What you can try is:

  • Enable Delta Aggregation
  • In Full Aggregation, create one task for one group type and run the tasks one after the other

You do few runs to determine, if you can merge few groups types to one task and whether you need to add a delay between the tasks.

Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(:heart:,:+1:, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

1 Like
3

have you tried with adding filter in application ?

some useful links:

Microsoft Graph throttling guidance - Microsoft Graph | Microsoft Learn

Aggregation, Filter, and Partitioning Settings

Customize Microsoft Graph Responses with Query Parameters - Microsoft Graph | Microsoft Learn

you can add retry that might be helpful.

4

@pravin_ranjan Could you please confirm if we have aggregation retry available for Azure/Entra connector? How can we do it?

5

Additional Settings please check here. we already have retry-After and retry list

6

I think this page is for ISC. In IIQ, there is no UI to set this but we can add it via debug in app xml under key = retryableErrorsOnAgg.

Thanks @pravin_ranjan for sharing this.

7

Its’ IIQ, you will find same info in connector doc.