Configure RingCentral for automatic user provisioning with Microsoft Entra ID

This article describes the steps you need to perform in both RingCentral and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users and groups to RingCentral 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.

Capabilities supported

• Create users in RingCentral
• Remove users in RingCentral when they don't require access anymore
• Keep user attributes synchronized between Microsoft Entra ID and RingCentral
• Single sign-on to RingCentral (recommended)

Prerequisites

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

• A Microsoft Entra tenant
• A user account in Microsoft Entra ID with permission to configure provisioning (like Application Administrator, Cloud Application Administrator, or Application Owner).
• A RingCentral tenant
• A user account in RingCentral with Admin permissions.

Note

This integration is also available to use from Microsoft Entra US Government Cloud environment. You can find this application in the Microsoft Entra US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.

Step 1: Plan your provisioning deployment

1. Learn about how the provisioning service works.
2. Determine who's in scope for provisioning.
3. Determine what data to map between Microsoft Entra ID and RingCentral.

Step 2: Configure RingCentral to support provisioning with Microsoft Entra ID

A RingCentral admin account is required to Authorize in the Admin Credentials section in Step 5.

In the RingCentral admin portal, under Account Settings -> Directory Integrations, set the Directory Provider setting to SCIM

Note

To assign licenses to users, refer to the video link here.

Step 3: Add RingCentral from the Microsoft Entra application gallery

Add RingCentral from the Microsoft Entra application gallery to start managing provisioning to RingCentral. If you have previously setup RingCentral for SSO you can use the same application. However, we recommend 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 is in scope for provisioning

The Microsoft Entra provisioning service allows you to scope who is provisioned based on assignment to the application, or based on attributes of the user or group. If you choose to scope who is provisioned to your app based on assignment, you can use the steps to assign users and groups to the application. If you choose to scope who is provisioned based solely on attributes of the user or group, you can use a scoping filter.

• Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an attribute based scoping filter.

• If you need extra roles, you can update the application manifest to add new roles.

Step 5: Configure automatic user provisioning to RingCentral

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Microsoft Entra ID.

To configure automatic user provisioning for RingCentral in Microsoft Entra ID:

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

2. Browse to Entra ID > Enterprise apps

   

3. In the applications list, select RingCentral.

   

4. Select the Provisioning tab.

   

5. Set + New configuration.

   

6. In the Tenant URL field, input your RingCentral Tenant URL and Secret Token. Select Test Connection to ensure Microsoft Entra ID can connect to RingCentral. If the connection fails, ensure your RingCentral account has the required admin permissions and try again.

   

7. Select Create to create your configuration.

8. Select Properties in the Overview page.

9. Select the pencil to edit the properties. Enable notification emails and provide an email to receive quarantine emails. Enable accidental deletions prevention. Select Apply to save the changes.

   

10. Select Attribute Mapping in the left panel and select users.

11. Review the user attributes that are synchronized from Microsoft Entra ID to RingCentral in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in RingCentral for update operations. If you choose to change the matching target attribute, you need to ensure that the RingCentral API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Attribute	Type
    userName	String
    externalId	String
    active	Boolean
    title	String
    emails[type eq "work"].value	String
    addresses[type eq "work"].country	String
    addresses[type eq "work"].region	String
    addresses[type eq "work"].locality	String
    addresses[type eq "work"].postalCode	String
    addresses[type eq "work"].streetAddress	String
    name.givenName	String
    name.familyName	String
    phoneNumbers[type eq "mobile"].value	String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department	String

12. To configure scoping filters, refer to the following instructions provided in the Scoping filter article article.

13. Use on-demand provisioning to validate sync with a small number of users before deploying more broadly in your organization.

14. When you're ready to provision, select Start Provisioning from the Overview page.

Step 6: Monitor your deployment

Once you configure provisioning, use the following resources to monitor your deployment:

1. Use the provisioning logs to determine which users are provisioned successfully or unsuccessfully
2. Check the progress bar to see the status of the provisioning cycle and how close it's to completion
3. If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states the application provisioning quarantine status article.

Change log

• 09/10/2020 - Removed support for "displayName" and "manager" attributes.
• 03/15/2021 - Updated authorization method from permanent bearer token to OAuth code grant flow.
• 10/28/2021 - Updated default mapping to mail-> emails[type eq “work”].value.
• 10/28/2021 - Rate limiting updated to 300/min for read, 1000/min for write.

Additional resources

• Managing user account provisioning for Enterprise Apps
• What is application access and single sign-on with Microsoft Entra ID?

Related content

• Learn how to review logs and get reports on provisioning activity