# Using RingCentral calling with Microsoft Teams

Systems: RingCentral to Microsoft Teams

For Microsoft 365 or Teams administrators who also administer a RingCentral RingEX account.

Canonical: https://warmtransfer.net/guides/ringcentral-with-teams

Last verified: 2026-09-25

This guide steps through integrating RingCentral phone service with Microsoft Teams using either the RingCentral embedded app or native Direct Routing[^31][^28]. It covers prerequisite licensing, tenant connection, user provisioning, queue interactions, and emergency calling setup[^17][^54].

## Before you start

Before starting deployment, assemble the required accounts, software components, and administrative access across both platforms[^38][^21]:

- Confirm user operating systems: the desktop integration supports Windows 10 or later and macOS 10.15 Catalina or later, while Windows 7, 8, and 8.1 and macOS 10.13 and 10.14 are not supported[^38].
- Verify that users are homed online in Microsoft 365[^25].
- Direct Routing is not supported when Teams is in Islands mode[^14].
- Teams Phone has 4 PSTN connectivity models: Microsoft Teams Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing[^61]. Direct Routing requires a contract with a third-party PSTN provider and a certified Session Border Controller (SBC) procured and managed by the customer, an integrator, or a DRaaS provider[^62].
- RingCentral describes its Direct Routing-as-a-Service as enabling Teams telephony without on-premises infrastructure[^28]. Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used, and support issues go to the SBC vendor first[^8].
- RingCentral states that Cloud PBX 1.0 for Microsoft Teams will be retired and customers must migrate to RingCentral native Direct Routing[^1]. Direct Routing BYOC support became available in Controlled Availability in RingCentral release 25.1[^7].
- Enabling auto attendant and call queue services requires at least 1 Teams Phone license in the tenant[^63].

## What changes by situation

- Where should calls ring and be placed? RingCentral embedded app inside Teams; RingCentral as the Direct Routing provider; RingCentral Direct Routing plus the embedded app in companion mode.
- Will RingCentral call queues ring these Teams users? Users take direct calls only; RingCentral call queues deliver calls to these users.
- How do your users' emergency locations behave? Fixed registered address; Location follows client.

## Step 1: Confirm Microsoft licensing

**RingCentral embedded app inside Teams**

### Do
Confirm that each user holds a supported license: RingCentral lists Microsoft 365 Enterprise E1, E3, and E5, Business Standard and Business Premium, and Frontline F1 and F3 as supported licenses for the embedded app[^32]. WarmTransfer's reading of the sources is that because the embedded app places calls through the RingCentral desktop plugin rather than Teams Phone, a Teams Phone license is probably not needed for embedded-app calling[^34].

### Verify
Suggested check: verify that each user has an assigned enterprise, business, or frontline license.

### Rollback
Suggested rollback: unassign any newly assigned licenses in the admin center.

**RingCentral as the Direct Routing provider**

### Do
Assign the required Microsoft licenses to each user: Microsoft states that Direct Routing requires a Teams Phone license[^13]. Teams Phone is a separate add-on license; Teams Phone Standard provides Teams Phone alone, and PSTN connectivity must be chosen in addition for external calls[^60]. RingCentral states that each Teams end user on Direct Routing must be assigned the applicable Microsoft licensing for phone calls[^23].

Setting up RingCentral Direct Routing needs 4 spare Microsoft end-user licenses with Teams phone capability, used temporarily to verify and create SBC domains and returned after setup[^11]. RingCentral accepts TEAMS1, TEAMS_GOV, TEAMS_FREE, TEAMS_AR_GCCHIGH, and TeamsEss as alternative license types for the spare setup licenses[^6].

### Verify
Suggested check: confirm that all target users have phone licenses assigned and that spare unassigned phone-capable licenses are available.

### Rollback
Suggested rollback: unassign the phone licenses from the users in the admin center.

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Assign Teams Phone to each user, because Microsoft states that Direct Routing requires a Teams Phone license[^13]. Teams Phone Standard provides Teams Phone alone, requiring separate PSTN connectivity[^60], and RingCentral requires each Direct Routing user to hold the applicable Microsoft licensing for phone calls[^23].

Confirm that each user holds one of the Microsoft 365 Enterprise E1, E3, and E5, Business Standard and Business Premium, or Frontline F1 and F3 licenses supported for the embedded app[^32].

Setting up RingCentral Direct Routing needs 4 spare Microsoft end-user licenses with Teams phone capability, used temporarily to verify and create SBC domains and returned after setup[^11]; RingCentral accepts TEAMS1, TEAMS_GOV, TEAMS_FREE, TEAMS_AR_GCCHIGH, and TeamsEss as alternative license types for the spare setup licenses[^6].

### Verify
Suggested check: verify that pilot users have both a supported base suite and phone capabilities, and confirm the availability of spare phone-capable licenses.

### Rollback
Suggested rollback: unassign the newly assigned licenses in the admin center.

## Step 2: Confirm RingCentral plan and identity prerequisites

**RingCentral embedded app inside Teams**

### Do
Before installing the embedded app, verify that the user principal name and email address match between each user's Microsoft and RingCentral accounts[^43]. Verify client endpoints run Windows 10 or later or macOS 10.15 Catalina or later[^38].

### Verify
Confirm that user principal names and email addresses match identically across both environments; otherwise chat notifications and personal contacts will not display[^43].

### Rollback
Suggested rollback: revert any modified user principal names or email attributes in the respective directory.

**RingCentral as the Direct Routing provider**

### Do
Confirm that the RingCentral account is on RingEX Core, Advanced, or Ultra, or on a legacy Standard, Premium, or Ultimate plan[^21]. Confirm that the Microsoft tenant is not in Islands mode[^14] and that users are homed online in Microsoft 365[^25].

### Verify
Suggested check: verify the subscription name in the portal and check coexistence mode in the admin center.

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Confirm the RingCentral subscription is on RingEX Core, Advanced, or Ultra, or on legacy Standard, Premium, or Ultimate[^21]. Confirm that Teams is not in Islands mode[^14] and users are homed online in Microsoft 365[^25]. Verify that user principal names and email addresses match between Microsoft and RingCentral accounts[^43].

### Verify
Confirm that user principal names and email addresses match identically across both directories so chat notifications and personal contacts display[^43].

## Step 3: Line up administrator roles

**RingCentral embedded app inside Teams**

