Rediger

Configure Leapsome for automatic user provisioning with Microsoft Entra ID

The objective of this article is to demonstrate the steps to be performed in Leapsome and Microsoft Entra ID to configure Microsoft Entra ID to automatically provision and de-provision users and/or groups to Leapsome.

Note

This article describes a connector built on top of the Microsoft Entra user Provisioning Service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Microsoft Entra ID.

This connector is currently in Preview. For more information about previews, see Universal License Terms For Online Services.

Prerequisites

The scenario outlined in this article assumes that you already have the following prerequisites:

Assigning users to Leapsome

Microsoft Entra ID uses a concept called assignments to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users and/or groups that have been assigned to an application in Microsoft Entra ID are synchronized.

Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Microsoft Entra ID need access to Leapsome. Once decided, you can assign these users and/or groups to Leapsome by following the instructions here:

Important tips for assigning users to Leapsome

  • It's recommended that a single Microsoft Entra user is assigned to Leapsome to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.

  • When assigning a user to Leapsome, you must select any valid application-specific role (if available) in the assignment dialog. Users with the Default Access role are excluded from provisioning.

Set up Leapsome for provisioning

  1. Sign in to your Leapsome Admin Console. Navigate to Settings > Admin Settings.

    Screenshot of Leapsome Admin Console.

  2. Navigate to Integrations > SCIM User provisioning.

    Screenshot of Leapsome Add SCIM.

  3. Copy the SCIM Authentication Token. This value is entered in the Secret Token field in the Provisioning tab of your Leapsome application.

    Screenshot of Leapsome Create Token.

Before configuring Leapsome for automatic user provisioning with Microsoft Entra ID, you need to add Leapsome from the Microsoft Entra application gallery to your list of managed SaaS applications.

To add Leapsome from the Microsoft Entra application gallery, perform the following steps:

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
  2. Browse to Entra ID > Enterprise apps > New application.
  3. In the Add from the gallery section, type Leapsome, select Leapsome in the search box.
  4. Select Leapsome from results panel and then add the app. Wait a few seconds while the app is added to your tenant. Screenshot of Leapsome in the results list.

Configuring automatic user provisioning to Leapsome

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users and/or groups in Leapsome based on user and/or group assignments in Microsoft Entra ID.

Tip

You may also choose to enable SAML-based single sign-on for Leapsome, following the instructions provided in the Leapsome Single sign-on article. Single sign-on can be configured independently of automatic user provisioning, though these two features complement each other

To configure automatic user provisioning for Leapsome in Microsoft Entra ID:

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

  2. Browse to Entra ID > Enterprise apps

    Screenshot of Enterprise applications blade.

  3. In the applications list, select Leapsome.

    Screenshot of the Leapsome link in the Applications list.

  4. Select the Provisioning tab.

    Screenshot of the Manage options with the Provisioning option called out.

  5. Select + New configuration.

    Screenshot of Provisioning tab automatic.

  6. In the Tenant URL field, enter your Leapsome Tenant URL and Secret Token. Select Test Connection to ensure Microsoft Entra ID can connect to Leapsome. If the connection fails, ensure your Leapsome account has the required admin permissions and try again.

    Note

    Enter https://www.leapsome.com/api/scim in Tenant URL.

    Screenshot of Provisioning test connection.

  7. Select Create to create your configuration.

  8. Select Properties on the Overview page.

  9. In the Notification Email field, enter the email address of a person who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box.

    Screenshot of Provisioning properties.

  10. Select Attribute Mapping in the left panel and select users.

  11. Review the user attributes that are synchronized from Microsoft Entra ID to Leapsome in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Leapsome for update operations. If you choose to change the matching target attribute, you need to ensure that the Leapsome API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Screenshot of Leapsome User Attributes.

  12. Review the group attributes that are synchronized from Microsoft Entra ID to Leapsome in the Attribute Mapping section. The attributes selected as Matching properties are used to match the groups in Leapsome for update operations. Select the Save button to commit any changes.

    Screenshot of Leapsome Group Attributes.

  13. To configure scoping filters, refer to the instructions provided in the Scoping filter article.

  14. Use on-demand provisioning to validate sync with a small number of users before deploying more broadly in your organization.

  15. When you're ready to provision, select Start Provisioning from the Overview page.

Connector Limitations

  • Leapsome requires userName to be unique.
  • Leapsome only allows work email addresses to be saved.

Additional resources