Security and Governance Controls
Token Validity
Each SCIM token has a one-year lifetime. Generating a new token does not in itself revoke previous issued tokens. This is to ensure synchronization continuity. Only when a new token is added to the SCIM application in Entra ID and a successful test sync has been run will the previous token be rendered inactive. An active token can also be revoked directly in Prime, by users with the required permission.
Token Rotation
Rotate before the one-year expiry. When a token expires, provisioning stops, and after repeated failures Entra ID places the application in quarantine.
- In Prime, go to Settings → SCIM Integration and generate a new token. Copy it immediately, it cannot be retrieved later.
- In Entra ID, open the SCIM application → Provisioning → Admin Credentials.
- Paste the new token into Secret Token and click Save.
- Run a Provision on Demand against a test user.
- Once that sync succeeds, the previous token is rendered inactive automatically.
The previous token remains active until step 5 completes, so scheduled synchronisation is not interrupted and a failed rotation can be retried without loss of service.
Revocation Rights:
The Secomea Team has the capability to fully revoke the SCIM integration, in exceptional or security-related scenarios, or in connection with customer offboarding.
Audit and Traceability:
All token creation, revocation, and usage events are logged and auditable through Prime’s backend services.
References
Official SCIM 2.0 Documents as listed below:
https://datatracker.ietf.org/doc/html/rfc7643
https://datatracker.ietf.org/doc/html/rfc7644
https://datatracker.ietf.org/doc/html/rfc7642
SCIM as per MS Entra ID
https://learn.microsoft.com/en-us/entra/architecture/sync-scim