The Azure Active Directory People Data Integration lets you create a scheduled import of your people data into Ardoq.
In short, it lets you take your list of users from Active Directory...
...and import them into an Ardoq workspace:
Requirements to use this Integration
- You must be an admin of your Ardoq organization to use this integration.
- The Ardoq organization must have Active Directory single sign-on enabled.
- You must grant consent for the AD integration to read information about users in Active Directory.
In addition, it is beneficial to have enabled the Managed Workspaces toggle as well.
On opening the integration for the first time you’ll be asked to grant permission for Ardoq to access data from Active Directory. This is done by clicking Grant Consent:
Clicking Grant Consent will take you to Microsoft’s consent page:
If you are not an administrator in Active Directory you can share the Grant Consent link with an Active Directory administrator and ask them to approve the application.
They do not need to be an Ardoq user to approve the Ardoq People Data Integration application.
Once you or the administrator have approved the application, click the Refresh button to test that you can retrieve data from Active Directory.
Why are these permissions required?
This integration can be scheduled to run at regular intervals to keep a workspace up to date, and must therefore have "application level" permission to read user information.
Configuring the Integration
Once consent has been granted and the page refreshed, the integration should be ready to set up.
Note that “displayName” is required and is mapped to the Component Name.
You can now select a target workspace, set up a schedule, and map fields from Active Directory to that target workspace.
You can use filters to restrict the number of components you import into your workspace. Apply a filter by clicking on the arrow icon next to the property name.
Once you’re done configuring the import, click Test Import in the top right corner. This will show you the results of the test import.
If you’ve set the integration to be scheduled you will be able to Schedule the Import, otherwise, you will be able to Import All.
Once you’re done, you can go to Ardoq's asset manager and see the new workspace the import has created.
For this integration, you are able to choose whether you want to schedule the integration or not.
If you set the integration to be scheduled, the workspace will become a Managed Workspace, meaning that restrictions will apply when trying to edit components in the workspace.
Let's now go through the most commonly-used fields from Active Directory and explain what they are.
Id (unique, recommended)
This is the user’s unique ID in Active Directory. This field is recommended, as it makes the scheduled integration more robust when dealing with name changes for users. If this field is not mapped, Ardoq will try to match users with existing components of the same name, meaning that renamed users will be created as new Person components.
This is the user’s full name. Since Ardoq integrations require a component name, this is required and will always map to the component name.
This is a user’s email address.