### Do
Assign the required administrator roles on both platforms: installing the embedded app via OAuth needs RingCentral Super Admin and User Admin, and on the Microsoft side either Global Admin or the combination of Privileged Roles Admin, User Admin, Teams Admin, and Application Admin[^36]. Alternatively, managing the policies that install the embedded app from the Teams admin center needs Global Administrator or Privileged Roles Administrator, plus Teams Administrator[^41].

### Verify
Suggested check: confirm the installing administrator account holds the assigned roles in the admin portal.

### Rollback
Suggested rollback: remove temporary role assignments from the administrator accounts.

**RingCentral as the Direct Routing provider**

### Do
Ensure an administrator with Microsoft 365 Global Admin is available: the RingCentral Direct Routing OAuth setup requires a Microsoft 365 Global Admin[^16]. Direct Routing release 24.1 (4 March 2024) added setup support for Microsoft PIM-enabled admins and Azure Active Directory authentication as an alternative to OAuth[^19].

### Verify
Suggested check: verify that the administrator initiating the connection has an active global admin role or active elevation.

### Rollback
Suggested rollback: deactivate elevated roles or remove administrator role assignments.

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Arrange an administrator holding Microsoft 365 Global Admin for the initial Direct Routing OAuth connection[^16] (or PIM-enabled admin access[^19]), alongside RingCentral Super Admin and User Admin roles[^36].

### Verify
Suggested check: verify administrator privileges across both directory environments.

### Rollback
Suggested rollback: revoke temporary administrator permissions.

## Step 4: Connect RingCentral to the Microsoft tenant

**RingCentral embedded app inside Teams**

### Do
Connect the embedded app: in the RingCentral Admin Portal, go to More > Account Settings > Microsoft Teams > Embedded App > Connect via OAuth, sign in as a Microsoft 365 admin, consent on behalf of the organisation, and authorise the integration[^37]. Accounts with more than 15,000 users are directed to install the embedded app from the Teams admin center rather than from the RingCentral Admin Portal[^29].

### Verify
Suggested check: confirm that the admin portal shows the embedded app status as connected.

**RingCentral as the Direct Routing provider**

### Do
Initiate the Direct Routing connection through the RingCentral Admin Portal using Global Admin credentials[^16]. The Direct Routing OAuth connection registers and verifies SBC subdomains in the Microsoft tenant through the Graph API and links voice routing policies to voice routes with PSTN usage records[^17]. Direct Routing release 25.1 added an account-level resync between RingCentral and Azure[^4].

### Verify
In the Teams admin center, confirm that SBC subdomains are verified and that voice routing policies are created and linked to voice routes and PSTN usages[^17]. Confirm voice routing policies are assigned correctly as part of post-configuration verification[^26].

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Establish the Direct Routing OAuth connection using Global Admin credentials to register SBC subdomains and voice routing configuration[^16][^17]. Next, complete the embedded app connection under More > Account Settings > Microsoft Teams > Embedded App > Connect via OAuth, consenting on behalf of the organisation[^37]. Accounts with more than 15,000 users install the embedded app from the Teams admin center instead[^29].

### Verify
Confirm that the SBC subdomains, voice routes, and voice routing policies exist in Teams admin center[^17][^26] and that the embedded app reports connected status in the RingCentral portal[^37].

## Step 5: Enable users

**RingCentral embedded app inside Teams**

### Do
From the OAuth setup screen, choose to install for all, multiple, or a single user[^37]. Alternatively, to install the embedded app from the Teams admin center, create a setup policy under Teams apps > Setup policies, add the RingCentral app (optionally pinned), save, then assign users or groups through Manage users > Assign users[^42].

### Verify
Suggested check: log in as a target user and confirm that the application appears in the navigation app bar.

### Rollback
Suggested rollback: remove the user assignment from the app setup policy in the admin center.

**RingCentral as the Direct Routing provider**

### Do
New Direct Routing users are enabled by turning on the MS Teams Connection toggle for the user in the Admin Portal User List; the migration tool is only for moving from Cloud PBX 1.0[^24]. Since Direct Routing release 25.1 (24 March 2025), an admin with Teams Administrator permissions can enable end users for Direct Routing, replacing an earlier requirement for 3 combined permission types[^22]. Direct Routing release 25.1 also lets admins manage notification preferences for Direct Routing enablement[^15]. RingCentral says Direct Routing 2.0 activation emails cannot be turned off when users are set up individually, for compliance reasons[^5].

### Verify
Suggested check: verify that the user's connection toggle is active and that their status displays as connected in the portal.

### Rollback
To remove a user whose Microsoft Teams connection failed, first reset the integration status with Disconnect under Microsoft Teams Integration, after which the user can be deleted[^9].

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Enable each user for Direct Routing by turning on the MS Teams Connection toggle in the Admin Portal User List[^24][^22], noting that individual enablement triggers activation emails[^5]. Then, deploy the embedded app via the OAuth installation options[^37] or by creating and assigning an app setup policy in the Teams admin center under Teams apps > Setup policies[^42].

### Verify
Since embedded-app releases 25.1.30 and 25.2.10 (2025), companion mode appears only for users whose Direct Routing status is Connected[^2]. Confirm the user's status is Connected before checking companion mode availability[^2].

### Rollback
Reset the integration status with Disconnect under Microsoft Teams Integration[^9] and unassign the app setup policy in the Teams admin center[^42].

## Step 6: Deploy or bypass the desktop plugin

**RingCentral embedded app inside Teams**

### Do
Deploy the RingCentral desktop plugin to client machines: the embedded app requires the Microsoft Teams app plus the RingCentral desktop plugin, which shows active call controls when a call is placed[^39]. Since embedded-app release 24.1.10 (20 January 2024), admins are notified by email and in the Admin Portal when a new desktop plugin version is available[^40]. Users do not need to sign in to the RingCentral mobile app to make and receive calls from the Teams embedded app[^33].

### Verify
Confirm that placing a call from the embedded app in Teams successfully invokes the desktop plugin and displays active call controls[^39].

### Rollback
Suggested rollback: uninstall the desktop plugin from the user's operating system.

**RingCentral as the Direct Routing provider**

### Do
WarmTransfer's reading of the sources is that because the desktop plugin is required by the embedded app rather than by Direct Routing itself, plain Direct Routing does not require deploying it, and calls are placed and received directly within Microsoft Teams[^39].

