Skip to content

Provision users from Microsoft Entra ID with SCIM ​

SCIM 2.0 lets Microsoft Entra ID create, update, suspend and remove people in your Tara organization, and set their role from Entra groups. It does not sign anyone in: people still sign in with Organization SSO (OIDC), so set that up first (see SAML providers through OIDC for the Entra OIDC steps).

SCIM is included in the Enterprise plan only. On Free and Team an owner cannot create a SCIM token, and a SCIM call from an organization that has lost the feature gets 403 with a message that names the plan (SCIM clients do not understand 402 Payment Required, so Tara uses 403 here).

You need to be an owner of the organization. Only owners can create SCIM tokens and map groups to roles.

In Tara ​

  1. Open Settings › SSO and find SCIM provisioning. Create a token and give it a name. Copy the token (starts with tara_scim_); it is shown once.
  2. Copy the base URL: https://<tara host>/scim/v2/orgs/<org slug>. <org slug> is your organization's slug.
  3. Optional but recommended: map Entra group names to roles (see Groups and roles).

From the terminal:

bash
ph org scim-token create entra --out scim-token.txt
ph org scim-roles set '{"Engineering":"member","Platform":"admin","Stakeholders":"viewer"}'

A token lasts 365 days by default (730 at most), belongs to this organization only, and can call only /scim/v2/orgs/<org slug>/…. An organization can have 10 active tokens, so you can create a second one before revoking the first when you rotate.

In Microsoft Entra ID ​

The labels below are the ones the Entra admin center usually shows; they can differ a little between versions.

  1. In the Microsoft Entra admin center, open Enterprise applications and create a new application of your own (a non-gallery application). You can reuse the enterprise application you made for SSO if you like; a separate one for provisioning also works.

  2. Open the application's Provisioning and set Provisioning Mode to Automatic.

  3. Under Admin Credentials, enter Tenant URL: the base URL from Tara. Enter Secret Token: the SCIM token.

  4. Choose Test Connection. Entra calls the Tara endpoint; success means the URL and token are right. Save.

  5. Open Mappings. For Provision Microsoft Entra ID Users, keep these attributes and remove the others:

    Entra ID attributeTara (SCIM) attribute
    userPrincipalNameuserName
    mailemails[type eq "work"].value
    Switch([IsSoftDeleted], , "False", "True", "True", "False")active
    displayNamedisplayName
    givenNamename.givenName
    surnamename.familyName
    objectIdexternalId

    The expression for active is the one Entra uses by default in its SCIM mappings; if your mapping already has an active row, keep it.

  6. For Provision Microsoft Entra ID Groups, keep the group mapping. Its displayName is the group name you map to a role.

  7. Under Settings, choose the Scope: Sync only assigned users and groups is the usual choice. Then assign people and groups to the application under Users and groups.

  8. Set Provisioning Status to On and save (the button may read Start provisioning).

The work email must be the person's email at your company: Tara links a person by it. If a person has no mail value, Tara uses userName as the email, so userPrincipalName must then be a real email address.

Tara reads only these user attributes: userName, externalId, name (given, family, formatted), displayName, the work emails and active. Anything else Entra sends is accepted and ignored. Entra sends active as the text "False" or "True" and writes operations as Replace, Add, Remove; Tara accepts both.

Entra runs a sync cycle about every 40 minutes, so changes are not instant. Use Provision on demand in Entra to test one person.

What happens ​

  • A person is assigned. Entra creates them in Tara. If someone with that email already has a Tara account with a verified email, they are linked at once and become members. Otherwise Tara holds a pending membership for the email.
  • First sign-in. When that person signs in with your organization's SSO and the email from Entra matches, Tara links their account and makes them a member with the role from their groups.
  • Entra disables or unassigns a person. Tara removes them from the organization and its projects, takes no seat, and does not let SSO sign-in or auto-join add them back. If they come back in scope, their membership is restored.
  • Entra deletes a person. Tara removes them from the organization. Their Tara account is not deleted.
  • Owners are never touched. SCIM never creates, changes or removes an owner.

Groups and roles ​

scimGroupRoles maps group names to admin, member or viewer (never owner). Names are not case-sensitive.

  • A person in several mapped groups gets the highest role.
  • If no mapping is set, every provisioned person is a member.
  • If a mapping is set but a person is in none of the mapped groups, they are a viewer (free, no seat).
  • People you added by hand or by invitation keep the role you gave them. SCIM changes the role of members who joined another way.
  • Change the mapping and Tara updates the roles of everyone already linked.
  • Entra must provision a user before it adds them to a group. Tara refuses a group member it has not seen.

Seats and limits ​

Admins and members use a seat; viewers do not. If your plan has no seat left, Entra gets 409 with Seat limit reached in the error detail, and shows it in the provisioning logs. People already provisioned keep their access. Give new people the viewer role through a group mapped to viewer, or upgrade (Billing and upgrading).

Check it worked ​

Open Audit log in Tara and look for:

ActionMeaning
scim.user.createEntra created a person
scim.user.linkLinked to a Tara account (verified_email or oidc_login)
scim.user.roleMembership added or role changed
scim.user.suspend, scim.user.reactivateEntra disabled or restored them
scim.user.deleteEntra deleted them
scim.group.create, scim.group.update, scim.group.deleteGroup changes
scim.group.rolesAn owner saved the group-to-role mapping
scim_token.create, scim_token.revokeAn owner created or revoked a token

Troubleshooting ​

You seeCause
401The secret token is wrong, expired or revoked.
403The token belongs to another organization (check the slug in the Tenant URL), or something other than a SCIM token was used.
404Wrong Tenant URL. It must end with the organization slug, with no /Users.
409 with uniquenessAnother person in the organization already has that userName, email or externalId.
409 with Seat limit reachedNo seat left for this role. See above.
400 with invalidValueA person has no usable work email, or a group member was not provisioned yet.
400 with invalidFilterTara does not support that filter. Tara supports eq on userName, externalId, id, active and the work email for users, and on displayName, externalId, id for groups.
scim_suspended at sign-inThe person is disabled in Entra.

Limits ​

  • No bulk, sort, ETag or password operations.
  • Only the eq filter operator.
  • Enterprise extension attributes are not stored.

Tara's own endpoint describes itself at /scim/v2/orgs/<org slug>/ServiceProviderConfig.

For Okta, see Provision users from Okta with SCIM.