Skip to content

SCIM provisioning

  • Plan: Enterprise. Organizations only.
  • Role: Super admin.
  1. Go to Devices & Access › Single sign-on › Provisioning (SCIM).
  2. Choose Create SCIM token, enter a name and Expires after (days) (at most 365).
  3. Copy the Tenant URL and the token from Copy your SCIM token. The token is shown once.
  1. Enterprise applications › New application › Create your own application (non-gallery).
  2. Provisioning › Automatic. Tenant URL is the SCIM base URL. Secret token is the SCIM token.
  3. Test connection.
  4. Under Mappings, keep userPrincipalName → userName, mail → emails[type eq "work"].value, objectId → externalId, and Switch([IsSoftDeleted]…) → active. Turn on group provisioning.
  5. Assign users and groups, then Start provisioning.
  1. Applications › Create App Integration, an OIDC or SAML app for sign-in. Under General, enable SCIM provisioning.
  2. Provisioning › Integration: SCIM connector base URL is the SCIM base URL. Unique identifier field is userName. Actions: Push New Users, Push Profile Updates, Push Groups. Authentication Mode is HTTP Header, with Bearer <SCIM token>.
  3. Provisioning › To App: enable Create, Update and Deactivate Users.
  4. Push the groups you map to roles.

Under Group-to-role mappings, use the SCIM group’s display name. SCIM can grant at most Admin. Grant Super admin under Users.

Only provisioned people refuses sign-in to anyone your IdP hasn’t provisioned.

  • People are linked at their first sign-in when their verified email matches.
  • Deactivating someone in the IdP signs them out at once and stops their API tokens.
  • SCIM never removes the last active Super admin.

Create a new token, paste it into the IdP, check that provisioning runs, then Revoke the old one.