### Verify
Suggested check: open the communication client and confirm the native dial pad is present without external helper plugins.

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Do not deploy the desktop plugin: when Direct Routing 2.0 is enabled, the embedded app hides its calling features and runs in companion mode, offering fax, text messaging, and call-history management while calls are made in Teams, and no desktop plugin is needed[^3].

### Verify
Verify that the embedded app operates in companion mode without prompting for or requiring a desktop plugin installation[^3].

## Step 7: Manage cut-over ringing behavior

**RingCentral embedded app inside Teams**

### Do
No additional client cut-over action is required because calls route through the RingCentral desktop plugin associated with the embedded app[^39].

### Verify
Suggested check: place a test call and verify ringing arrives at the embedded app client.

**RingCentral as the Direct Routing provider**

### Do
Sign migrated users out of standalone RingCentral calling clients, or retire those clients; users still active in both RingCentral and Microsoft after moving to Direct Routing receive 2 notifications for each incoming call[^10].

### Verify
Suggested check: place a test incoming call to the user and confirm call alerting behavior.

### Rollback
Suggested rollback: sign the user back in to the standalone client.

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Sign users out of separate standalone RingCentral desktop phone clients, because users active in both RingCentral and Microsoft receive 2 notifications for each incoming call[^10]. The companion app itself hides calling controls and will not generate a second ring[^3].

### Verify
Suggested check: verify that incoming calls ring only in the primary client interface.

### Rollback
Suggested rollback: sign the user back in to the standalone client.

## Step 8: Configure call queues and voicemail

**RingCentral embedded app inside Teams + Users take direct calls only**

### Do
The embedded app provides voicemail notifications and direct user calling natively[^31].

### Verify
Suggested check: leave a test voicemail for the user and confirm notification delivery in the embedded app.

**RingCentral embedded app inside Teams + RingCentral call queues deliver calls to these users**

### Do
The RingCentral embedded app in Teams provides call-queue management alongside calling, unified contact search, SMS, fax, and missed-call, text, and voicemail notifications[^31].

### Verify
Place a test inbound call to the RingCentral call queue and verify that users can answer and manage queue calls directly from the embedded app[^31].

### Rollback
Suggested rollback: remove the user from the call queue.

**RingCentral as the Direct Routing provider + Users take direct calls only**

### Do
Configure user voicemail routing: Direct Routing release 24.4 (16 December 2024) lets admins choose whether a user's voicemail is delivered in Microsoft Teams or in the RingCentral app[^27].

### Verify
Suggested check: call the user while busy or unanswered, leave a message, and verify delivery in the selected destination.

### Rollback
Suggested rollback: toggle the voicemail destination setting back to its previous selection.

**RingCentral as the Direct Routing provider + RingCentral call queues deliver calls to these users**

### Do
For RingCentral call queues serving Direct Routing users, set the queue's phone number type to Voice only, or calls can go to voicemail instead of the queue[^20]. When a Direct Routing user is offline in Teams, Teams voicemail answers the queue call and returns answered, which stops the queue from escalating; RingCentral's remedies are to disable Teams voicemail or enable presence sync so offline users are skipped[^18]. Select voicemail delivery destination (Microsoft Teams or the RingCentral app) under the release 24.4 settings[^27].

### Verify
Sign a test queue member out of Teams, dial the queue, and verify that the call is skipped or escalates rather than being terminated by the offline user's Teams voicemail[^18].

### Rollback
Suggested rollback: restore previous queue number types and re-enable individual voicemail routing.

**RingCentral Direct Routing plus the embedded app in companion mode + Users take direct calls only**

### Do
Select voicemail delivery: configure whether voicemail is delivered in Microsoft Teams or in the RingCentral app using the Direct Routing release 24.4 setting[^27].

### Verify
Suggested check: leave a test message and confirm it arrives at the configured voicemail target.

### Rollback
Suggested rollback: toggle the voicemail delivery setting back in the portal.

**RingCentral Direct Routing plus the embedded app in companion mode + RingCentral call queues deliver calls to these users**

### Do
Set the queue phone number type to Voice only to prevent queue calls dropping to voicemail[^20]. Disable Teams voicemail for queue members or enable presence sync to prevent an offline member's Teams voicemail from answering the call and stopping queue escalation[^18]. Choose whether voicemail is delivered to Microsoft Teams or the RingCentral app[^27].

### Verify
Place a test queue call while a member is offline in Teams and verify the call escalates properly to remaining members[^18].

### Rollback
Suggested rollback: restore the previous number type and revert voicemail settings.

## Step 9: Configure emergency calling

**Fixed registered address + RingCentral embedded app inside Teams**

### Do
Have each user set their RingCentral emergency response location: a RingCentral user's emergency response location is set in the RingCentral desktop app under Settings > Phone > Emergency response location > Manage, and cannot be set in the web or mobile app[^52]. WarmTransfer's reading of the sources is that emergency calls placed from the embedded app travel over RingCentral rather than Teams Phone, so they probably depend on the user's RingCentral emergency response location, not on Teams emergency policies or network locations[^30].

### Verify
Suggested check: open phone settings in the desktop app and verify the registered address.

### Rollback
Suggested rollback: update the emergency response location address in the desktop app.

**Location follows client + RingCentral embedded app inside Teams**

### Do
Embedded-app release 23.3.10 (12 July 2023) added Nomadic ERL support to RingCentral for Microsoft Teams[^35]. Configure company emergency response locations in RingCentral and verify users can access and update their emergency response location via the desktop application[^52]. WarmTransfer's reading of the sources is that embedded app emergency calls route through RingCentral rather than Teams Phone, depending on RingCentral emergency response locations rather than Teams policies[^30].

### Verify
Suggested check: move a test client across network locations and confirm the desktop client prompts for or updates the nomadic emergency response location.

### Rollback
Suggested rollback: update or delete the assigned emergency response locations in the portal.

**Fixed registered address + RingCentral as the Direct Routing provider**

### Do
An emergency address must be validated before it can be assigned to a user or network identifier, and it needs a geo code to be assigned to a network identifier for dynamic emergency calling; addresses created with the Teams admin center map search get both automatically[^44].

