Skip to main content

Troubleshooting SCIM Provisioning

If users are not being provisioned correctly — or authentication is failing after the Entra ID integration has been configured — work through the…

If users are not being provisioned correctly — or authentication is failing after the Entra ID integration has been configured — work through the checks below in sequence.


Tenant not registered

The organisation's Entra ID Tenant ID must be provided to the platform support team before configuration begins. If this step was skipped, the integration will not function regardless of how the enterprise application is configured. Contact support to confirm the tenant has been registered.


Enterprise application is missing

The Foundation Cloud for Energy enterprise application must exist in your Entra ID tenant. Open Enterprise Applications in the Entra ID administration portal and confirm the application is listed. If it is not present, follow the steps in Setting Up Entra ID Integration to create it.


Tenant Administrator role not assigned

At least one user must have the Tenant Administrator role assigned within the enterprise application. Without this role, no one can access the tenant administration portal or generate provisioning tokens. Open Users and Groups on the enterprise application and confirm the role assignment.


SCIM token is missing, incorrect, or expired

A SCIM token must be generated in the platform's tenant administration portal and entered correctly in the Entra ID provisioning configuration. Check the following:

  • The correct token value was copied and entered.

  • The provisioning URL was entered without modification.

  • The token has not expired — tokens are valid for twelve months.

If the token has expired, generate a new one in the tenant administration portal and update the provisioning configuration in Entra ID.


Provisioning is not enabled

SCIM provisioning must be switched on in the Entra ID enterprise application. Open the Provisioning section and confirm that Provisioning Status is set to On.


Attribute mapping is incorrect

The userName attribute must be mapped to originalUserPrincipalName. If this mapping is missing or incorrect, users may fail to provision or may be created with incorrect identifiers. Review the attribute mappings in the Provisioning configuration and correct them if needed.


Connection test is failing

Use Test Connection in the provisioning configuration to verify that Entra ID can reach the platform. If the test fails, recheck the provisioning URL and token, confirm that provisioning is enabled, and verify the attribute mappings.


Users are provisioned but cannot access the platform

Provisioning creates the user account but does not assign application roles. A user with no roles assigned will authenticate successfully but will see no applications. Assign the appropriate roles within the platform. See Configuring User Roles.


Provisioning is slow or a user needs immediate access

Scheduled provisioning cycles run at intervals and may not apply changes immediately. Use on-demand provisioning to synchronise a specific user without waiting. See Configuring SCIM Provisioning.


Provisioning is failing

Check user provisioning logs for details of any errors. All users must have a first name, last name and email address assigned for our SCIM provisioning to succeed.

Did this answer your question?