Tutorial: Configure Insite LMS for automatic user provisioning

This tutorial describes the steps you need to do in both Insite LMS and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to Insite LMS using the Azure AD 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.

Capabilities Supported

  • Create users in Insite LMS
  • Remove users in Insite LMS when they do not require access anymore
  • Keep user attributes synchronized between Azure AD and Insite LMS


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

  • An Azure AD tenant
  • A user account in Azure AD with permission to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
  • A Insite LMS tenant.
  • A user account in Insite LMS with Admin permissions.

Step 1. Plan your provisioning deployment

  1. Learn about how the provisioning service works.
  2. Determine who will be in scope for provisioning.
  3. Determine what data to map between Azure AD and Insite LMS.

Step 2. Configure Insite LMS to support provisioning with Azure AD

  1. Navigate to https://portal.insitelms.net/<OrganizationName>.
  2. Download and install the Desktop Client.
  3. Log in with your Admin Account and Navigate to Users Module.
  4. Select the User scim@insitelms.net and press the button Generate Access Token. If you can't find the scim-User, contact the Support-Team
    1. Choose AzureAdScimProvisioning and press generate
    2. Copy the AccessToken
  5. The Tenant Url is https://web.insitelms.net/<OrganizationName>/api/scim.

Add Insite LMS from the Azure AD application gallery to start managing provisioning to Insite LMS. If you have previously setup Insite LMS for SSO, you can use the same application. However it's recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 4. Define who will be in scope for provisioning

The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described here.

  • Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an attribute based scoping filter.

  • If you need additional roles, you can update the application manifest to add new roles.

Step 5. Configure automatic user provisioning to Insite LMS

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

To configure automatic user provisioning for Insite LMS 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 Insite LMS.

    The Insite LMS link in the Applications list

  3. Select the Provisioning tab.

    Provisioning tab

  4. Set the Provisioning Mode to Automatic.

    Provisioning tab automatic

  5. In the Admin Credentials section, enter your Insite LMS Tenant URL and Secret token information. Select Test Connection to ensure that Azure AD can connect to Insite LMS. If the connection fails, ensure that your Insite LMS account has admin permissions and try again.


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

    Notification Email

  7. Select Save.

  8. In the Mappings section, select Synchronize Azure Active Directory Users to Insite LMS.

  9. Review the user attributes that are synchronized from Azure AD to Insite LMS in the Attribute Mapping section. The attributes selected as Matching properties are used to match the user accounts in Insite LMS for update operations. If you change the matching target attribute, you'll need to ensure that the Insite LMS API supports filtering users based on that attribute. Select Save to commit any changes.

    Attribute Type Supported for filtering
    userName String
    emails[type eq "work"].value String
    active Boolean
    name.givenName String
    name.familyName String
    phoneNumbers[type eq "work"].value String
  10. To configure scoping filters, see the instructions provided in the Scoping filter tutorial.

  11. To enable the Azure AD provisioning service for Insite LMS, change Provisioning Status to On in the Settings section.

    Provisioning Status Toggled On

  12. Define the users or groups that you want to provision to Insite LMS by selecting the desired values in Scope in the Settings section.

    Provisioning Scope

  13. When you're ready to provision, select Save.

    Saving Provisioning Configuration

This operation starts the initial synchronization cycle of all users and groups defined in Scope in the Settings section. The initial cycle takes longer to do than next cycles, which occur about every 40 minutes as long as the Azure AD provisioning service is running.

Step 6. Monitor your deployment

After you've configured provisioning, use the following resources to monitor your deployment:

  • Use the provisioning logs to determine which users were provisioned successfully or unsuccessfully.
  • Check the progress bar to see the status of the provisioning cycle and how close it's to completion.
  • If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. To learn more about quarantine states, see Application provisioning status of quarantine.

More resources

Next steps