Tutorial: Configure ThousandEyes for automatic user provisioning
The objective of this tutorial is to show you the steps you need to perform in ThousandEyes and Azure AD to automatically provision and de-provision user accounts from Azure AD to ThousandEyes.
The scenario outlined in this tutorial assumes that you already have the following items:
- An Azure Active directory tenant
- A ThousandEyes tenant with the Standard plan or better enabled
- A user account in ThousandEyes with Admin permissions
The Azure AD provisioning integration relies on the ThousandEyes SCIM API, which is available to ThousandEyes teams on the Standard plan or better.
Assigning users to ThousandEyes
Azure Active Directory uses a concept called "assignments" to determine which users should receive access to selected apps. In the context of automatic user account provisioning, only the users and groups that have been "assigned" to an application in Azure AD is synchronized.
Before configuring and enabling the provisioning service, you need to decide what users and/or groups in Azure AD represent the users who need access to your ThousandEyes app. Once decided, you can assign these users to your ThousandEyes app by following the instructions here:
Important tips for assigning users to ThousandEyes
It is recommended that a single Azure AD user is assigned to ThousandEyes to test the provisioning configuration. Additional users and/or groups may be assigned later.
When assigning a user to ThousandEyes, you must select either the User role, or another valid application-specific role (if available) in the assignment dialog. The Default Access role does not work for provisioning, and these users are skipped.
Configuring user provisioning to ThousandEyes
This section guides you through connecting your Azure AD to ThousandEyes's user account provisioning API, and configuring the provisioning service to create, update, and disable assigned user accounts in ThousandEyes based on user and group assignment in Azure AD.
You may also choose to enabled SAML-based Single Sign-On for ThousandEyes, following the instructions provided in Azure portal. Single sign-on can be configured independently of automatic provisioning, though these two features compliment each other.
Configure automatic user account provisioning to ThousandEyes in Azure AD
In the Azure portal, browse to the Azure Active Directory > Enterprise Apps > All applications section.
If you have already configured ThousandEyes for single sign-on, search for your instance of ThousandEyes using the search field. Otherwise, select Add and search for ThousandEyes in the application gallery. Select ThousandEyes from the search results, and add it to your list of applications.
Select your instance of ThousandEyes, then select the Provisioning tab.
Set the Provisioning Mode to Automatic.
Under the Admin Credentials section, input the OAuth Bearer Token generated by your ThousandEyes's account (you can find and or generate a token under your ThousandEyes account Profile section).
In the Azure portal, click Test Connection to ensure Azure AD can connect to your ThousandEyes app. If the connection fails, ensure your ThousandEyes account has Admin permissions and try step 5 again.
Enter the email address of a person or group who should receive provisioning error notifications in the Notification Email field, and check the checkbox "Send an email notification when a failure occurs."
Under the Mappings section, select Synchronize Azure Active Directory Users to ThousandEyes.
In the Attribute Mappings section, review the user attributes that are synchronized from Azure AD to ThousandEyes. The attributes selected as Matching properties are used to match the user accounts in ThousandEyes for update operations. Select the Save button to commit any changes.
To enable the Azure AD provisioning service for ThousandEyes, change the Provisioning Status to On in the Settings section
This operation starts the initial synchronization of any users and/or groups assigned to ThousandEyes in the Users and Groups section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the service is running. You can use the Synchronization Details section to monitor progress and follow links to provisioning activity logs, which describe all actions performed by the provisioning service.
For more information on how to read the Azure AD provisioning logs, see Reporting on automatic user account provisioning.
- Managing user account provisioning for Enterprise Apps
- What is application access and single sign-on with Azure Active Directory?
Send feedback about: