The decision in one sentence
If you have predictable call volumes, want fast deployment, and don’t have strict carrier or compliance constraints — Teams Phone with Microsoft Calling Plans is the simpler answer. If you have specific carrier requirements, complex compliance, or international call patterns where you need to control quality and cost — Direct Routing with a session border controller (SBC) is the right call. The Saudi context tilts more enterprises toward Direct Routing than the global average.
What Teams Phone Calling Plans actually give you
Microsoft sells Teams Phone in two flavours: Calling Plans (Microsoft is your carrier) and Direct Routing (you bring your own carrier). With Calling Plans, you license per-user, get a Microsoft-issued number range, and skip all the carrier integration work. Domestic and international minutes are bundled per the plan tier.
The advantages are speed and simplicity. A 200-user organisation can be live on Teams Phone Calling Plans in two to four weeks of project work. There’s no SBC to size, no carrier contracts to manage, no number-porting saga across STC, Mobily, or Salam. For organisations whose telephony pattern looks like “knowledge workers making and receiving calls, mostly within KSA, modest international call volume”, this is often the right answer.
The trade-offs: limited carrier choice (Microsoft routes calls through its own infrastructure), less control over quality of service for specific destinations, and licensing costs that can exceed Direct Routing once you factor in international minute consumption.
What Direct Routing actually gives you
Direct Routing means Teams becomes the user-facing app, but the actual telephony goes through a session border controller (SBC) you operate, connecting Teams to a carrier of your choice. AudioCodes, Ribbon, and Oracle ACME are the dominant SBC vendors in this space.
What you get in exchange for the additional setup complexity: full control over carrier choice, ability to route calls through whichever Saudi carrier offers the best terms for your call patterns, fine-grained call-quality control, and explicit compliance with recording obligations. You can also keep your existing carrier contracts and existing number ranges with no porting required — just update the routing configuration.
The trade-offs: longer setup (typically six to twelve weeks), need for SBC sizing and high-availability design, and ongoing operational responsibility for the SBC infrastructure (or an MSP relationship to manage it).
Cost comparison — KSA-specific
Take a 500-user enterprise with mixed domestic and international call patterns:
Teams Phone Calling Plan (Domestic + International): roughly SAR 90 per user per month for unlimited domestic and a 600-minute international pool. Total monthly: ~SAR 45,000.
Direct Routing equivalent: Teams Phone Standard licence (~SAR 30/user/month) + carrier minutes through STC Business or Mobily (typically half the international rate) + SBC capex (~SAR 80,000-150,000 one-time) + SBC operational support. Total monthly after amortisation: ~SAR 35,000-40,000.
For organisations with high international minute volume — common in Saudi enterprises with offshore relationships, GCC trade, or international supplier bases — Direct Routing is typically cheaper at scale. For purely domestic call patterns, the gap narrows.
Compliance and recording (the SAMA factor)
Saudi banks and SAMA-regulated entities face explicit call-recording obligations for trader communications, customer service, and certain transaction flows. Teams Phone Calling Plans support compliance recording through Microsoft-licensed integrations (typically Verint, NICE, or RedBox). Direct Routing offers more flexibility — you can integrate with a wider range of recording solutions, including those operating fully on-premise or in Saudi-region cloud.
For SAMA-regulated organisations, Direct Routing usually wins on compliance grounds. The data residency and recording-control story is more defensible to regulators when you can point to specific infrastructure components rather than to “Microsoft’s cloud”.
Survivability under network failure
What happens when your internet link to Saudi Microsoft data centres is impaired? With Calling Plans, calls drop. With Direct Routing and a properly designed SBC, you can configure local survivability — calls continue routing through the SBC and the carrier even if the path to Microsoft’s cloud is degraded. For organisations operating in NEOM, the Red Sea Project, or other locations with less mature internet infrastructure, this matters.
The hybrid case — why most KSA enterprises end up here
The pattern we see most often in mid-to-large KSA enterprises is hybrid: Direct Routing for the main office and primary call patterns, with Teams Phone Calling Plans layered in for specific user segments (occasional callers, secondary offices, mobile-first workers). This balances cost, complexity, and operational simplicity.
Decision matrix
If your organisation has fewer than 100 users, predominantly domestic call patterns, no SAMA constraints, and a small IT team — Calling Plans. If you have more than 200 users, significant international volume, regulatory recording obligations, or operations across multiple KSA regions — Direct Routing. If you’re between those, build the cost model both ways and let the numbers decide.
For a written decision brief covering your specific organisation, book a Teams architecture session and we’ll deliver a one-page recommendation. Pair Microsoft Teams with unified communications, VoIP installation, and networking services for a coherent communications platform.
