Rediger

Del via

Tutorial: Configure Leapsome for automatic user provisioning

  • Artikkel

The objective of this tutorial 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 tutorial 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 tutorial assumes that you already have the following prerequisites:

  • A Microsoft Entra tenant.
  • A Leapsome tenant.
  • A user account in Leapsome with Admin permissions.

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 is 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.

    Leapsome Admin Console

  2. Navigate to Integrations > SCIM User provisioning.

    Leapsome Add SCIM

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

    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 Identity > Applications > Enterprise applications > 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. 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 tutorial. 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 Identity > Applications > Enterprise applications

    Enterprise applications blade

  3. In the applications list, select Leapsome.

    The Leapsome link in the Applications list

  4. Select the Provisioning tab.

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

  5. Set the Provisioning Mode to Automatic.

    Screenshot of the Provisioning Mode dropdown list with the Automatic option called out.

  6. Under the Admin Credentials section, input https://www.leapsome.com/api/scim in Tenant URL. Input the SCIM Authentication Token value retrieved earlier in Secret Token. Click Test Connection to ensure Microsoft Entra ID can connect to Leapsome. If the connection fails, ensure your Leapsome account has Admin permissions and try again.

    Tenant URL + Token

  7. In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and check the checkbox - Send an email notification when a failure occurs.

    Notification Email

  8. Click Save.

  9. Under the Mappings section, select Synchronize Microsoft Entra users to Leapsome.

  10. 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. Select the Save button to commit any changes.

    Leapsome User Attributes

  11. Under the Mappings section, select Synchronize Microsoft Entra groups to Leapsome.

  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.

    Leapsome Group Attributes

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

  14. To enable the Microsoft Entra provisioning service for Leapsome, change the Provisioning Status to On in the Settings section.

    Provisioning Status Toggled On

  15. Define the users and/or groups that you would like to provision to Leapsome by choosing the desired values in Scope in the Settings section.

    Provisioning Scope

  16. When you are ready to provision, click Save.

    Saving Provisioning Configuration

This operation starts the initial synchronization of all users and/or groups defined in Scope in the Settings section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the Microsoft Entra provisioning service is running. You can use the Synchronization Details section to monitor progress and follow links to provisioning activity report, which describes all actions performed by the Microsoft Entra provisioning service on Leapsome.

For more information on how to read the Microsoft Entra provisioning logs, see Reporting on automatic user account provisioning.

Connector Limitations

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

Additional resources

Next steps