"InvalidLookupReference" error in Azure AD provisioning.

Sriraj V
Tera Contributor

Hi Team,

How we can handle this type of error in servicenow when we do azure ad provisioning. Any idea?

As per the tip, missing location "LA" data must be added in servicenow. Apart from this, is there any way to treat this error. Azure AD provisioning will hit the sys_user table directly, how can we create that missing 'LA' data in location table so that it can reflect in user table during the provisioning.

find_real_file.png

Regards,

Sriraj

1 REPLY 1

Mike W_
Tera Contributor

I know this is old, but I'm just hitting this same problem too.  I haven't yet found a solution.  A non-optimal solution might be to setup AzureAD provisioning without the reference attributes mapped, then have a second data source pull the data out of AzureAD and just set the reference attributes the way you want, via a transform map.