RingCentral + Microsoft Teams Direct Routing Integration

Audience: IT Admins / Service Desk
Systems: RingCentral, Microsoft Teams, Microsoft Entra ID (Azure AD)

Overview

RingCentral integrates with Microsoft Teams using Direct Routing, allowing users to place and receive calls directly within the Teams client instead of the RingCentral app. For the integration to function correctly, user provisioning, licensing, and group membership must be aligned across RingCentral and Entra ID.

High‑Level Architecture

• RingCentral acts as the PSTN provider

• Microsoft Teams is the softphone interface

• Entra ID (Azure AD) manages user access via security groups

Prerequisites for a Working Integration

For a user to successfully use RingCentral calling inside Teams, all of the following must be true:

1. User exists in RingCentral

2. User is a member of the RingCentral - Enable Teams Calling group in Entra ID

3. User has:

   • A phone number assigned in RingCentral

   • The Teams integration toggle enabled in RingCentral

4. User is signed into the Teams desktop client (not web-only) and relaunched after provisioning

Verification Steps (Admin)

1. Check Entra ID

   • Confirm user is in the RingCentral - Enable Teams Calling Entra group

   • Group membership drives automatic provisioning

2. Check RingCentral User

   • Verify a phone number is assigned

   • Confirm Teams integration toggle is enabled

End‑User Experience: RingCentral Calling Inside Microsoft Teams

From the end user’s perspective, nothing new needs to be installed or learned beyond Microsoft Teams.

Once their account is fully provisioned:

• Users make and receive phone calls directly inside the Microsoft Teams desktop app

• Calling appears in Teams just like a native phone system (dial pad, call history, voicemail)

• Their existing RingCentral phone number is used for all inbound and outbound calls

• No separate RingCentral app is required when Teams integration is enabled