Teams Phone in Australia when Calling Plans are not the fit: Operator Connect, Direct Routing or leave Teams for voice?

01Start with the split that causes most bad buying decisions

Teams Phone has two layers to think about. First, the Microsoft layer: users need the right Teams Phone entitlement, unless it is already included in their Microsoft 365 package. Microsoft’s licensing guidance is explicit that assigning calling capability starts with the Microsoft 365 user account and the correct Teams Phone licence path (Teams Phone licensing). Second, the PSTN layer: telephone numbers are not included with Teams Phone licensing, and Microsoft’s number management guidance says numbers are acquired separately through Calling Plans, Operator Connect, Teams Phone Mobile or Direct Routing (Get telephone numbers in Microsoft Teams).

That matters because a Teams voice project can fail for the wrong reason. Some organisations spend weeks comparing carriers without first checking whether they really want every voice user inside Teams. Others focus on Microsoft seat cost but underestimate the operational cost of number porting, emergency calling setup, handset replacement, SBC support, and who owns fault isolation when calls break. If you want the least costly and least painful result, decide the operating model first, then fit licensing and carrier choices around it.

A practical way to frame it is this: do you want Microsoft and a certified carrier to hide most telephony complexity from you, do you need custom voice routing and legacy integration, or do you mostly need business telephony that happens to coexist with Microsoft 365? If you answer that clearly, the shortlist gets much smaller.

• Keep Teams for voice only if users genuinely benefit from a single client for chat, meetings and PSTN calls.
• Treat numbers, carrier contracts, porting and support paths as separate from Microsoft user licensing.
• If your voice estate includes contact centre logic, analogue devices, branch survivability or legacy PBX tie-ins, test whether Teams is still the centre of gravity.
• If your real priority is reducing admin effort, favour managed PSTN models before custom ones.

02When Operator Connect is the default answer

Microsoft positions Operator Connect as the managed middle path. It lets a Microsoft-certified operator provide PSTN connectivity to Teams Phone, while admins work in the Teams admin centre. Microsoft’s planning guidance says it is a good fit when you want a managed PSTN solution without deploying and maintaining your own Session Border Controllers, or when you want to stay with an existing operator that offers Operator Connect for Teams Phone (Plan for Operator Connect).

This is usually the best option for Australian organisations that want Teams calling, do not need unusual call routing, and do not want to own SBCs, certificates, SIP interconnects or voice policy complexity. Microsoft’s configuration guidance also shows the operational model clearly: choose an operator in Teams admin centre, let the provider reserve or port numbers, then assign those numbers to users inside Teams (Configure Operator Connect, Get Operator Connect telephone numbers).

Operator Connect is strongest when your decision criteria are speed, supportability and a clean admin model. You still need Teams Phone licensing for users, but the carrier manages the PSTN side. You also avoid one of the biggest hidden costs of Direct Routing, ongoing ownership of the voice edge and the support split across SBC vendor, carrier and Microsoft.

The limits are just as important. Microsoft says you should evaluate providers on regional availability, phone number availability and porting support, service offerings and existing business relationships (Plan for Operator Connect). In practice, that means you must verify Australian number coverage, whether your exact ranges can be ported, what happens to fax or lift phones, and whether hunt groups or contact centre needs sit outside the Operator Connect scope.

• Choose Operator Connect if your top priority is low deployment friction.
• Use it when you want carrier-managed PSTN and Teams-native user administration.
• Avoid it if you need deep custom routing logic or non-standard telephony integration.
• Confirm Australian number portability and support response boundaries before signing.

03When Direct Routing is justified, and when it becomes self-inflicted complexity

Direct Routing exists for organisations that need control. Microsoft defines it as connecting your own telephony infrastructure to Teams Phone through a supported, customer-provided SBC (Plan Direct Routing). That opens the door to using your preferred carrier, integrating legacy estates, supporting more complex call routing, and handling scenarios that do not map neatly to Operator Connect.

The trade-off is visible in Microsoft’s own deployment sequence. Planning Direct Routing typically includes reviewing infrastructure and licensing, selecting a Microsoft-certified SBC, configuring networking, DNS, certificates and connectivity, connecting the SBC to Teams, then configuring voice routing and validating production calls (Plan Direct Routing). Microsoft also maintains a certified SBC list and says Direct Routing is supported only with certified devices (Session Border Controllers certified for Direct Routing, Configure Direct Routing).

So Direct Routing is not just a carrier choice. It is an operating model decision. You are taking responsibility for more moving parts: SBC platform choice, certificate lifecycle, SIP interoperability, firewall and DNS configuration, routing policy design and incident ownership. If your team has not run SIP estates before, the labour cost is usually larger than the line-item hardware or hosting cost.

There are good reasons to accept that burden. Direct Routing can be the right answer if you must preserve legacy PBX coexistence during migration, integrate analogue devices, or support branch continuity. Microsoft’s own documentation includes analogue device support through an ATA that is supported by the certified SBC vendor, and survivable branch appliance options for internet outage scenarios (Direct Routing analog devices, Direct Routing SBA). If those scenarios are real, Direct Routing can save a second redesign later.

