Tutorial: Configure Humbol for automatic user provisioning

This tutorial describes the steps you need to perform in both Humbol and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users to Humbol using the Microsoft Entra 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.

Supported capabilities

• Create users in Humbol.
• Remove users in Humbol when they do not require access anymore.
• Keep user attributes synchronized between Microsoft Entra ID and Humbol.
• Single sign-on to Humbol (recommended).

Prerequisites

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

• A Microsoft Entra tenant.
• One of the following roles: Application Administrator, Cloud Application Administrator, or Application Owner.
• Active contract with Humbol including SCIM API usage with Humbol Inc.
• A user account in Humbol 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 Microsoft Entra ID and Humbol.

Step 2: Configure Humbol to support provisioning with Microsoft Entra ID

Contact Humbol support to configure Humbol to support provisioning with Microsoft Entra ID.

1. As Humbol Admin login to your Humbol organization.
2. Go to organization's API settings page.
   1. On this page you can find the organization SCIM API url. Copy it.
   2. Create SCIM API token and copy the value.

   Note

   The token value is not saved anywhere on the Humbol service, so if you lose it, you should create a new one and remove old one.

Step 3: Add Humbol from the Microsoft Entra application gallery

Add Humbol from the Microsoft Entra application gallery to start managing provisioning to Humbol. If you have previously setup Humbol 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 Microsoft Entra provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users to the application. If you choose to scope who will be provisioned based solely on attributes of the user, you can use a scoping filter as described here.

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

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

Step 5: Configure automatic user provisioning to Humbol

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

To configure automatic user provisioning for Humbol 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

   

3. In the applications list, select Humbol.

   

4. Select the Provisioning tab.

   

5. Set the Provisioning Mode to Automatic.

   

6. Under the Admin Credentials section, input your Humbol Tenant URL and Secret Token. Click Test Connection to ensure Microsoft Entra ID can connect to Humbol. If the connection fails, ensure your Humbol account has Admin permissions and try again.

   

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

   

8. Select Save.

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

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

    Attribute	Type	Supported for filtering	Required by Humbol
    userName	String	✓	✓
    active	Boolean		✓
    title	String
    emails[type eq "work"].value	String		✓
    preferredLanguage	String
    name.givenName	String		✓
    name.familyName	String		✓
    addresses[type eq "work"].locality	String
    addresses[type eq "work"].region	String
    addresses[type eq "work"].country	String
    roles[primary eq "True"].value	String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department	String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager	String

    Note

    • If you include roles[primary eq "True"].value every user must have precisely one role.
    • Another option is to remove the role attribute mapping and manage Humbol user roles inside the Humbol application.

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

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

    

13. Define the users that you would like to provision to Humbol by choosing the desired values in Scope in the Settings section.

    

14. When you're ready to provision, click Save.

    

This operation starts the initial synchronization cycle of all users defined in Scope in the Settings section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Microsoft Entra provisioning service is running.

Step 6: Monitor your deployment

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

• Use the provisioning logs to determine which users have been 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 goes into quarantine. Learn more about quarantine states here.

More resources

• Managing user account provisioning for Enterprise Apps
• What is application access and single sign-on with Microsoft Entra ID?

Next steps

• Learn how to review logs and get reports on provisioning activity