Re: ServiceNow Azure AD integration with SCIM for ...

AndersBGS · ‎09-09-2026

Just for information... We tried the same, but made a SOAP integration instead as recommend here: https://learn.microsoft.com/en-us/entra/identity/saas-apps/servicenow-provisioning-tutorial We unfortunatly hade to many errors with the SCIM solution.

manish62 · ‎09-10-2026

Thank you for your response

We selected the SCIM option because, when we tried using the out-of-the-box ServiceNow application, a message was displayed indicating that SCIM provisioning is required for this integration. Based on that recommendation, we proceeded with the SCIM-based configuration. we had no option to go with SOAP base integration.

Thanks

Manish Gupta

masonreed11 · ‎09-10-2026

This looks more like a user-matching or attribute-mapping issue than an Azure permission problem. Check that the SCIM account has the required ServiceNow roles and that Azure’s userName/email mapping exactly matches the ServiceNow user record. Also verify the SCIM endpoint and authentication token, then test with a user whose UPN matches an existing ServiceNow user.

manish62 · ‎09-10-2026

Thanks @masonreed11 for response.

We have created a dedicated integration account for this integration; however, we are unable to understand where this account is mapped or associated within the configuration. As part of the Azure AD integration, the connection is established using the tenant SCIM endpoint:

https://<instance_name>.service-now.com/api/now/v2/scim

along with the secret token that was generated through the OAuth Registry configuration as part of the SCIM plugin setup. We have also verified that the necessary attribute mappings are configured in the SCIM configuration. Given that the authentication appears to rely on the tenant URL and bearer token, we are trying to understand where and how the integration account is actually linked or utilized during the provisioning process.

Anoop8 · ‎09-14-2026

You can get more logs from syslog.list. Message contains SCIM. Try populating more fields in Entra such as email.
SCIM requires custom schema and corresponding ETL definition to make it work. Enterprise schema attributes are not supported (disregarded) by service-now.