Synchronization approach followed in Azure AD SCIM provisioning

Ruchi 386 Reputation points

During the SCIM based provisioning for User/Group data from Azure AD, is there any standard followed to make api calls in parallel/sequential. Would /get requests come as parallel api calls and /post or /patch would be the sequential api calls. Also please suggest if /patch api calls to update /groups member list would happen in parallel?

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,859 questions
0 comments No comments
{count} votes

Accepted answer
  1. Danny Zollner 9,531 Reputation points Microsoft Employee

    AAD Provisioning will send more than one request in a short period of time. There is a limit to how many open connections will be made, with any new requests waiting until responses have been received for previous ones. The exact number is not published and may change over time. GET calls will always precede other actions (POST/PATCH/DELETE), but it is possible for one GET to then lead to multiple other actions - i.e.: multiple PATCH requests on the same user/group. Users would generally only be two requests (one for most attributes, a second for the manager attribute separately on some occasions), groups can have hundreds of requests after an initial GET.

    0 comments No comments

0 additional answers

Sort by: Most helpful