Revspire Resources

Microsoft Entra ID SCIM Provisioning

The Microsoft Entra ID provisioning service synchronizes assigned users and groups to Revspire over SCIM 2.0.

Before You Start

  • Microsoft Entra administrator access with permission to configure enterprise application provisioning.
  • A tested Revspire enterprise application for SAML SSO.
  • An active Revspire Deal Room entitlement for the Revspire organization.
  • Revspire access to Setup > SSO with View SSO Settings, Edit SSO Providers, and Generate API Tokens permissions.
  • A default internal profile unless Entra sends an explicit profile mapping, plus an eligible default product when users should be created active.

Step 1: Copy Revspire SCIM Values

In Revspire > Setup > SSO, select the Azure / Microsoft Entra ID provider and click SCIM Config.

SCIM Base URL = <copy from Revspire>
SCIM Token = <generate and copy once>

Step 2: Open Provisioning in Entra

Path: Microsoft Entra admin center > Entra ID > Enterprise apps > All applications > Revspire > Provisioning

Choose + New configuration. If your tenant shows the legacy provisioning interface instead, set Provisioning Mode to Automatic and use its equivalent Admin Credentials fields.

Step 3: Configure Admin Credentials

Entra Field Label: Tenant URL
Value: <Revspire SCIM Base URL>

Entra Field Label: Secret Token
Value: <Revspire SCIM Token only>

Click Test Connection. After the test succeeds, click Create to create the provisioning job. In the legacy interface, use Save.

Step 4: Review User Attribute Mappings

Path: Provisioning > Attribute mapping > Users (legacy interface: Mappings > Provision Microsoft Entra ID Users)

userPrincipalName -> userName
objectId -> externalId
givenName -> name.givenName
surname -> name.familyName
mail -> emails[type eq "work"].value
Switch([IsSoftDeleted], , "False", "True", "True", "False") -> active

Revspire requires the primary email entry to be non-empty, or the first email entry when none is marked primary. If mail is not populated for every assigned user, map another governed Entra attribute that always contains the user’s correct email. Do not map passwords.

Use the Revspire default profile unless you have deliberately added the Revspire profile extension to the Entra target attribute list.

Step 5: Review Group Mappings

Path: Provisioning > Attribute mapping > Groups (legacy interface: Mappings > Provision Microsoft Entra ID Groups)

displayName -> displayName
objectId -> externalId
members -> members

Provision users before their groups. Revspire accepts group members only when they are active and owned by this same provider connection.

Step 6: Set Scope and Test

  1. Set Scope to Sync only assigned users and groups for a controlled rollout.
  2. Assign one test user to the enterprise application.
  3. Use Provision on demand and confirm the user is created with the expected profile and product.
  4. Test one small assigned group.
  5. Click Start provisioning only after both tests succeed.

Troubleshooting

  • 401: verify the exact Tenant URL, Bearer header, selected provider, and token status. Rotate only when the token is expired, revoked, or unavailable.
  • 409: resolve the reported uniqueness conflict or unavailable product seat.
  • 400: verify that the user mapping supplies a non-empty email and valid explicit profile when used.
  • 422: verify the default internal profile, default product, organization defaults, and product dependencies.
  • Provisioning job enters quarantine: review Entra provisioning logs and retry Provision on demand after fixing the first reported SCIM error.

See the SCIM Provisioning overview for supported operations and lifecycle rules.