Tutorial: Configure Ardoq for automatic user provisioning
This tutorial describes the steps you need to perform in both Ardoq and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users to Ardoq 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.
- Create users in Ardoq.
- Remove users in Ardoq when they do not require access anymore.
- Keep user attributes synchronized between Microsoft Entra ID and Ardoq.
- Single sign-on to Ardoq (recommended).
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).
- An administrator account with Ardoq.
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 Ardoq.
Step 2: Configure Ardoq to support provisioning with Microsoft Entra ID
Provisioning is gated by a feature toggle in Ardoq. If you intend to configure SSO or have already done so, Ardoq will automatically recognize that Microsoft Entra ID is in use, and the provisioning feature will be automatically enabled.
If you don't intend to use the provisioning features of Microsoft Entra ID along with SSO, please reach out to Ardoq customer support and they'll manually enable support for provisioning.
Before we proceed we need to obtain a Tenant Url and a Secret Token, to configure secure communication between Microsoft Entra ID and Ardoq.
Log in to Ardoq admin console.
In the left menu click on profile logo and, navigate to Organization Settings->Manage Organization->Manage SCIM Token.
Click on Generate new.
Copy and save the Token.This value will be entered in the Secret Token field in the Provisioning tab of your Ardoq application.
To create your tenant URL, use this template:
https://<YOUR-SUBDOMAIN>.ardoq.com/api/scim/v2by replacing the placeholder text
<YOUR-SUBDOMAIN>.This value will be entered in the Tenant Url field in the Provisioning tab of your Ardoq application.
<YOUR-SUBDOMAIN>is the subdomain your organization has chosen to access Ardoq. This is the same URL segment you use when you access the Ardoq app. For example, if your organization accesses Ardoq at
https://acme.ardoq.comyou'd fill in
acme. If you're in the US and access Ardoq at
https://piedpiper.us.ardoq.comthen you'd fill in
Step 3: Add Ardoq from the Microsoft Entra application gallery
Add Ardoq from the Microsoft Entra application gallery to start managing provisioning to Ardoq. If you have previously setup Ardoq 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 or group, 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 Ardoq
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 and/or group assignments in Microsoft Entra ID.
To configure automatic user provisioning for Ardoq in Microsoft Entra ID:
Browse to Identity > Applications > Enterprise applications
In the applications list, select Ardoq.
Select the Provisioning tab.
Set the Provisioning Mode to Automatic.
Under the Admin Credentials section, input your Ardoq Tenant URL and Secret Token. Click Test Connection to ensure Microsoft Entra ID can connect to Ardoq. If the connection fails, ensure your Ardoq 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.
Under the Mappings section, select Synchronize Microsoft Entra users to Ardoq.
Review the user attributes that are synchronized from Microsoft Entra ID to Ardoq in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Ardoq for update operations. If you choose to change the matching target attribute, you'll need to ensure that the Ardoq API supports filtering users based on that attribute. Select the Save button to commit any changes.
Attribute Type Supported for filtering Required by Ardoq userName String ✓ ✓ active Boolean ✓ displayName String ✓ roles[primary eq "True"].value String ✓
To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.
To enable the Microsoft Entra provisioning service for Ardoq, change the Provisioning Status to On in the Settings section.
Define the users that you would like to provision to Ardoq by choosing the desired values in Scope in the Settings section.
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.
- Managing user account provisioning for Enterprise Apps
- What is application access and single sign-on with Microsoft Entra ID?