Edit

Share via


Configure StarLeaf for automatic user provisioning with Microsoft Entra ID

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

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:

Step 1: Assign users to StarLeaf

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 you configure and enable automatic user provisioning, you should decide which users and groups in Microsoft Entra ID need access to StarLeaf. Then you can assign the users and groups to StarLeaf by following these instructions.

Important tips for assigning users to StarLeaf

  • It's recommended that a single Microsoft Entra user is assigned to StarLeaf to test the automatic user provisioning configuration. More users and groups can be assigned later.

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

Step 2: Set up StarLeaf for provisioning

Before you configure StarLeaf for automatic user provisioning with Microsoft Entra ID, you need to configure SCIM provisioning in StarLeaf:

  1. Sign in to your StarLeaf Admin Console. Navigate to Integrations > Add integration.

    Screenshot of the StarLeaf Admin Console with the Integrations and Add integration options called out.

  2. Select the Type to be Microsoft Entra ID. Enter a suitable name in Name. Select Apply.

    Screenshot of the Add integration dialog box with the Type and Name text boxes called out.

  3. The SCIM base URL and Access token values are then displayed. These values are entered in the Tenant URL and Secret Token fields in the Provisioning tab of your StarLeaf application.

    Screenshot of the Edit integration dialog box with the Type, Name, and SCIM base URL text boxes called out.

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

To add StarLeaf 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 StarLeaf, select StarLeaf in the results panel.

    Screenshot of the StarLeaf in the results list.

Step 4: Configure automatic user provisioning to StarLeaf

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users and/or groups in StarLeaf based on user and/or group assignments 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 the Enterprise applications blade.

  3. In the applications list, select StarLeaf.

    Screenshot of the StarLeaf 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 the New configuration option on the Provisioning page.

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

    Screenshot of Provisioning test connection.

  7. Select Create to create your configuration.

  8. Select Properties on the Overview page.

  9. Select the Edit icon to edit the properties. Enable notification emails and provide an email to receive quarantine notifications. Enable Accidental deletions prevention. Select Apply to save the changes.

    Screenshot of the Provisioning properties page.

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

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

    Screenshot of the Attribute Mappings section showing nine mappings displayed.

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

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

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

Step 5: Monitor your deployment

Once you configure provisioning, use the following resources to monitor your deployment:

  1. Use the provisioning logs to determine which users are provisioned successfully or unsuccessfully
  2. Check the progress bar to see the status of the provisioning cycle and how close it's to completion
  3. If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states the application provisioning quarantine status article.

Connector limitations

  • StarLeaf doesn't currently support group provisioning.
  • StarLeaf requires email and userName values to have the same source value.

More resources