We are syncing the User ID attribute to Azure, we want to use the same attribute to correlate the accounts back into IDN. We are seeing that the correlation is not working as expected. Is it because we can’t use sync attributes as the correlation attribute or is it something else. Any thoughts would be highly appreciated.
Thanks
We use unique attributes for correlation like SamAccountName, Email or UserID or Username…etc
These attributes doesn’t change that often, so we never had experience this kind of situation. However there is nothing that you should not sync attributes that are used in Correlation. Both are independent rite.
If there is a change in correlation, you need to run un-optimized aggregation to see the changes.
Thanks
Krish
Yeah, that was my thinking as well but we recently updated the correlation logic in Azure AD and ran the unoptimised aggregation, the correlation doesnt seem to work, the correlated accounts are not even able to bring in the user id attribute (but they are still correlated for some reason). Might be because we have changed the logic and somehow it is still correlating with the previous config.
One more strange thing i have noticed is that when i disable the sync on user id attribute, i can see it in the correlated account but the correlation itself didnt run as exoected. Not sure if this is a glitch or something specific to us.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.