Assign an emergency call routing policy: for Direct Routing, emergency numbers and their routing are defined in a Teams emergency call routing policy, which can be assigned to a user, a network site, or both, with site policy taking precedence[^46]. If the Teams client cannot obtain an emergency call routing policy, the Direct Routing user is not enabled for emergency calling[^48].

The Direct Routing emergency call routing policy references an online PSTN usage, and there must be an online voice route for the emergency dial string[^47]. Teams clients no longer prepend a plus sign to emergency numbers, so Direct Routing voice route patterns must match 911 without a leading plus[^49]. Optionally, configure security desk notifications, which are available with Direct Routing and governed by the Teams emergency calling policy[^51].

### Verify
Verify that the emergency call routing policy is assigned to the user[^46]. If a US Direct Routing user's Teams client does not dynamically acquire a US emergency address, the registered emergency address is used and the call is screened to determine whether an updated address is needed before connecting to a PSAP[^50].

### Rollback
Suggested rollback: unassign the emergency call routing policy and remove the registered address assignment.

**Location follows client + RingCentral as the Direct Routing provider**

### Do
Contact RingCentral support to enable Nomadic 911: Nomadic 911 for Teams Direct Routing is enabled by contacting RingCentral support, and every Nomadic 911 user must be associated with the provisioned PBX[^55]. Direct Routing release 23.1 (9 March 2023) introduced Nomadic 911, which sends emergency calls through RingCentral using Teams location settings[^54]. For Direct Routing users, dynamic location for routing emergency calls is supported only in the United States, and in Canada with all calls screened nationally before transfer to the PSAP[^45].

In the Teams admin center, configure trusted IPs, network sites and subnets, emergency addresses and places, and Wi-Fi access points in the Locations pages[^57]. Ensure addresses are validated and geo-coded[^44]. Assign emergency call routing policies referencing an online PSTN usage and voice route matching 911 without a leading plus[^46][^47][^49].