• Use Direct Routing when you need custom routing, legacy coexistence or branch continuity features.
• Budget for design, certification, testing and ongoing operations, not just implementation.
• Do not pick it only to keep carrier choice if Operator Connect already gives that with less effort.
• Insist on a support map showing who owns SBC, carrier, Microsoft and internal admin issues.

04When leaving Teams for voice is the simpler commercial answer

This is the option many buyers skip too early. Microsoft’s PSTN guidance is clear that Teams Phone is flexible, but flexibility is not the same thing as necessity. If your users mainly need meetings, chat and document collaboration in Teams, but business voice is already handled well by another cloud telephony platform, forcing PSTN into Teams can add cost and support overlap without much user value (PSTN connectivity options).

Leaving Teams for voice can be simpler when your business phone platform already covers queues, recording, reporting, contact centre functions, mobile-first workflows or handset fleets better than Teams does for your use case. It can also be commercially cleaner if only a small subset of staff actually need deep Teams-native calling. In those cases, a separate hosted telephony service can reduce Microsoft add-on sprawl and keep the telephony contract with the provider that already owns numbers, call plans and support.

The key question is not whether Teams can do it. It is whether the business benefits enough from doing it inside Teams. If the answer is weak, you may be better off leaving Teams as the collaboration layer and integrating directories, calendars and presence where practical rather than buying, deploying and supporting a full Teams Phone estate.

This is especially true in organisations where telephony is operationally distinct from knowledge work. Frontline field teams, retail sites, warehouses and small branch offices often care more about dependable calling, simple device management and mobile workflows than about a unified Teams client. In that case, the voice platform decision belongs in the broader communications estate, not just the Microsoft tenancy.

• Ask whether users really need PSTN inside Teams, not whether IT prefers a single vendor.
• Compare the cost of Teams Phone licences plus PSTN plus migration effort against staying on a fit-for-purpose telephony platform.
• If contact centre or advanced telephony drives the requirement, evaluate that platform first and treat Teams integration as secondary.
• Avoid duplicate spend where users end up licensed in both ecosystems but only use one for calling.

05What to ask a provider before you choose

Most teams ask about call rates first. That is too late in the process. Microsoft’s own Operator Connect planning guidance highlights availability, numbers, porting and service offerings, while Direct Routing guidance highlights certified SBCs, networking and support boundaries (Plan for Operator Connect, Plan Direct Routing, Configure Direct Routing). Your vendor questions should reflect that.

Ask the Operator Connect provider or Direct Routing partner these questions: Which Australian number types and regions can you supply or port? What is the documented porting process and the realistic lead time? Which features are native, and which depend on another platform layer? Who handles emergency calling configuration and testing? What is the support path for failed inbound calls, poor audio, and number provisioning issues? If Direct Routing is proposed, which certified SBC is included, where is it hosted, who patches it, who renews certificates, and who owns outage response?

Also ask for the migration shape, not just the destination. Can you run a pilot with a subset of users and keep the old platform during cutover? Can you split users by business unit or site? Microsoft explicitly supports using more than one PSTN connectivity type within the same tenant, which means phased designs are possible when they reduce migration risk (PSTN connectivity options).

Finally, ask each provider to show the ongoing admin burden after go-live. A cheap proposal that leaves your Microsoft admin team, network team and service desk holding the operational complexity is not actually the cheaper proposal.

• Ask for a named support boundary matrix.
• Ask who owns number porting and rollback if a cutover fails.
• Ask for evidence that the proposed SBC is Microsoft-certified if Direct Routing is involved.
• Ask what features are unavailable or different in Australia.
• Ask for the first 90 days operating model, not just implementation steps.

06A practical selection path for Australian buyers

Use this sequence. First, segment users by actual voice need: heavy PSTN callers, queue-based workers, mobile-first field staff, knowledge workers who mostly live in meetings, and locations with legacy or analogue dependencies. Second, decide whether Teams-native calling is truly valuable for each segment. Third, prefer the least complex path that satisfies the hardest segment without forcing every other user onto the same model.

For many organisations, that means Operator Connect for office knowledge workers who want Teams-native calling, and a separate telephony platform for specialist or frontline scenarios. For some, it means Direct Routing temporarily, because there is legacy PBX coexistence or analogue equipment that cannot disappear in one move. For others, it means no Teams voice rollout at all, because the commercial and support case never becomes compelling enough.

If you need help working through that architecture and support trade-off, this is the sort of problem a plain technology consulting engagement or a focused telephony infrastructure service should solve. The work is not just implementation. It is choosing the model that creates the fewest contracts, the fewest operational handoffs, and the smallest chance of paying twice for calling.

The safest default is simple: if you want Teams calling and do not need unusual telephony behaviour, start with Operator Connect. If you need control, coexistence or specialised routing, justify Direct Routing explicitly. If neither option improves the business enough to offset licence and support overhead, leave Teams for collaboration and keep voice on the platform that already does that job better.

• Default to Operator Connect for standard Teams calling needs.
• Use Direct Routing only with a clear technical reason.
• Be willing to leave Teams for voice if that removes duplication and support pain.
• Optimise for operating simplicity, not just theoretical platform consolidation.