Tutorial: Configure Tribeloo for automatic user provisioning

Article
10/23/2023

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

Capabilities Supported

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

Prerequisites

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

A Microsoft Entra tenant.
A user account in Microsoft Entra ID with permission to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
A Tribeloo tenant.
A user account in Tribeloo with Admin permissions.

Step 1: Plan your provisioning deployment

Learn about how the provisioning service works.
Determine who will be in scope for provisioning.
Determine what data to map between Microsoft Entra ID and Tribeloo.

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

Navigate to the Tribeloo app and log as a user with Admin permissions.

Using the side menu(1), navigate to Admin(2), select User management(3)
Select the User provisioning(1) tab. On this tab, you have access to Tribeloo information that you will have to use to configure the Microsoft Entra integration.
1. SCIM base URL (2)
2. SCIM Bearer token (3)
Copy these values to the clipboard and paste them in the corresponding Microsoft Entra ID fields (see Step 5). The AD fields are named Tenant URL and Secret Token respectively.
On the User Provisioning tab you can now click the Enable User provisioning(1) button to enable user provisioning in Tribeloo.

Step 3: Add Tribeloo from the Microsoft Entra application gallery

Add Tribeloo from the Microsoft Entra application gallery to start managing provisioning to Tribeloo. If you have previously setup Tribeloo for SSO you can use the same application. However it is 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 / 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 Tribeloo

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

To configure automatic user provisioning for Tribeloo in Microsoft Entra ID:

Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
Browse to Identity > Applications > Enterprise applications
In the applications list, select Tribeloo.
Select the Provisioning tab.
Set the Provisioning Mode to Automatic.
In the Admin Credentials section, input your Tribeloo Tenant URL and Secret Token. Click Test Connection to ensure Microsoft Entra ID can connect to Tribeloo. If the connection fails , ensure your Tribeloo account has Admin permissions and try again.
In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box.
Select Save.
In the Mappings section, select Synchronize Microsoft Entra users to Tribeloo.

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

Attribute	Type	Supported for filtering
userName	String	✓
emails[type eq "work"].value	String
active	Boolean
displayName	String
name.givenName	String
name.familyName	String
addresses[type eq "work"].formatted	String

To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.
To enable the Microsoft Entra provisioning service for Tribeloo, change the Provisioning Status to On in the Settings section.
Define the users and/or groups that you would like to provision to Tribeloo by choosing the desired values in Scope in the Settings section.
When you are ready to provision, click Save.

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 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 is to completion
If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states here.

Change Log

08/12/2021 - Added support for core user attributes emails[type eq "work"].value and addresses[type eq "work"].formatted.

More resources

Next steps

Learn how to review logs and get reports on provisioning activity