Your staff already spend their day in Microsoft Teams. Chat, meetings, the lot. What surprisingly few businesses realise is that Teams can also be the phone system: real numbers, real inbound and outbound calls to the public network, reception queues, voicemail, the works, in the same app on the laptop and the mobile.

When it’s set up well, the separate phone platform (and its bill, and its maintenance contract) simply ceases to exist. The question is how you connect Teams to the actual phone network, and that’s where the options split.

The three ways in, and why Operator Connect usually wins

Microsoft will sell you its own calling plans: simple, but per-user pricing runs high and call rates aren’t negotiable. At the other extreme is Direct Routing, where your own session border controllers link Teams to a carrier: maximally flexible, and an infrastructure project with ongoing care and feeding that most businesses have no appetite for.

Operator Connect is the middle path Microsoft built after watching everyone struggle with the other two. Certified carriers plug directly into the Teams platform; you pick one, numbers appear in your Teams admin centre, and the carrier owns the telephony layer. Local numbers, local call rates, carrier-grade voice, no hardware. For most Australian SMEs it’s the sweet spot on cost, control and simplicity, and you keep your existing numbers by porting them across.

What it costs, roughly

Two components: a Microsoft licence for phone functionality per user (already included in some enterprise plans, an add-on for the rest) and the carrier’s calling plan on top. All up, for a typical 50-user business, it lands well under what a traditional PBX with lines and maintenance costs, and it scales per user rather than per hardware upgrade. Add what disappears (the PBX replacement cycle, the maintenance contract, the separate conferencing bill) and the comparison usually isn’t close.

Where it goes wrong

This is the part the licensing pages don’t mention. The businesses that come to us mid-mess have usually hit one of these:

• The porting trap. Moving your numbers into Operator Connect is a real carrier port, with all the classic failure modes: mismatched account records, numbers with EFTPOS or alarms silently attached, rejections that reset the clock. Get this wrong and the business is uncontactable, which rather undermines the shiny new phone system.
• Emergency addresses. Australian regulation requires accurate emergency service addresses on every number. It’s mandatory, it’s audited, and it’s routinely skipped by DIY setups.
• Call flows nobody designed. A PBX accumulates years of routing wisdom: the after-hours behaviour, the overflow rules, who rings when reception is busy. Recreating that in Teams takes deliberate design, not defaults. The gap is invisible until the first missed customer call.
• A network that can’t carry it. Voice in Teams rides your internet connection. If the upload is already saturated or quality-of-service was never configured, you’ve moved your phone system onto your most congested asset.

The sensible path

None of those problems are exotic. They’re the standard failure modes of any voice migration, wearing a Microsoft badge, and avoiding them is a matter of doing the boring work in the right order: audit the current numbers and what’s attached to them, verify the network can carry voice, design the call flows on paper, port with parallel running, then cut over. That end-to-end job is what we do, carrier-agnostic, including choosing which Operator Connect provider actually suits your call volumes and rates.

If Teams calling is on your roadmap, or your phone system’s next maintenance renewal is coming and you’re wondering if there should even be a next one, talk to us before you’re locked in for another term.