SCIM Provisioning for Microsoft Entra ID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2026 09:49 PM
When attempting to configure provisioning in the Azure portal, I can only see the "Bearer Authorization" and "OAuth 2.0 client credentials grant" options in the Authentication Method dropdown.
Could you please confirm whether Basic Authentication is still supported? If so, how can I enable or switch to this authentication method?
Additionally, I followed the referenced documentation to generate a Bearer token and used it while configuring provisioning in Azure AD. However, I encountered the following error:
Error Code: CredentialValidationUnavailable
Could you please provide guidance on how to resolve this issue? Are there any specific property settings or configurations that need to be checked?
Additionally,
Could you also provide detailed steps for configuring authentication in ServiceNow, including:
- How to set up API authentication (OAuth if applicable)
- Required configurations on the ServiceNow side
- The correct Redirect URL to be used during integrationI have also attached the error message and authentication configuration details for your reference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Basic Authentication for a Custom Provisioning Application in Entra is not supported. If you want to use Basic Auth, you have to use the ServiceNow gallery application (which does not use SCIM, but rather uses SOAP).
You really shouldn't use the Bearer token option either, because it requires that you generate a long-lasting bearer token and then enter it and keep track of it in Azure.
Use Client Credentials grant instead, and create an app registration that does just that in ServiceNow.
Unfortunately, you'll run into more issues after this, because Microsoft does not conform to the RFC standard for SCIM, and is also using the Enterprise version for users, whereas ServiceNow only supports Core.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
Hello Team,
I am doing the integration with Azure AD with SCIM plugin for user provisioning and completed the steps till connection, Azure AD is successfully connected with ServiceNow but when we try to create one user the getting error any sort of permission do we need to use in Azure side .
I have created one integration account but not sure where to use this account as for generating the auth token using the client id and secret.
Tenant Url - https://instancename.service-now.com/api/now/scim
I am getting error when creating a single user from Azure to Servicenow-
Error-User 'abce@abc.com' will be created in customappsso (User is active and assigned in Microsoft Entra ID, but no matching User was found in customappsso)
Failed to create User 'abce@abc.com' in customappsso
Error code
Error message
UpdateForUnconnectedEntry
Please let me know any insight on this issue how could i resolve it.
Thanks,
Manish
