SCIM Integration between Servicenow and Azure AD as unregistered gallery app

Question

SCIM Integration between Servicenow and Azure AD as unregistered gallery app

Naman Khandelwal 0

Message: Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details. Web Response: {"schemas":["urn:ietf:params:scim:api:messages:2.0:Error"],"status":"400","scimType":"invalidPath","detail":"Patch op[0]: Attribute departmentName in path departmentName is undefined"}

Receiving this error while mapping department field from Azure to ServiceNow
I am using [ urn:ietf:params:scim:schemas:extension:servicenow:custom:2.0:User.departmentName ] as the target attribute

Have configured the ETL definitions and the custom schema extension within ServiceNow for the departmentName. This is working completely fine and Department is getting populated within ServiceNow using it's REST API Explorer.

On provisioning from Azure to ServiceNow - core fields like username/first name/last name/email are getting mapped within ServiceNow. Have found the workaround for "manager" but unable to map "department" field.

How can the schema edited to add the namespace within the request payload from Azure? Or any workaround for mappings that work.

Carolyne 1,151 Reputation points Microsoft Employee

2026-02-03T12:20:29.3+00:00

It seems the invalidPath error occurs because the SCIM payload sent by Microsoft Entra ID does not include the ServiceNow custom schema namespace in the schemas array, so ServiceNow treats departmentName as undefined even though the field and ETL mapping exist. This is as picked from the documentation on ServiceNow here- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2668604

Have you tried to map Department to a standard ServiceNow field (for example department or u_department) via the Entra attribute list, or populate the custom field post‑provisioning using ServiceNow business rules or scheduled jobs - https://learn.microsoft.com/en-us/entra/identity/saas-apps/servicenow-provisioning-tutorial

Your answer

Carolyne 1,151 Reputation points Microsoft Employee

2026-02-03T12:20:29.3+00:00

It seems the invalidPath error occurs because the SCIM payload sent by Microsoft Entra ID does not include the ServiceNow custom schema namespace in the schemas array, so ServiceNow treats departmentName as undefined even though the field and ETL mapping exist. This is as picked from the documentation on ServiceNow here- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2668604

Have you tried to map Department to a standard ServiceNow field (for example department or u_department) via the Entra attribute list, or populate the custom field post‑provisioning using ServiceNow business rules or scheduled jobs - https://learn.microsoft.com/en-us/entra/identity/saas-apps/servicenow-provisioning-tutorial