### Verify
Once Nomadic 911 is enabled, confirm the RingCentral Services list shows "RingCentral PBX with E911 PBX 3" (labels from RingCentral's Cloud PBX documentation) with the note that it has an Emergency trunk configured, and users show that service in the Users column[^58].

When a user is connected to both a mapped subnet and a mapped Wi-Fi access point, the Wi-Fi access point determines the emergency address, and new access points can take longer to appear than IPs or subnets[^59]. When a caller's location cannot be determined from trusted IPs, RingCentral says the Nomadic 911 call reaches the National Emergency Call Center rather than the local PSAP[^56].

### Rollback
Suggested rollback: remove the network identifiers from the admin center and contact support to disable emergency services on the PBX.

**Fixed registered address + RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Validate emergency addresses and geo codes via the Teams admin center map search[^44]. Assign an emergency call routing policy to the user or site, ensuring the online voice route matches 911 without a leading plus[^46][^48][^47][^49]. Configure optional security desk notifications under the emergency calling policy[^51]. Calls run over Direct Routing, as companion mode places no calls[^3].

### Verify
Verify the user has an assigned emergency call routing policy[^46] and that unscreened or fallback calls resolve to the registered emergency address[^50].

### Rollback
Suggested rollback: unassign the emergency call routing policy from the user.

**Location follows client + RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Contact RingCentral support to activate Nomadic 911 and associate users with the provisioned PBX[^55][^54]. Note that dynamic emergency call routing for Direct Routing users is supported only in the United States, and in Canada with national screening[^45]. Configure trusted IPs, network sites, subnets, emergency addresses, and Wi-Fi access points in the Teams admin center Locations pages[^57][^44]. Ensure voice routes match 911 without a plus[^49].

### Verify
Confirm that the RingCentral Services list displays "RingCentral PBX with E911 PBX 3" (labels from RingCentral's Cloud PBX documentation) with an Emergency trunk configured[^58]. Verify that a client connected to both a subnet and a Wi-Fi access point resolves using the Wi-Fi access point's address[^59], and that unmapped network locations fall back to the National Emergency Call Center[^56].

### Rollback
Suggested rollback: remove the subnet and Wi-Fi mappings in the admin center and submit a support ticket to disable emergency features.

## Step 10: Perform validation calls

**RingCentral embedded app inside Teams**

### Do
Have pilot users place outbound PSTN calls, receive inbound calls, test unified contact search, and send an SMS from the embedded app to verify functionality[^31]. Verify that click-to-dial launches the desktop plugin and displays active call controls[^39].

### Verify
Suggested check: confirm two-way audio on an external call and verify transmission and delivery within the embedded app interface.

### Rollback
Suggested rollback: unassign the user from the app setup policy to revert to the standard interface.

**RingCentral as the Direct Routing provider**

### Do
Execute Microsoft's Direct Routing post-configuration checklist: validate inbound and outbound PSTN calling, verify emergency calling if configured, and confirm voice routing policies are assigned correctly[^26]. If call routing fails, escalate to RingCentral first, because Microsoft supports Direct Routing only with certified SBCs and directs support boundaries to the SBC vendor first[^8].

### Verify
Suggested check: place test inbound and outbound PSTN calls through the dial pad and confirm call records register in tenant analytics.

### Rollback
To remove a user with a failed connection, reset the integration status with Disconnect under Microsoft Teams Integration[^9].

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Validate inbound and outbound PSTN calling on the native Teams dial pad according to Microsoft's Direct Routing checklist[^26]. Open the embedded companion app and test sending an SMS, accessing fax, and viewing call history[^3].

### Verify
Verify that Direct Routing status displays Connected, enabling companion mode[^2], and confirm native calling functions alongside companion features[^26][^3].

### Rollback
Reset the user connection with Disconnect under Microsoft Teams Integration[^9] and remove the app setup policy in Teams admin center[^42].

## Step 11: Clean up elevated roles and tenant objects

**RingCentral embedded app inside Teams**

### Do
Revoke temporary elevated administrator privileges, such as Global Admin or the combination of Privileged Roles Admin, User Admin, Teams Admin, and Application Admin[^36].

### Verify
Suggested check: confirm in the directory admin center that temporary roles have expired or been revoked.

**RingCentral as the Direct Routing provider**

### Do
Revoke Global Admin from the connecting administrator account: once the Direct Routing connection is established, the Global Admin role is no longer required to maintain it and can be revoked[^12]. Retain the Teams Administrator role for ongoing day-to-day user enablement and management[^16][^22]. Setting up RingCentral Direct Routing needs 4 spare Microsoft end-user licenses with Teams phone capability, used temporarily to verify and create SBC domains and returned after setup[^11].

### Verify
Once the Direct Routing connection is established, the Global Admin role is no longer required to maintain it and can be revoked[^12]. Setting up RingCentral Direct Routing needs 4 spare Microsoft end-user licenses with Teams phone capability, used temporarily to verify and create SBC domains and returned after setup[^11].

**RingCentral Direct Routing plus the embedded app in companion mode**

### Do
Revoke the Global Admin role from the setup administrator account, as it is not needed to maintain the connection[^12]. Retain Teams Administrator for day-to-day administration[^16][^22]. Setting up RingCentral Direct Routing needs 4 spare Microsoft end-user licenses with Teams phone capability, used temporarily to verify and create SBC domains and returned after setup[^11]. Remove temporary embedded app installation roles[^36].

### Verify
Once the Direct Routing connection is established, the Global Admin role is no longer required to maintain it and can be revoked[^12]. Setting up RingCentral Direct Routing needs 4 spare Microsoft end-user licenses with Teams phone capability, used temporarily to verify and create SBC domains and returned after setup[^11].

## Applicability

Applies to: RingCentral Cloud PBX for Microsoft Teams, RingCentral for Microsoft Teams embedded app, RingCentral RingEX Direct Routing for Microsoft Teams, Microsoft Teams Phone Direct Routing, Microsoft Teams Phone, and RingCentral app. Deployments: multi-tenant. Sources checked 2026-09-25. RingCentral Direct Routing requires a RingEX Core, Advanced, or Ultra plan, or a legacy Standard, Premium, or Ultimate plan[^21]. The embedded app supports Windows 10 or later and macOS 10.15 Catalina or later, while Windows 7, 8, and 8.1 and macOS 10.13 and 10.14 are not supported[^38]. Direct Routing dynamic emergency call routing applies only to users in the United States, and in Canada with national screening[^45].

## What remains uncertain

The exact click path within the RingCentral Admin Portal for completing the Direct Routing OAuth tenant connection is not covered by the sources below. A tenant-level teardown procedure to fully remove RingCentral SBC subdomains, voice routes, and routing policies from Microsoft 365 is not covered by the sources below. RingCentral client uninstallation procedures for the desktop plugin are not covered by the sources below. Whether an E5 license SKU includes Teams Phone without separate add-on purchasing is not covered by the sources below. Emergency calling behavior for the embedded app outside of the United States is not covered by the sources below.

## Sources

[^1]: RingCentral says Cloud PBX 1.0 for Microsoft Teams will be retired and customers must migrate to RingCentral native Direct Routing. Source: [Setting up Nomadic 911 in RingCentral Cloud PBX for Microsoft Teams](https://support.ringcentral.com/article-v2/Setting-up-Nomadic-911-in-RingCentral-Cloud-PBX-for-Microsoft-Teams.html?brand=RingCentral&product=RingEX&language=en_US), Important notes. Checked 2026-09-25.
[^2]: Since embedded-app releases 25.1.30 and 25.2.10 (2025), companion mode appears only for users whose Direct Routing status is Connected. Source: [RingCentral for Microsoft Teams - Embedded App release notes](https://support.ringcentral.com/release-notes/integrations/rc-for-microsoft-teams.html), Version 25.1.30 (March 2025); Version 25.2.10 (May 2025). Checked 2026-09-25.
[^3]: When Direct Routing 2.0 is enabled, the embedded app hides its calling features and runs in companion mode, offering fax, text messaging and call-history management while calls are made in Teams, and no desktop plugin is needed. Source: [RingCentral's next generation integration for the Microsoft Teams desktop and web app](https://support.ringcentral.com/article-v2/RingCentral-s-next-generation-integration-for-the-Microsoft-Teams-desktop-and-web-app.html?brand=RingCentral&product=RingEX&language=en_US), Companion mode section. Checked 2026-09-25.
[^4]: Direct Routing release 25.1 added an account-level resync between RingCentral and Azure. Source: [Microsoft Teams - Direct Routing Release Notes](https://support.ringcentral.com/release-notes/integrations/microsoft-teams-direct-routing.html), Version 25.1 (March 24, 2025). Checked 2026-09-25.
[^5]: RingCentral says Direct Routing 2.0 activation emails cannot be turned off when users are set up individually, for compliance reasons. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: Can activation emails be disabled?. Checked 2026-09-25.
[^6]: RingCentral accepts TEAMS1, TEAMS_GOV, TEAMS_FREE, TEAMS_AR_GCCHIGH and TeamsEss as alternative licence types for the spare setup licences. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: What Microsoft licenses are required for Direct Routing setup?. Checked 2026-09-25.
[^7]: Direct Routing BYOC support became available in Controlled Availability in RingCentral release 25.1. Source: [Microsoft Teams - Direct Routing Release Notes](https://support.ringcentral.com/release-notes/integrations/microsoft-teams-direct-routing.html), Version 25.1 (March 24, 2025). Checked 2026-09-25.
[^8]: Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used, and support issues go to the SBC vendor first. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Support boundaries. Checked 2026-09-25.
[^9]: To remove a user whose Microsoft Teams connection failed, first reset the integration status with Disconnect under Microsoft Teams Integration, after which the user can be deleted. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: How do I remove a user with failed Microsoft Teams connection?. Checked 2026-09-25.
[^10]: Users still active in both RingCentral and Microsoft after moving to Direct Routing receive two notifications for each incoming call. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: Why do users receive duplicate incoming calls after Cloud PBX migration?. Checked 2026-09-25.
[^11]: Setting up RingCentral Direct Routing needs four spare Microsoft end-user licences with Teams phone capability, used temporarily to verify and create SBC domains and returned after setup. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: What Microsoft licenses are required for Direct Routing setup?. Checked 2026-09-25.
[^12]: Once the Direct Routing connection is established, the Global Admin role is no longer required to maintain it and can be revoked. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: Can Global Admin permissions be revoked after setup?. Checked 2026-09-25.
[^13]: Microsoft states that Direct Routing requires a Teams Phone licence. Source: [Microsoft Teams add-on licenses](https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/microsoft-teams-add-on-licensing), Teams Phone with PSTN connectivity licenses > Teams Phone with a separate PSTN connectivity option > Direct Routing bullet. Checked 2026-09-25.
[^14]: Direct Routing is not supported when Teams is in Islands mode. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Licensing requirements, Note. Checked 2026-09-25.
[^15]: Direct Routing release 25.1 lets admins manage notification preferences for Direct Routing enablement. Source: [Microsoft Teams - Direct Routing Release Notes](https://support.ringcentral.com/release-notes/integrations/microsoft-teams-direct-routing.html), Version 25.1 (March 24, 2025). Checked 2026-09-25.
[^16]: The RingCentral Direct Routing OAuth setup requires a Microsoft 365 Global Admin; after initial setup the Teams Administrator role is enough for ongoing management and adding users. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: What Microsoft 365 permissions are needed for Direct Routing setup?. Checked 2026-09-25.
[^17]: The Direct Routing OAuth connection registers and verifies SBC subdomains in the Microsoft tenant through the Graph API and links voice routing policies to voice routes with PSTN usage records. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: domain updates during OAuth setup. Checked 2026-09-25.
[^18]: When a Direct Routing user is offline in Teams, Teams voicemail answers the queue call and returns answered, which stops the queue from escalating; RingCentral's remedies are to disable Teams voicemail or enable presence sync so offline users are skipped. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ on call queue routing when users are offline. Checked 2026-09-25.
[^19]: Direct Routing release 24.1 (4 March 2024) added setup support for Microsoft PIM-enabled admins and Azure Active Directory authentication as an alternative to OAuth. Source: [Microsoft Teams - Direct Routing Release Notes](https://support.ringcentral.com/release-notes/integrations/microsoft-teams-direct-routing.html), Version 24.1 (March 4, 2024). Checked 2026-09-25.
[^20]: For RingCentral call queues serving Direct Routing users, RingCentral says to set the queue's phone number type to Voice only, or calls can go to voicemail instead of the queue. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ on call queue phone number type. Checked 2026-09-25.
[^21]: RingCentral Direct Routing for Teams requires a RingEX Core, Advanced or Ultra plan, or a legacy Standard, Premium or Ultimate plan. Source: [Setting up Direct Routing in RingCentral and Microsoft Teams](https://support.ringcentral.com/article-v2/Enabling-direct-routing-in-RingCentral-and-Microsoft-Teams.html?brand=RingCentral&product=RingEX&language=en_US), Prerequisites, RingCentral licensing. Checked 2026-09-25.
[^22]: Since Direct Routing release 25.1 (24 March 2025), an admin with Teams Administrator permissions can enable end users for Direct Routing, replacing an earlier requirement for three combined permission types. Source: [Microsoft Teams - Direct Routing Release Notes](https://support.ringcentral.com/release-notes/integrations/microsoft-teams-direct-routing.html), Version 25.1 (March 24, 2025). Checked 2026-09-25.
[^23]: RingCentral states that each Teams end user on Direct Routing must be assigned the applicable Microsoft licensing for phone calls. Source: [Setting up Direct Routing in RingCentral and Microsoft Teams](https://support.ringcentral.com/article-v2/Enabling-direct-routing-in-RingCentral-and-Microsoft-Teams.html?brand=RingCentral&product=RingEX&language=en_US), Prerequisites, Microsoft 365 licensing. Checked 2026-09-25.
[^24]: New Direct Routing users are enabled by turning on the MS Teams Connection toggle for the user in the Admin Portal User List; the migration tool is only for moving from Cloud PBX 1.0. Source: [RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting](https://support.ringcentral.com/article-v2/Troubleshooting-RingCentral-for-Teams-direct-routing-issues.html?brand=RingCentral&product=RingEX&language=en_US), FAQ: Do I need the migration tool to set up new Direct Routing users?. Checked 2026-09-25.
[^25]: Direct Routing requires users to be homed online in Microsoft 365. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Infrastructure requirements table, User registrar row. Checked 2026-09-25.
[^26]: Microsoft's post-configuration checklist for Direct Routing includes validating inbound and outbound PSTN calling, verifying emergency calling if configured, and confirming voice routing policies are assigned correctly. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Verify your deployment. Checked 2026-09-25.
[^27]: Direct Routing release 24.4 (16 December 2024) lets admins choose whether a user's voicemail is delivered in Microsoft Teams or in the RingCentral app. Source: [Microsoft Teams - Direct Routing Release Notes](https://support.ringcentral.com/release-notes/integrations/microsoft-teams-direct-routing.html), Version 24.4 (December 16, 2024). Checked 2026-09-25.
[^28]: RingCentral describes its Direct Routing-as-a-Service as enabling Teams telephony without in-house technical expertise or on-premises infrastructure. Source: [Microsoft Teams Direct Routing: A helpful guide](https://www.ringcentral.com/us/en/blog/microsoft-teams-not-all-direct-routing-integrations-are-equal/), section on Direct Routing-as-a-Service. Checked 2026-09-25.
[^29]: Accounts with more than 15,000 users are directed to install the embedded app from the Teams admin center rather than from the RingCentral Admin Portal. Source: [RingCentral for Teams 2.0 integration using OAuth](https://support.ringcentral.com/article-v2/Using-the-Microsoft-Team-admin-experience.html?brand=RingCentral&product=RingEX&language=en_US&pills-nav=oauth), Accounts over 15,000 users. Checked 2026-09-25.
[^30]: Emergency calls placed from the embedded app travel over RingCentral rather than Teams Phone, so they probably depend on the user's RingCentral emergency response location, not on Teams emergency policies or network locations (inferred). Source: [RingCentral for Microsoft Teams - Embedded App release notes](https://support.ringcentral.com/release-notes/integrations/rc-for-microsoft-teams.html), Version 23.3.10 read with the desktop-plugin call path. Checked 2026-09-25.
[^31]: The RingCentral embedded app in Teams provides calling, call-queue management, unified contact search, SMS and fax, and missed-call, text and voicemail notifications. Source: [RingCentral's next generation integration for the Microsoft Teams desktop and web app](https://support.ringcentral.com/article-v2/RingCentral-s-next-generation-integration-for-the-Microsoft-Teams-desktop-and-web-app.html?brand=RingCentral&product=RingEX&language=en_US), introduction and features. Checked 2026-09-25.
[^32]: RingCentral lists Microsoft 365 Enterprise E1, E3 and E5, Business Standard and Business Premium, and Frontline F1 and F3 as supported licences for the embedded app. Source: [RingCentral's next generation integration for the Microsoft Teams desktop and web app](https://support.ringcentral.com/article-v2/RingCentral-s-next-generation-integration-for-the-Microsoft-Teams-desktop-and-web-app.html?brand=RingCentral&product=RingEX&language=en_US), Requirements, Microsoft 365 licenses. Checked 2026-09-25.
[^33]: Users do not need to sign in to the RingCentral mobile app to make and receive calls from the Teams embedded app. Source: [RingCentral embedded app for Microsoft Teams FAQ](https://support.ringcentral.com/article-v2/RingCentral-embedded-app-for-Microsoft-Teams-FAQ.html?brand=RingCentral&product=RingEX&language=en_US), FAQ on mobile app sign-in. Checked 2026-09-25.
[^34]: Because the embedded app places calls through the RingCentral desktop plugin rather than Teams Phone, a Teams Phone licence is probably not needed for embedded-app calling (inferred). Source: [RingCentral's next generation integration for the Microsoft Teams desktop and web app](https://support.ringcentral.com/article-v2/RingCentral-s-next-generation-integration-for-the-Microsoft-Teams-desktop-and-web-app.html?brand=RingCentral&product=RingEX&language=en_US), Requirements and Making calls sections, read together. Checked 2026-09-25.
[^35]: Embedded-app release 23.3.10 (12 July 2023) added Nomadic ERL support to RingCentral for Microsoft Teams. Source: [RingCentral for Microsoft Teams - Embedded App release notes](https://support.ringcentral.com/release-notes/integrations/rc-for-microsoft-teams.html), Version 23.3.10 (July 12, 2023). Checked 2026-09-25.
[^36]: Installing the embedded app via OAuth needs RingCentral Super Admin and User Admin, and on the Microsoft side either Global Admin or the combination of Privileged Roles Admin, User Admin, Teams Admin and Application Admin. Source: [RingCentral for Teams 2.0 integration using OAuth](https://support.ringcentral.com/article-v2/Using-the-Microsoft-Team-admin-experience.html?brand=RingCentral&product=RingEX&language=en_US&pills-nav=oauth), Required administrator roles. Checked 2026-09-25.
[^37]: The embedded app OAuth connection is made in the Admin Portal under More > Account Settings > Microsoft Teams > Embedded App > Connect via OAuth, signing in as a Microsoft 365 admin and consenting on behalf of the organisation, then choosing to install for all, multiple or a single user. Source: [RingCentral for Teams 2.0 integration using OAuth](https://support.ringcentral.com/article-v2/Using-the-Microsoft-Team-admin-experience.html?brand=RingCentral&product=RingEX&language=en_US&pills-nav=oauth), OAuth connection steps 1-9; Installation options. Checked 2026-09-25.
[^38]: The embedded app's desktop side supports Windows 10 or later and macOS 10.15 Catalina or later; Windows 7, 8 and 8.1 and macOS 10.13 and 10.14 are not supported. Source: [RingCentral's next generation integration for the Microsoft Teams desktop and web app](https://support.ringcentral.com/article-v2/RingCentral-s-next-generation-integration-for-the-Microsoft-Teams-desktop-and-web-app.html?brand=RingCentral&product=RingEX&language=en_US), Requirements, Operating systems. Checked 2026-09-25.
[^39]: The embedded app requires the Microsoft Teams app plus the RingCentral desktop plugin, which shows active call controls when a call is placed. Source: [RingCentral's next generation integration for the Microsoft Teams desktop and web app](https://support.ringcentral.com/article-v2/RingCentral-s-next-generation-integration-for-the-Microsoft-Teams-desktop-and-web-app.html?brand=RingCentral&product=RingEX&language=en_US), Prerequisites; Making calls. Checked 2026-09-25.
[^40]: Since embedded-app release 24.1.10 (20 January 2024), admins are notified by email and in the Admin Portal when a new desktop plugin version is available. Source: [RingCentral for Microsoft Teams - Embedded App release notes](https://support.ringcentral.com/release-notes/integrations/rc-for-microsoft-teams.html), Version 24.1.10 (January 20, 2024). Checked 2026-09-25.
[^41]: Managing the policies that install the embedded app from the Teams admin center needs Global Administrator or Privileged Roles Administrator, plus Teams Administrator. Source: [Installing the RingCentral embedded app from the Teams admin center](https://support.ringcentral.com/article-v2/Install-RingCentral-for-Teams-2-0-from-Microsoft-Admin-Center.html?brand=RingCentral&product=RingEX&language=en_US), Required admin role. Checked 2026-09-25.
[^42]: To install the embedded app from the Teams admin center, create a setup policy under Teams apps > Setup policies, add the RingCentral app (optionally pinned), save, then assign users or groups through Manage users > Assign users. Source: [Installing the RingCentral embedded app from the Teams admin center](https://support.ringcentral.com/article-v2/Install-RingCentral-for-Teams-2-0-from-Microsoft-Admin-Center.html?brand=RingCentral&product=RingEX&language=en_US), Creating the setup policy, steps 1-8; Assigning users, steps 1-5. Checked 2026-09-25.
[^43]: Before installing the embedded app, the user principal name and email address must match between each user's Microsoft and RingCentral accounts, or chat notifications and personal contacts will not display. Source: [RingCentral for Teams 2.0 integration using OAuth](https://support.ringcentral.com/article-v2/Using-the-Microsoft-Team-admin-experience.html?brand=RingCentral&product=RingEX&language=en_US&pills-nav=oauth), Important provisioning note. Checked 2026-09-25.
[^44]: An emergency address must be validated before it can be assigned to a user or network identifier, and it needs a geo code to be assigned to a network identifier for dynamic emergency calling; addresses created with the Teams admin center map search get both automatically. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Emergency address validation; Emergency address geo codes. Checked 2026-09-25.
[^45]: For Direct Routing users, dynamic location for routing emergency calls is supported only in the United States, and in Canada with all calls screened nationally before transfer to the PSAP. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Dynamic emergency calling for Direct Routing. Checked 2026-09-25.
[^46]: For Direct Routing, emergency numbers and their routing are defined in a Teams emergency call routing policy, which can be assigned to a user, a network site or both, and the site policy takes precedence when the client is at a site that has one. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call enablement for Direct Routing. Checked 2026-09-25.
[^47]: The Direct Routing emergency call routing policy references an online PSTN usage, and there must be an online voice route for the emergency dial string. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call routing for Direct Routing. Checked 2026-09-25.
[^48]: If the Teams client cannot obtain an emergency call routing policy, the Direct Routing user is not enabled for emergency calling. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call enablement for Direct Routing, third bullet. Checked 2026-09-25.
[^49]: Teams clients no longer prepend a plus sign to emergency numbers, so Direct Routing voice route patterns must match 911 without a leading plus. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call routing for Direct Routing, Note. Checked 2026-09-25.
[^50]: If a US Direct Routing user's Teams client does not dynamically acquire a US emergency address, the registered emergency address is used and the call is screened to determine whether an updated address is needed before connecting to a PSAP. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Dynamic emergency calling for Direct Routing, second bullet. Checked 2026-09-25.
[^51]: Security desk notifications for emergency calls are available with Direct Routing and are governed by the Teams emergency calling policy. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Security desk notifications. Checked 2026-09-25.
[^52]: A RingCentral user's emergency response location is set in the RingCentral desktop app under Settings > Phone > Emergency response location > Manage, and cannot be set in the web or mobile app. Source: [Setting and updating your emergency response location](https://support.ringcentral.com/article-v2/Setting-and-updating-your-Emergency-response-location.html?brand=RingCentral&product=RingEX&language=en_US&pills-nav=desktop_%26_web), Desktop and web tab, update steps and limitations. Checked 2026-09-25.
[^53]: RingCentral's Direct Routing datasheet states that RingCentral provides and hosts the SBC, so the customer does not deploy SBC hardware. Source: [RingCentral datasheet: Cloud PBX for Microsoft Teams: Direct Routing](https://assets.ringcentral.com/us/datasheet/cloud-pbx-microsoft-teams-direct-routing.pdf), datasheet body; exact page not recoverable from encoded PDF text. Checked 2026-09-25.
[^54]: Direct Routing release 23.1 (9 March 2023) introduced Nomadic 911, which sends emergency calls through RingCentral using Teams location settings. Source: [Microsoft Teams - Direct Routing Release Notes](https://support.ringcentral.com/release-notes/integrations/microsoft-teams-direct-routing.html), Version 23.1 (March 9, 2023). Checked 2026-09-25.
[^55]: Nomadic 911 for Teams Direct Routing is enabled by contacting RingCentral support, and every Nomadic 911 user must be associated with the provisioned PBX. Source: [Setting up Nomadic 911 in RingCentral Cloud PBX for Microsoft Teams](https://support.ringcentral.com/article-v2/Setting-up-Nomadic-911-in-RingCentral-Cloud-PBX-for-Microsoft-Teams.html?brand=RingCentral&product=RingEX&language=en_US), Prerequisites. Checked 2026-09-25.
[^56]: When a caller's location cannot be determined from trusted IPs, RingCentral says the Nomadic 911 call reaches the National Emergency Call Center rather than the local PSAP. Source: [Setting up Nomadic 911 in RingCentral Cloud PBX for Microsoft Teams](https://support.ringcentral.com/article-v2/Setting-up-Nomadic-911-in-RingCentral-Cloud-PBX-for-Microsoft-Teams.html?brand=RingCentral&product=RingEX&language=en_US), Emergency address fallback. Checked 2026-09-25.
[^57]: RingCentral's Nomadic 911 setup has admins configure trusted IPs, network sites and subnets, emergency addresses and places, and Wi-Fi access points in the Teams admin center Locations pages. Source: [Setting up Nomadic 911 in RingCentral Cloud PBX for Microsoft Teams](https://support.ringcentral.com/article-v2/Setting-up-Nomadic-911-in-RingCentral-Cloud-PBX-for-Microsoft-Teams.html?brand=RingCentral&product=RingEX&language=en_US), Teams admin center setup. Checked 2026-09-25.
[^58]: Once Nomadic 911 is enabled, the RingCentral Services list shows 'RingCentral PBX with E911 PBX 3' with the note that it has an Emergency trunk configured, and users show that service in the Users column. Source: [Setting up Nomadic 911 in RingCentral Cloud PBX for Microsoft Teams](https://support.ringcentral.com/article-v2/Setting-up-Nomadic-911-in-RingCentral-Cloud-PBX-for-Microsoft-Teams.html?brand=RingCentral&product=RingEX&language=en_US), RingCentral admin portal verification. Checked 2026-09-25.
[^59]: When a user is connected to both a mapped subnet and a mapped Wi-Fi access point, the Wi-Fi access point determines the emergency address, and new access points can take longer to appear than IPs or subnets. Source: [Setting up Nomadic 911 in RingCentral Cloud PBX for Microsoft Teams](https://support.ringcentral.com/article-v2/Setting-up-Nomadic-911-in-RingCentral-Cloud-PBX-for-Microsoft-Teams.html?brand=RingCentral&product=RingEX&language=en_US), Emergency address fallback; Important notes. Checked 2026-09-25.
[^60]: Teams Phone is a separate add-on licence; the Teams Phone Standard licence provides Teams Phone alone, and PSTN connectivity must be chosen in addition for external calls. Source: [Microsoft Teams add-on licenses](https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/microsoft-teams-add-on-licensing), Teams Phone with PSTN connectivity licenses, second paragraph. Checked 2026-09-25.
[^61]: Teams Phone has four PSTN connectivity models: Microsoft Teams Calling Plan, Operator Connect, Teams Phone Mobile and Direct Routing. Source: [PSTN connectivity options](https://learn.microsoft.com/en-us/microsoftteams/pstn-connectivity), PSTN connectivity options, bulleted highlights. Checked 2026-09-24.
[^62]: Direct Routing differs from Calling Plans in that it requires a contract with a third-party PSTN provider plus a certified Session Border Controller procured and managed by the customer, an integrator or a DRaaS provider. Source: [PSTN connectivity options](https://learn.microsoft.com/en-us/microsoftteams/pstn-connectivity), PSTN connectivity options > Direct Routing bullet. Checked 2026-09-24.
[^63]: Enabling auto attendant and call queue services requires at least one Teams Phone license in the tenant. Source: [Reference - Voice applications prerequisites and licensing - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/aa-cq-reference-prerequisites-licensing), Licensing > Base licensing > Auto Attendant and Call Queue. Checked 2026-09-24.