Let Azure AD retry failed exports with 429 response code as soon as the Retry-After has passed
We have implemented our own SCIM (2.0) Service with a rate limiting feature.
The Azure AD user provisioning application does not recognize 429 responses from our services when requests are sent to rapidly and just logs failures. These failures will be retried 40 minutes later, but this is a very long delay making an intial sync take way longer than needed. (especialy when the retries run into the rate limit again and again)
I suggest to retry requests that received a 429 response soon after the Retry-After header value ( has passed) to optimize the duration of a sync cycle.
8
votes
Hans Kusters (Infoland)
shared this idea