Creating and Mapping a SCIM Schema Extension in ServiceNow (SCIM API)Issue When provisioning users via SCIM, certain attributes (such as a department name) are not part of the default SCIM core schema. As a result, these attributes are not mapped in the ServiceNow ETL process, causing them to be ignored or dropped during user creation or update. Release All Resolution Create the SCIM Schema Extension Use the following sample JSON as a reference: { "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:Schema" ], "id": "urn:ietf:params:scim:schemas:extension:servicenow:custom:2.0:User", "name": "CustomUser", "description": "Custom schema for User", "attributes": [ { "name": "departmentName", "type": "string", "multiValued": false, "description": "Department Name", "required": false, "caseExact": false, "mutability": "readWrite", "returned": "default", "uniqueness": "none" } ]} Update the "name" in the attributes section to your required custom attribute. Update ETL Definitions - Navigate to ETL Definitions. - Open the SCIM User ETL definition. Update the scim-user ETL Entity - Open the scim-user ETL entity. - Locate the mapping for the Department field. - Update the Path to: custom.departmentName - Set the Coercion Action based on requirements (e.g., create new record if not found). Update the user ETL Entity - Open the user ETL entity. - Locate the Department field mapping. - Update the Path to: department.name - This ensures that the value from the SCIM payload is correctly mapped to the Department Name field in the User table. Validate the Configuration - Send a SCIM provisioning request with the new custom attribute from the identity provider. - Verify that the value is received, mapped, and updated in the User record. Note: This is only an example and should be adapted to match your environment and schema requirements. Always test in a non-production instance before making changes in production.