Skip to main content
Question

Entra ID (formerly Azure AD) - User Provisioning (SCIM) - Generic Create Errors

  • March 21, 2025
  • 1 reply
  • 39 views
A
Apprentice
Forum|alt.badge.img

All,

 

Hoping I can get some guidance on this issue - I’ve recently implemented the “Azure Active Directory Provisioning (SCIM)” app in our Freshservice tenant w/ setup in Entra ID. For some time, this was working properly, however, it appears that most but not all “Create” actions fail the majority of the time..

 

I have attempted the following in attempt to correct the issue:

  • Uninstalled and reinstalled app in Freshservice, entered new SCIM token in the Freshservice Enterprise App in Entra ID.
  • Stopped, restarted provisioning in the Enterprise App.
  • Manually provisioned select users.
  • Reviewed Freshservice API request limit to which our tenant is nowhere near maxing out.

I would like to note that I previously added custom attributes that were functioning and are reporting in Freshservice, but no other config has been tampered with.

 

Every once in awhile, 1 or more requestors will create successfully, though most result in this useless and generic error code:

 

Did this topic help you find an answer to your question?

1 reply

Ayeshaarian
Community Debut
  • Ayeshaarian
  • Community Debut
  • 2 replies
  • March 29, 2025

  1. Check SCIM Logs in Azure AD: Review the Provisioning Logs for errors, especially related to data formatting or API issues.

  2. Review Attribute Mappings: Ensure that both custom attributes and standard ones are correctly mapped between Azure AD and Freshservice.

  3. Check API Token Permissions: Ensure the SCIM API token in Freshservice has the correct permissions and is properly applied.

  4. Provisioning Profile Settings: Make sure the profile is active, and check for delays if provisioning many users.

  5. Verify SCIM Endpoint Availability: Ensure the Freshservice SCIM endpoint is working and not affected by rate limiting or network issues.

  6. Test with Simple Users: Test provisioning with minimal attributes or simpler user profiles to isolate the issue.

  7. Reach Out to Freshservice Support: If the issue persists, contact Freshservice support for more specific help or logs.

This should help narrow down the issue further. Let me know if you'd like more details on any step!

 

 

Reply


Most helpful members this week

Terms of UsePrivacy Notice