How does the Azure AD user provisioning map reference fields?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2024 01:45 AM
Hi. We have been trying to troubleshoot some recent issues where Managers and Locations (both reference fields) on user records are not getting updated via AAD user provisioning - this has worked until very recently.
When checking the mappings, we found the 'manager' field was being mapped to the AAD GUID attribute. We store a user's GUID on their user record in a custom field called 'u_objectid'. Does this mean the user provisioning engine is able to find a record via a reference to any unique value on that record? I.e., if we changed the mapping for 'manager' to the UserPrincipleName attibute for example, it would also find the correct reference record?
The AAD documentation isn't explicit on this point, only stating "When you're provisioning certain attributes (such as Department and Location) in ServiceNow, the values must already exist in a reference table in ServiceNow. If they don't, you'll get an InvalidLookupReference error.". https://learn.microsoft.com/en-us/entra/identity/saas-apps/servicenow-provisioning-tutorial