Azure Active Directory uses a concept called assignments to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users and/or groups that have been assigned to an application in Azure AD are synchronized.
Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Azure AD need access to Dialpad. Once decided, you can assign these users and/or groups to Dialpad by following the instructions here.
Keep in mind that Microsoft Azure SCIM provisioning only supports the Dialpad Talk license type.
In this article, we will demonstrate the steps to be performed in Dialpad and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to Dialpad.
To perform the steps below, you will need to have the following:
- An Azure AD tenant
- A Dialpad tenant
- A user account in Dialpad with Admin permissions
Generate API Key in Dialpad
- Navigate to Admin Settings > My Company > Authentication> API keys
- Select Add a key and generate a new API key for Azure
This API key will be used later when authenticating with Azure.
Add Dialpad from the gallery
To configure Dialpad for automatic user provisioning with Azure AD, you need to add Dialpad from the Azure AD application gallery to your list of managed SaaS applications.
To add Dialpad from the Azure AD application gallery, perform the following steps:
- In the Azure portal, in the left navigation panel, select Azure Active Directory.
- Go to Enterprise applications, and then select All applications.
- To add a new application, select the New application button at the top of the pane.
- In the search box, enter Dialpad, select Dialpad in the results panel.
- Navigate to the URL highlighted below in a separate browser.
- In the top right-hand corner, select Log In > Use Dialpad online.
- As Dialpad is an OpenIDConnect app, choose to login to Dialpad using your Microsoft work account.
- After successful authentication, accept the consent prompt for the consent page. The application will then be automatically added to your tenant and you will be redirected to your Dialpad account.
Configure Automatic User Provisioning in Dialpad
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Dialpad based on user and/or group assignments in Azure AD.
- Sign in to the Azure portal. Select Enterprise Applications, then select All Applications.
- In the applications list, select Dialpad.
- Select the Provisioning tab.
- Set the Provisioning Mode to Automatic.
- Under the Admin Credentials section, input
https://dialpad.com/scimin Tenant URL. Input the value that you retrieved and saved earlier from Dialpad in Secret Token. Click Test Connection to ensure Azure AD can connect to Dialpad. If the connection fails, ensure your Dialpad 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 check the checkbox - Send an email notification when a failure occurs.
- Click Save.
- Under the Mappings section, select Synchronize Azure Active Directory Users to Dialpad.
- Review the user attributes that are synchronized from Azure AD to Dialpad in the Attribute Mapping section. The attributes selected as Matching properties are used to match the user accounts in Dialpad for update operations. Select the Save button to commit any changes.
- To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.
- To enable the Azure AD provisioning service for Dialpad, change the Provisioning Status to On in the Settings section.
- Define the users and/or groups that you would like to provision to Dialpad 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 of all users and/or groups defined in Scope in the Settings section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. You can use the Synchronization Details section to monitor progress and follow links to the provisioning activity report, which describes all actions performed by the Azure AD provisioning service on Dialpad.
Connector Limitations
Dialpad does not support group renames today. This means that any changes to the displayName of a group in Azure AD will not be updated and reflected in Dialpad.
Awesome