SSO and User Groups · 6 min read
User provisioning (SCIM)
How SCIM lets your identity provider create, update, deactivate and remove Intric accounts, how to set it up in Microsoft Entra ID, and what it does not cover.
SCIM (System for Cross-domain Identity Management) is a standard for sending user accounts from one system to another. With SCIM turned on, your identity provider (IdP) decides who has an Intric account and whether it is active: a user you add is created in Intric before their first login, and a user you remove loses access without anyone having to do anything in Intric.
This page is for the person who administers your IdP. The walkthrough is for Microsoft Entra ID. If you use another IdP that supports SCIM 2.0, contact Intric support.
SCIM and SSO
Section titled “SCIM and SSO”SCIM and SSO are separate, and you need both.
- SSO handles how a user signs in.
- SCIM handles whether the user has an account, and in what state.
With SSO alone, an account is created and updated only when the user signs in. A user you remove from your IdP can no longer sign in, but their Intric account stays active until someone deactivates it by hand, and a new user doesn’t exist in Intric until their first login, so an admin can’t prepare anything for them in advance.
With SCIM alone, a user gets an account but can’t sign in. SCIM issues no password, so sign-in still goes through SSO.
Adding SCIM changes nothing in your existing SSO setup. Set up SSO first, see SSO and User Groups.
What is synced
Section titled “What is synced”| Change in your IdP | Effect in Intric |
|---|---|
| A user is assigned to the provisioning application | An account is created before the user’s first login, with the User role and in your default billing group. It shows as Invited in the user list until the user signs in for the first time. |
| A user is unassigned, or their account is disabled | The account is deactivated and shows as Inactive. The user can’t sign in, and their sessions and API keys are rejected. Nothing is deleted, and the change is reversible. |
| A user is re-enabled or assigned again | The account is restored with everything intact. |
| A user is deleted | The account is deactivated at once. When Entra ID permanently deletes the user, about 30 days later, the account is removed from Intric: it disappears from all lists and its email address can be used again. Content the user created and the audit history are kept. |
| A user’s name changes | The name is updated, unless the user has changed their own name in Intric. A name the user chose in Intric is kept. |
| A user’s email address changes | The email address is updated, once it is verified and provided no other Intric account uses it. |
A few rules decide the cases the table doesn’t cover:
- A user who already has an Intric account with the same email address keeps that account. No second account is created. The same goes for a user with a pending invitation: they join through the invitation.
- An account that an Intric admin deactivated by hand stays deactivated. Re-enabling the user in your IdP restores only accounts that your IdP deactivated.
- Every change SCIM makes is recorded in Intric’s audit log.
What SCIM does not do
Section titled “What SCIM does not do”- It is one-way. Changes go from your IdP to Intric, never back. Changing a role, deactivating a user or moving a user to another billing group in Intric changes nothing in your IdP.
- It does not sync groups. Group membership still updates each time a user signs in, as described in User groups.
- It does not assign roles. Provisioned users get the User role. An Intric admin changes roles in Intric.
- It is not instant. Entra ID sends changes in a cycle that runs every 40 minutes. Intric applies each change within seconds of receiving it. To cut a user off immediately, also deactivate them in Intric’s user administration.
What you need
Section titled “What you need”- SSO with Entra ID already working for your organization.
- The Application Administrator or Cloud Application Administrator role in Entra ID.
- Entra ID P1 or P2 if you assign groups rather than individual users.
- Two values from Intric, sent through a secure channel: a Tenant URL and a Secret Token. Ask Intric support to turn on provisioning for your organization, and we send both.
Entra ID’s own provisioning service does the work. It connects to Intric’s login service, login.intric.ai, with the Secret Token, and manages users in your organization only.
Set up provisioning in Entra ID
Section titled “Set up provisioning in Entra ID”Provisioning runs from its own enterprise application, separate from the app registration you use for login.
Create the provisioning application
- In the Entra admin center, go to Entra IDEnterprise apps and click New application.
- Click Create your own application.
- Give it a name your admins will recognize, for example
Intric provisioning, choose Integrate any other application you don’t find in the gallery (Non-gallery), and click Create.
Connect it to Intric
- In the new application, open Provisioning and set the provisioning mode to Automatic.
- Under Admin Credentials, paste the Tenant URL and the Secret Token you got from Intric.
- Click Test Connection. It must succeed before you continue. If it fails, check that both values were pasted whole, then contact Intric support.
- Save.
Set the attribute mappings
- Under Mappings, open Provision Microsoft Entra ID Users and keep only the mappings in the table below. Delete the others, such as department and job title: Intric’s login service doesn’t store them.
- Under Mappings, open Provision Microsoft Entra ID Groups and set Enabled to No.
- Under Settings, set Scope to Sync only assigned users and groups.
| Entra ID attribute | SCIM attribute |
|---|---|
userPrincipalName |
userName |
Switch([IsSoftDeleted], , "False", "True", "True", "False") |
active |
mail |
emails[type eq "work"].value |
givenName |
name.givenName |
surname |
name.familyName |
displayName |
displayName |
objectId |
externalId |
Test with one user, then start
- Under Users and groups, assign one test user.
- Open Provision on demand, select the test user and click Provision. The result lists each step and what the login service answered.
- Confirm with Intric support that the account appeared in Intric.
- Assign the same users and groups that are assigned to your login application.
- Click Start provisioning.
From here on, adding a user to an assigned group gives them an Intric account, and removing them takes it away.
Running Intric on your own servers
Section titled “Running Intric on your own servers”The steps in Entra ID are the same. Two things differ.
You create the credential yourself. Your installation runs its own login service, so instead of receiving a Tenant URL and Secret Token from Intric, you create a service user and its token in your own login service. Intric guides you through it. Your installation needs Intric backend 2.7.0 or later and Zitadel 4.13 or later.
Entra ID also has to reach your login service. Its provisioning service runs in Microsoft’s cloud, and your login service sits inside your network. Your network team has to allow that traffic. There are two ways:
- Publish only the
/scim/v2/path of your login host to Microsoft’s provisioning service. - Install Microsoft’s on-premises provisioning agent inside your network, which reaches the login service without anything being opened inward.
Which one fits is your decision. Tell Intric which you choose, and if neither fits, we work out a setup with you.
Upkeep
Section titled “Upkeep”- The Secret Token has an expiry date. When it lapses, provisioning stops without any error in Intric: the next Entra ID cycle fails and users are no longer created or deactivated. Ask Intric for a new token before the date, and paste it under Admin Credentials.
- Check the provisioning logs when a change doesn’t arrive. In the provisioning application, Provisioning logs shows every user Entra ID tried to send and the answer it got. If Entra ID reports success and Intric still shows the old state after a few minutes, contact Intric support with the user’s email address and the time.