When Microsoft Teams is already where your employees chat and meet, forcing them to use a separate app or desk phone for customer calls creates friction. Teams Direct Routing brings business calling into the Teams experience while giving your company more choice over carriers, phone numbers, call handling, and support.
Learning how to set up Teams Direct Routing is less about clicking through a Microsoft admin portal and more about making the right design decisions before you touch the configuration. A rushed setup can lead to one-way audio, failed emergency calling, confusing call routes, or a painful number port. A planned deployment gives employees a familiar calling experience without locking your business into a legacy phone provider.
What Teams Direct Routing Does
Teams Direct Routing connects Microsoft Teams Phone to the public telephone network through a certified Session Border Controller, commonly called an SBC. The SBC sits between Microsoft Teams and your phone carrier or cloud communications provider. It controls signaling, media traffic, security, number routing, and call policies.
This model is different from Microsoft Calling Plans, where Microsoft provides the calling service directly. Direct Routing lets a business keep existing phone numbers, use a preferred provider, support more advanced call flows, and often manage costs more predictably. It is particularly useful for organizations with multiple locations, contact center needs, compliance requirements, or existing carrier agreements.
The trade-off is that Direct Routing has more moving parts. You need the right Microsoft licensing, a compatible SBC arrangement, voice routing policies, and a provider that can support the deployment when something changes. For a small team with simple calling needs, Calling Plans may be enough. For a growing business that needs control and flexibility, Direct Routing is usually the stronger long-term option.
Before You Set Up Teams Direct Routing
Start with a short discovery process. Identify which users need external calling, which numbers must be ported, and whether each department needs its own caller ID, auto attendant, call queue, or business hours. This is also the time to document locations and emergency addresses. Emergency calling is not an item to handle after launch.
Confirm that every calling user has an eligible Microsoft license. In most cases, users need Teams Phone in addition to a qualifying Microsoft 365 license. Your exact licensing path depends on your Microsoft plan and whether Teams Phone is included, added separately, or bundled through your provider.
You also need an SBC. Some organizations buy, configure, and maintain their own certified SBC. That approach can make sense for large enterprises with dedicated voice engineers and complex infrastructure. Most small and mid-sized businesses are better served by a hosted Direct Routing provider that manages the SBC environment, carrier connectivity, security certificates, monitoring, and ongoing updates.
Finally, assess your network. Teams calling depends on stable internet service, adequate bandwidth, and sensible quality-of-service policies. If your office Wi-Fi drops calls today, Direct Routing will not fix that underlying issue. Test your connection, review firewall rules, and identify remote employees who may need wired connections or better home internet.
How to Set Up Teams Direct Routing Step by Step
Prepare your Microsoft 365 tenant
In the Teams admin center, make sure Teams Phone is assigned to each employee who will place or receive public phone calls. Confirm users are enabled for Teams and have the correct usage location. This setting matters because it affects licensing availability and emergency calling configuration.
Set up emergency locations before assigning phone numbers. For office-based staff, associate each number with the appropriate physical address. For remote and hybrid users, establish a process for keeping location information current. Emergency services requirements vary by location, but accurate address data protects employees and reduces compliance risk.
Connect a certified SBC
Your SBC must be configured to communicate with Microsoft Teams through Direct Routing. That includes a publicly resolvable fully qualified domain name, trusted TLS certificates, supported cipher settings, and the required SIP signaling configuration.
If you operate your own SBC, this is where deployments become technical. You will need to configure DNS, certificate renewal, SIP options, media bypass decisions, firewall rules, and high availability. A single SBC can create a point of failure, so businesses that cannot tolerate downtime should use redundant SBCs or a provider with geographic resiliency.
With a managed service, the provider handles the SBC connection and gives you the domain details needed to pair it in the Teams admin center. This reduces the internal workload, but you should still ask how redundancy, monitoring, failover, and support escalation work. Low monthly pricing is not a good deal if a carrier issue leaves your customer-facing team unable to answer calls.
Configure voice routing and dial plans
Voice routing tells Teams which calls should travel through which SBC and carrier path. Create a voice route that includes the appropriate phone number patterns, assign the route to a voice routing policy, and apply that policy to the correct users.
Dial plans determine how users enter numbers. A well-designed dial plan lets employees call naturally, whether they enter a 10-digit number, an extension, or a local number. Normalize these entries into E.164 format so Teams can route them consistently.
Keep policies simple at first. You may eventually need separate routing for international calls, executive users, contact center agents, or specific offices. But creating too many exceptions before launch makes troubleshooting harder. Start with the rules your business actually needs, then add complexity only when there is a clear operational reason.
Port or assign phone numbers
You can assign new direct inward dialing numbers, commonly called DIDs, or port existing numbers from your current carrier. Porting preserves the numbers customers already know, but it requires planning. Your provider will generally need a recent bill, a letter of authorization, account details, and a list of numbers to transfer.
Do not cancel your old service before the port is complete. That can cause number loss or delay. Keep the existing service active, confirm the port date, and schedule a validation window after the transfer. If you have toll-free numbers, fax lines, alarm panels, elevator phones, or analog devices, identify them early. Not every number or device belongs in the same migration plan.
After numbers are available, assign them to Teams users, auto attendants, call queues, or resource accounts. Test outbound caller ID as well. A sales representative should present the main business number or assigned direct number, not an unfamiliar carrier number that customers may ignore.
Build the call experience around real workflows
Direct Routing handles connectivity, but your call flow determines whether customers reach the right person. Configure auto attendants for your main number, business hours, holiday schedules, and basic department options. Use call queues for teams that answer shared calls, such as billing, scheduling, or customer support.
Avoid building a phone tree that sounds like a maze. Most growing businesses need a concise greeting, a few clear options, and an easy path to a live person. Define overflow rules for unanswered calls and decide where after-hours calls should go. Voicemail, an on-call employee, or a dedicated answering team may each be appropriate depending on the department.
Test before you announce the rollout
Run pilot calls with a small group before moving the whole organization. Test inbound and outbound calling, voicemail, transfers, hold, caller ID, call queues, auto attendants, emergency calling, and calls between Teams desktop, mobile, and desk devices.
Test from outside networks as well as inside the office. Have remote users place calls from their normal home environment. Check audio quality in common areas with Wi-Fi. Confirm that front-desk staff can handle transfers and that managers know how to access call history or reports.
Document issues by call type, user, time, and location. That detail helps your provider isolate whether the problem is a routing policy, an SBC setting, a network condition, or an endpoint issue. “Calls are bad” is difficult to diagnose. “Inbound calls to the main queue have one-way audio for remote users” is actionable.
Common Direct Routing Mistakes to Avoid
The most expensive mistakes are usually operational, not technical. Businesses underestimate number port timing, skip emergency address setup, and assume every legacy device can move to Teams without a replacement plan. Others assign licenses and numbers but never train employees on transfers, call queue behavior, mobile calling, or voicemail.
Another common issue is treating support as an optional add-on. Direct Routing spans Microsoft, the SBC, the carrier, your network, and user devices. When a call fails, your team needs a provider that will investigate the full path instead of sending you from one vendor to another. Skyretel’s managed approach is designed to reduce that handoff problem with live support and guided onboarding.
Make the First Day Feel Ordinary
The best Direct Routing rollout is not the one with the most complicated configuration. It is the one where employees arrive on Monday, make and receive calls in Teams, and customers keep reaching the same numbers without noticing a migration happened. Build for that outcome: keep the design practical, test the real call paths, and choose support that remains accountable after the port date.