Hi Connections,
Problem Statement:
XYZ Azure AD sync user accounts to ServiceNow using Azure AD Store application through Inbound. The sync is not correctly working for one of the group, and get skipped while updating group members. Members being added to the group on Azure AD is failing to get added to target system ServiceNow through the provisioning channel But it is working for the same group sometimes and for other groups without any issues. Sync is happening from Azure to ServiceNow every 40 min.
The Azure AD provisioning just mentions that the record is skipped as this is a ‘REDUNDANT EXPORT’.
Upon targeted reprovisioning of a user they are getting added to the Group on ServiceNow
we had a P2 issue where users are in AD group but not associated with ServiceNow.
This is a known issue for provisioning in Microsoft Entra ID, there is no proper solution, we need to just restart the sync, should not effect. Yesterday we initiated the sync for the SN Acceptance instance to see if it works today, I review SN Acceptance instance the users are synced without any issue.
Member of group not provisioned :
When a group is in scope and a member is out of scope, the group will be provisioned. The out-of-scope user won't be provisioned. If the member comes back into scope, the service won't immediately detect the change. Restarting provisioning addresses the issue. Periodically restart the service to ensure that all users are properly provisioned.
My analysis (Sync is working fine, but for some users provisioning is not happening. The reason "Skipped" in the provisioning logs indicates that the user was already provisioned successfully before and that's the reason it gets skipped when tried to provision again)
Need to find out the root cause for this issue, I hope someone had faced this issue, I really appreciate any help to find out the RCA
Best Regards,
Rafmine
