Tutorial: Configure Leapsome for automatic user provisioning

The objective of this tutorial is to demonstrate the steps to be performed in Leapsome and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to Leapsome.

Note

This tutorial describes a connector built on top of the Azure AD 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 Azure Active Directory.

This connector is currently in Preview. For more information on the general Microsoft Azure terms of use for Preview features, see Supplemental Terms of Use for Microsoft Azure Previews.

Prerequisites

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

  • An Azure AD tenant.
  • A Leapsome tenant.
  • A user account in Leapsome with Admin permissions.

Assigning users to Leapsome

Azure Active Directory 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 Azure AD are synchronized.

Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Azure AD 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 Azure AD 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.

Setup 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 in the Azure portal.

    Leapsome Create Token

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

To add Leapsome from the Azure AD application gallery, perform the following steps:

  1. In the Azure portal, in the left navigation panel, select Azure Active Directory.

    The Azure Active Directory button

  2. Go to Enterprise applications, and then select All applications.

    The Enterprise applications blade

  3. To add a new application, select the New application button at the top of the pane.

    The New application button

  4. In the search box, enter Leapsome, select Leapsome in the results panel, and then click the Add button to add the application.

    Leapsome in the results list

Configuring automatic user provisioning to Leapsome

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

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 compliment each other

To configure automatic user provisioning for Leapsome in Azure AD:

  1. Sign in to the Azure portal. Select Enterprise Applications, then select All applications.

    Enterprise applications blade

  2. In the applications list, select Leapsome.

    The Leapsome link in the Applications list

  3. Select the Provisioning tab.

    Provisioning tab

  4. Set the Provisioning Mode to Automatic.

    Provisioning tab

  5. 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 Azure AD can connect to Leapsome. If the connection fails, ensure your Leapsome account has Admin permissions and try again.

    Tenant URL + Token

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

  7. Click Save.

  8. Under the Mappings section, select Synchronize Azure Active Directory Users to Leapsome.

    Leapsome User Mappings

  9. Review the user attributes that are synchronized from Azure AD 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

  10. Under the Mappings section, select Synchronize Azure Active Directory Groups to Leapsome.

    Leapsome Group Mappings

  11. Review the group attributes that are synchronized from Azure AD 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

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

  13. To enable the Azure AD provisioning service for Leapsome, change the Provisioning Status to On in the Settings section.

    Provisioning Status Toggled On

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

  15. 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 Azure AD 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 Azure AD provisioning service on Leapsome.

For more information on how to read the Azure AD 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