Before you begin
Make sure your company uses cloud based Azure AD. Currently, we do not support on-prem Azure AD, hybrid environment or AD B2C.
Why set up provisioning?
Improve the HR - IT flow with provisioning's auto-sync capabilities that automatically update changes, create accounts for new hires, or close accounts for terminated employees.
When is the user created in Azure AD?
Based on the configuration, Bob can create the user once the user's profile has been created in Bob.
Default user field mapping
You define how Bob employee fields will be mapped to Azure fields. The synchronization of user information will be according to the user field mappings you define. The table below shows the default field mappings:
What information does Bob need to set up the integration?
To activate the provisioning process, bob requires the following:
Tenant name for the Azure AD account
Note: An application needs to be created (see "Create an Azure Active Directory application").
Don't know how to get the above? Follow this link for additional information on how to obtain the app ID and how to generate the API authentication key.
You will need to provide permissions for the integration to work (for additional information, click here):
Select Settings > Required permissions, and then click Add.
Select an API and Microsoft Graph.
In Application Permissions, select the Directory.ReadWrite.All permission
In the Required permissions panel, click Grant permissions.
Setting up Azure AD provisioning in the Bob app
- From the left menu, select Settings > Integrations.
- In the Provisioning category, select the Azure AD thumbnail.
- Copy the Application ID (Client id), API key (Secret) and Tenant name of your Azure AD account into the Azure AD provisioning configuration.
Note: The default password should comply with your Azure AD password policy.
- Click Save.