Skip to main content

Troubleshooting

Common issues you may encounter when provisioning users from Azure Entra ID to nullplatform, with causes and solutions.

Provisioning fails with "Invalid credentials"​

Cause: The API secret token is incorrect or expired.

Solution:

  1. Verify the token in your configuration is correct.
  2. Generate a new token if needed.
  3. Update the Secret Token in Azure Entra ID provisioning settings.
  4. Retry the provisioning operation.

Users are not syncing​

Cause: Users may not be assigned to the application in Azure Entra ID.

Solution:

  1. In the application, go to Users and groups.
  2. Click Add user/group.
  3. Assign users or groups to the application.
  4. Wait for the next provisioning cycle (typically every 40 minutes) or manually trigger a sync.

"User not found" errors​

Cause: The SCIM API cannot locate a user to update.

Solution:

  1. Check the userName mapping is correct (usually matches email or UPN).
  2. Verify user was successfully created on initial provisioning.
  3. Check provisioning logs for validation errors.

Attribute mappings not working​

Cause: Attribute values may be missing or incorrectly mapped.

Solution:

  1. Verify the Azure Entra ID user has values for mapped attributes.
  2. Check the SCIM schema supports the attribute.
  3. Review the provisioning logs for specific mapping errors.
  4. Test with a sample user first.

Next steps​