If your team lives in Microsoft Teams all day, giving it real phone numbers is an obvious consolidation: one app for chat, meetings and now the main business line. Microsoft offers three doors into the phone network, and the pricing difference between them is large enough to fund a good deal of coffee. Here's the honest comparison we walk clients through.
First, the licence everyone needs
Whatever route you choose, users making external calls in Teams need Teams Phone licensing (included in E5, an add-on for Business plans). That turns Teams into a phone system; the three options below are purely about how calls reach the public network — and who bills you for them.
Microsoft Calling Plans: simplest, priciest
Microsoft sells numbers and minutes directly inside 365. Setup is a few clicks and there's no third party involved — genuinely the fastest start for a small, simple setup.
The trade-offs: per-user cost is the highest of the three, international rates are unremarkable, number management is basic, and porting complex estates into Microsoft can be slow. Fine for a five-person firm; expensive at fifty.
Operator Connect: the managed middle path
Operator Connect lets an approved carrier plug its network into your Teams tenant through Microsoft's own integration. You keep carrier pricing (usually well below Calling Plans), get proper porting and number management from a telecoms specialist, and admin stays inside the Teams admin centre.
It's the sweet spot for most SMEs: better rates and support than Microsoft direct, without running any infrastructure. The limitation is flexibility — you're within the operator's standard service, and advanced call flows or non-Teams endpoints aren't its game.
Direct Routing: maximum control and the best economics at scale
Direct Routing connects Teams to any SIP trunk via a certified Session Border Controller (SBC), hosted by your provider. It's the most flexible option: keep your existing trunks and rates, mix Teams with desk phones or a contact centre, build custom routing, and cover countries Operator Connect doesn't reach.
The SBC layer means there's genuine engineering involved — which is why it's typically delivered as a managed service. Per-user economics beat everything else from a few dozen users up, and it's the only option that lets analogue devices (door entry, alarms, DECT) live alongside Teams cleanly.
The decision in one honest table
How we'd summarise it after dozens of migrations:
- Under ~10 users, no legacy kit, simplicity above all → Microsoft Calling Plans
- 10-100 users, standard needs, want carrier pricing without infrastructure → Operator Connect
- Complex routing, mixed devices, contact centre, international, or 50+ users → Direct Routing
- Whichever you pick: port your numbers, don't buy new ones — continuity beats convenience
What a migration actually looks like
A typical Teams calling migration runs: licence check → number audit and porting plan → pilot group with real numbers → call-flow build (menus, queues, out-of-hours mirrored from the old system) → floor-by-floor cutover → old system decommissioned. Done in that order, users notice new features, not disruption.
We deliver all three models and will tell you plainly which fits — start with a Teams Phone conversation or get a full phone system comparison including non-Teams options, because Teams isn't always the right PBX for call-heavy front desks.
