Direct Routing enables new enterprise voice options in Microsoft Teams

Today we are taking the next step for Enterprise Voice and announcing that Direct Routing will be joining Calling Plans as one of the options customers will have for Calling in Microsoft Teams.

 enterprise voice 3 - less white space.png


 We are targeting the end of Q2-2018 for general availability of this capability. To access the Direct Routing capability, customers will need to have Microsoft Teams and Phone System as part of Office 365.


What is Direct Routing?


Direct Routing is a capability of Phone System in Office 365 to help customers connect their SIP trunks to Microsoft Teams. In the simplest deployment model, customers start with SIP trunks from their telecommunications provider. Next, customers will use and configure a supported Session Border Controller (SBC) from one of our certified partners. Finally, they will connect their SBC to Microsoft Teams and Phone System.


direct routing 2.png


Besides the primary Direct Routing scenario, we anticipate customers will want to use this capability to integrate with other 3rd party voice applications. There are several additional scenarios:

Easy Transition to Calling in Teams. By integrating with an existing PBX, pilot users can be moved to Calling in Teams while users remain on their legacy PBX. Eventually all users can be easily transitioned to Calling in Teams. The call traffic between these users during the transition stay within the organization.

Telephony System Inter/Op. While users are being transitioned to Calling in Teams, Call Center agents can continue to use their application. Direct Routing enables both use cases to coexist. The call traffic between call center agents and Teams users stay within the organization.


Support for Analog Devices. If an organization decides to move to Calling in Teams but has analog devices such as elevator phones or overhead pagers, these devices can be connected to Teams and Phone System via Direct Routing. Call traffic between analog devices and Teams users stay within the organization.


Microsoft will certify select SBC vendors to insure they are compatible with our Direct Routing guidelines. We will start with AudioCodes, Ribbon Communications, and ThinkTel. Our plan is to continue to evaluate SBC vendors and certify as needed.

It’s important to note that Direct Routing is designed to work with Microsoft Teams. Customers using Skype for Business Online should continue to use Cloud Connector Edition (CCE) or connect via or a on-premises SFB Pool for their SIP trunk connection needs.

Getting started with Calling in Teams


If you are new to Teams, please review our quick start guide.  We also invite you to mark your calendars for March 22 for a Teams on Air episode with guest Nikolay Muravlyannikov, Sr. Program Manager where he will discuss Direct Routing in more detail.

New Contributor

Is there anything on the roadmap to remove the CCE requirement for SfBO?

Hi @patrick yore the CCE is still stays the solution to bring your carrier for SFBO users. Direct Routing works with Teams only. However, there is a clear migration path. If you use a supported SBC (AudioCodes or Ribbon) with the CCE you can pair the same SBC, which is paired to CCE, to the Teams backend and migrate users from SFBO to Teams. It is a matter deploying Teams client and changing the voice routing on SBC and in our Cloud. Once all users migrated you can decommission the CCE.

We will publish detailed migration guidance 

Occasional Visitor

Does Direct Routing still require a static IP address like CCE does? My company has a fast, low latency Internet connection (300 Mbps down / 30 Mbps up) but our ISP does not offer static IP addresses. This has prevented us from implementing SFBO voice via CCE.

Senior Member

As Microsoft announced end of support for SBCs by July 2018, what is the future plan? 


hi @Venkat Kantamneni, We will share more updates the last week of March.

Senior Member

Thank You Paul. Waiting for future direction from MS as we are moving onto O365...

New Contributor

This is great news as CCE is expensive and prohibiting adoption at the lower end of the market i.e sub 100

Hi, what about Cisco UCM and Teams connectivity? Will there be a possibility to port existing trunks from on-prem CUCM into Teams or we will need additional SBC to do that?

This is the best news since sliced bread! Been waiting for a solution in our country where Calling Plans are not available.

@Venkat Kantamneni I think you may be referring to SBC support for Exchange UM? I cant see MS dropping support for SBC's ever.

@Святослав Терлецький you'll need a supported SBC, and my guess is you won't see a Cisco one (you never know though!). This would mean that you would need a supported SBC to allow interworking between CUCM and MS Teams.

Hi @Святослав Терлецький we do certify SBCs which can interconnect Microsoft Phone System and CUCM or other systems

Occasional Visitor

Will we be able to take advantage of o365 voicemail with this change?


Alonzo Wilson

Occasional Visitor

We don't use SIP, but PRI lines instead. Is SIP a requirement or will be be able to just point our supported SBC to teams instead of our current on premise servers? 

Occasional Visitor

Hi will the connectivity between SBC and Teams Phone System be available through a Microsoft Peering on an ExpressRoute (i.e. with QoS) or just available via the internet as shown in the diagram?

@Mark Hood thank you for noticing. We certify the SBC, the trunk to that SBC can be SIP or PRI for Direct Routing it is doesn't matter

@Antony Millington we support both options: Express Route and internet. The IP addresses of the Direct Routing service already advertised in ER

Frequent Visitor

This is great news! What are the requirement from a licensing perspective?

E1/E3/E5 etc.

@Jonas Andersson the same as for SFB, either E3 + Cloud PBX add on or E5. That is it. 

Hi @Alonzo Wilson the voice mail for users on the service provided from the Cloud (a service in Azure) the same way as for Teams with Calling Plans

Hi, this is great news indeed. Is there a plan to introduce LBR in Phone System and/or Direct Calling? 

Hi @Sandeep Kulkarni LBR is on our roadmap with delivery by the end of the year. 

Regular Contributor

Will this support meeting audio conferencing - call in / dial out - as well?

@David Phillips yes we do support dial in dial out to/from conference using Microsoft PSTN Conferencing, which part of E5 or add on on to E3

Regular Contributor

@Nikolay Muravlyannikov sorry, let me clarify.  Will we be able to connect our on prem PBX to Teams and use that infrastructure for dial in / call out for meetings?

@David Phillips got the scenario, no you cannot use your own numbers for dial in and dial out for/from conferences, this requires the Microsoft PSTN Conferencing add on 

Occasional Visitor

What would be the specification/process to make a SIP tunk certified for Direct Routing ?

Hi @Oscar Novoa we don't certify the trunks, we certify the Session Border Controllers (ThinkTel also has an SBC which is being tested). You can connect any trunk if it works with the SBC.

Occasional Visitor

We have a CORE SBC (carrier class), and would like to know how to get it certified.


Today we have certified our trunk for Lync (and SFB). 

Hi @Oscar Novoa Core SBC do you refer to Ribbon/Sonus Core series?

Occasional Visitor

I refer to a group of  HUGE SBC’s (we are a carrier). 


We use Sansay. We got certified our trunks for Lync (and SFB) using this infrastructure.

Hi @Oscar Novoa Ribbon Core series are also huge and being used by big carriers :)  Back to the question, we don't work with Sansay. We will look to adding additional SBC vendors as needed. 

Occasional Visitor

How could we do something from our side ?

I mean, can we submit for testing our SBC and cooperate within the process?

Hi @Oscar Novoa our plan is to continue to evaluate SBC vendors and certify as needed.