Skip to content
⌘K
InboxAsk a human

SCIM with Azure

Updated by Vaishnavi

Enterpret SCIM Integration with Azure Entra ID

Set up automatic user provisioning from Azure Entra ID to Enterpret

Enterpret provides one SCIM endpoint for supported provisioning requests. Review the common requirements and role limits in the SSO and SCIM overview, then configure and test Microsoft Entra ID as described below.

Supported SCIM role groups

Enterpret exposes four fixed SCIM groups. Link your identity-provider groups to these existing groups:

Group nameSCIM group ID
Enterpret Adminsenterpret-admins
Enterpret Editorsenterpret-editors
Enterpret Membersenterpret-members
Enterpret Viewersenterpret-viewers

Link to the existing fixed groups; creating, renaming, replacing or deleting SCIM groups is unsupported. Keep each user in one Enterpret role group. Membership removal alone does not reset a user’s role or suspend access. SCIM cannot grant or change Owner roles; manage those in Enterpret through an Owner. An active=false user update suspends access without deleting the user.

Prerequisites

  • SCIM OAuth bearer token: In Enterpret, open Settings → SSO and SCIM → SCIM provisioning, choose Generate token, then copy it. Use Copy token for an existing token. Ask your Enterpret team if the controls are unavailable. Regenerating invalidates the old token.

  • Admin rights in Azure Entra ID: Application or Cloud Application Administrator permissions are required.

  • User matching: Map the Entra field that contains the intended Enterpret email address to userName, and use userName as the matching attribute. Verify the value for guests and aliases as well as regular users.

  • Role mapping: Decide whether you will manage roles manually or configure tested membership updates to Enterpret’s existing fixed SCIM groups. Naming an Entra group “Enterpret Admins” alone does not assign the Enterpret role.


Instructions: Azure Entra ID Setup for Enterpret SCIM

1. Create the Enterprise Application

  • Go to Microsoft Entra admin center → Enterprise applications → New application.

  • Select “Create your own application,” name it (e.g., “Enterpret SCIM”), and choose non-gallery.

2. Connect Provisioning to Enterpret SCIM

  • In the newly created app, navigate to Provisioning.

  • Create the automatic provisioning configuration. Depending on your Entra admin-center version, choose New configuration or set Provisioning Mode to Automatic. Use the bearer-token/Secret Token authentication option for the Enterpret token.

  • Enter Tenant URL: https://api.enterpret.com/scim/scim/v2

  • Paste your Enterpret SCIM OAuth Bearer Token into Secret Token.

  • Click “Test Connection.” Save if successful.

3. Configure Attribute Mappings

  • In Provisioning > Mappings, edit “Provision Azure Active Directory Users.”

  • Map supported user fields and use userName for matching. Creation requires an email-valued userName, Boolean active, name.givenName and name.familyName. Enterpret does not apply arbitrary profile attributes or change an existing user’s userName through this SCIM flow. The mappings below describe these fields:

    • userName ← the directory field containing the user’s Enterpret email address; enable matching on userName.

    • active ← the Boolean lifecycle mapping appropriate for your Entra configuration, including disabled or out-of-scope users. Review Entra’s accountEnabled/IsSoftDeleted behavior and test deactivation.

    • name.givenName ← givenName

    • name.familyName ← surname

    • emails[type eq "work"].value can describe the work email, but Enterpret uses userName for matching and account creation. Do not configure this email subfield as an additional matching key.

  • Save changes.

4. Set Provisioning Scope

  • Provisioning > Settings > Scope: Select “Sync only assigned users and groups” for control.

  • Save.

5. Assign Users or Groups

  • In Users and groups for the application, add users or groups.

  • For SCIM role updates, configure the group matching and membership mappings to target Enterpret’s existing groups by their fixed identities. Do not enable arbitrary group creation or deletion. Test a membership update and verify the role in Enterpret. If your Entra configuration cannot link the existing groups, leave group-object provisioning disabled and manage roles in Enterpret; assigning users through an Entra group is a separate provisioning-scope choice.

6. Start Provisioning

  • Return to Provisioning and click “Start provisioning.”

  • Monitor Entra’s provisioning logs and test creating or matching a user, changing the user’s active status, and any configured role membership update. Confirm the resulting access and role in Enterpret before expanding scope. SCIM user deletion is unsupported; deprovision by sending active=false.