Tutorial: Configure Dialpad for automatic user provisioning

The objective of this tutorial is to 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.

Note

This tutorial describes a connector built on top of the Azure AD User 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 Azure Active Directory.

This connector is currently in Preview. For more information on the general Microsoft Azure terms of use for Preview features, see Supplemental Terms of Use for Microsoft Azure Previews.

Prerequisites

The scenario outlined in this tutorial assumes that you already have the following prerequisites:

  • An Azure AD tenant.
  • A Dialpad tenant.
  • A user account in Dialpad with Admin permissions.

Assign Users to Dialpad

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:

Important tips for assigning users to Dialpad

  • It is recommended that a single Azure AD user is assigned to Dialpad to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.

  • When assigning a user to Dialpad, you must select any valid application-specific role (if available) in the assignment dialog. Users with the Default Access role are excluded from provisioning.

Setup Dialpad for provisioning

Before configuring Dialpad for automatic user provisioning with Azure AD, you will need to retrieve some provisioning information from Dialpad.

  1. Sign in to your Dialpad Admin Console and select Admin settings. Ensure that My Company is selected from the dropdown. Navigate to Authentication > API Keys.

    Screenshot of the Dialpad admin console, with the settings icon, My Company, Authentication, and A P I keys highlighted, and My Company selected.

  2. Generate a new key by clicking Add a key and configuring the properties of your secret token.

    Screenshot of the A P I keys page in the Dialpad admin console. Add a key is highlighted.

    Screenshot of the Edit A P I key page in the Dialpad admin console. The Save button is highlighted.

  3. Click the Click to show value button for your recently created API key and copy the value shown. This value will be entered in the Secret Token field in the Provisioning tab of your Dialpad application in the Azure portal.

    Dialpad Create Token

To configuring 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:

  1. In the Azure portal, in the left navigation panel, select Azure Active Directory.

    The Azure Active Directory button

  2. Go to Enterprise applications, and then select All applications.

    The Enterprise applications blade

  3. To add a new application, select the New application button at the top of the pane.

    The New application button

  4. In the search box, enter Dialpad, select Dialpad in the results panel. Dialpad in the results list

  5. Navigate to the URL highlighted below in a separate browser.

    Screenshot of a page displaying information about the Dialpad app. Under U R L, an address is listed and is highlighted.

  6. In the top right-hand corner, select Log In > Use Dialpad online.

    Screenshot of the Dialpad website. Log in is highlighted, and the Log in tab is open. Use Dialpad online is also highlighted.

  7. As Dialpad is an OpenIDConnect app, choose to login to Dialpad using your Microsoft work account.

    Screenshot of the Start making calls page in the Dialpad website. The Log in with Office 365 button is highlighted.

  8. After a 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.

    Screenshot showing a Microsoft authentication page stating that the Dialpad app has requested access to some data. The Accept button is highlighted.

Configure automatic user provisioning to 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.

To configure automatic user provisioning for Dialpad in Azure AD:

  1. Sign in to the Azure portal. Select Enterprise Applications, then select All applications.

    Enterprise applications blade

  2. In the applications list, select Dialpad.

    The Dialpad link in the Applications list

  3. Select the Provisioning tab.

    Screenshot of the Manage options with the Provisioning option called out.

  4. Set the Provisioning Mode to Automatic.

    Screenshot of the Provisioning Mode dropdown list with the Automatic option called out.

  5. Under the Admin Credentials section, input https://dialpad.com/scim in 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.

    Tenant URL + Token

  6. 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.

    Notification Email

  7. Click Save.

  8. Under the Mappings section, select Synchronize Azure Active Directory Users to Dialpad.

    Dialpad User Mappings

  9. 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.

    Dialpad User Attributes

  10. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

  11. To enable the Azure AD provisioning service for Dialpad, change the Provisioning Status to On in the Settings section.

    Provisioning Status Toggled On

  12. 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.

    Provisioning Scope

  13. When you are ready to provision, click Save.

    Saving Provisioning Configuration

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 provisioning activity report, which describes all actions performed by the Azure AD provisioning service on Dialpad.

For more information on how to read the Azure AD provisioning logs, see Reporting on automatic user account provisioning

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.

Additional resources

Next steps