Teams Phone in Australia: when Operator Connect or SIP is cheaper than more add-on licences

01First, separate the three cost layers

A Teams calling estate usually has three separate commercial layers. Layer one is your Microsoft productivity licence. Layer two is the telephony feature licence, usually Teams Phone Standard unless you already hold a plan that includes it, such as Microsoft 365 E5. Layer three is PSTN connectivity, which can be Microsoft Calling Plans, Operator Connect from a certified carrier, or a SIP based path such as Direct Routing or a replacement PBX. Microsoft’s Teams Phone pages make this distinction explicit: Teams Phone provides the phone system capability, but external calling depends on a PSTN option such as Calling Plans or Operator Connect. Microsoft Teams Phone, Teams calling overview, Calling Plans for Office 365

That matters because many cost reviews go wrong at the first step. Buyers compare a carrier quote against their total Microsoft bill and conclude the carrier is expensive, or compare only the Teams add-on against SIP rates and conclude Microsoft is expensive. Neither is a fair comparison. You need to compare the part you are trying to optimise. If the issue is PSTN connectivity, then your baseline is Teams Phone plus current PSTN spend. If the issue is that too many low-usage staff are voice-enabled, then the baseline is your seat mix, not the carrier tariff.

For Australia, Microsoft publishes business and enterprise Teams pricing on local pages, and shows Teams Phone as an add-on on those pages. Microsoft’s Australian business pricing page also notes that displayed prices exclude GST. Microsoft Teams business pricing, Microsoft Teams enterprise pricing

• Do not compare full Microsoft 365 bundles with bare SIP trunks
• Do compare voice-enabled user count, call usage, number requirements and support overhead
• Assume any option still needs number porting, emergency location setup and admin effort

02When Calling Plans are the most expensive kind of simplicity

Microsoft says Calling Plans are the simplest way to connect Teams Phone to the PSTN, and for some organisations that is true operationally. Setup guidance covers buying and assigning licences, obtaining numbers and configuring emergency addresses and locations. Calling Plans for Office 365, Set up Microsoft Calling Plans

But simplicity is not the same as lowest cost. Calling Plans are still a per-user logic. Microsoft documents three plan types, Domestic, International and Pay-As-You-Go, and notes that identical plans in the same country share a pooled minute allowance. That pooling helps if you have a concentrated group of similar users. It helps less if your estate is mixed, for example 20 reception, sales or service staff who live on the phone and 180 knowledge workers who rarely dial out. In that case you can end up buying voice capability for too many people because organisational convenience wins over seat economics. Calling Plans for Office 365

The add-on effect is also real. Microsoft’s Australian channel pricing shows Teams Phone Standard available at A$19.80 user per month including GST on a monthly term, with a lower effective monthly price on an annual term. Independent Australian pricing summaries published in 2026 also reference A$15 per user per month excluding GST for Teams Phone Standard on annual commitment. Even before PSTN minutes, that is a meaningful recurring charge if you have over-licensed casual callers.

So Calling Plans tend to be cheapest only when three things are true: you value single-vendor administration highly, your user base is relatively homogeneous, and the operational cost of dealing with a separate carrier would outweigh the extra seat spend. That is often true for smaller estates, greenfield deployments and teams that want the fewest moving parts. It is much less true once finance starts asking why hundreds of people have voice licences for occasional inbound and almost no outbound use.

• Best fit: small or mid-sized estates that want minimal telephony administration
• Weak fit: mixed usage profiles with many low-call users
• Watch for: every new voice-enabled seat bringing another monthly licence cost

03Where Operator Connect changes the cost logic

Operator Connect keeps Teams as the client and control plane, but moves PSTN connectivity to a Microsoft-certified operator. Microsoft describes it as the managed option for organisations that want PSTN connectivity without deploying and maintaining their own SBCs. Admins enable the operator in the Teams admin centre, and the operator manages PSTN infrastructure. Plan for Operator Connect, Configure Operator Connect, Operator Directory

That commercial model matters because Operator Connect can break the assumption that every external calling cost must sit inside Microsoft’s own Calling Plan structure. In Australia, Microsoft-certified operators are listed in the Operator Directory, and carrier offers vary by whether they charge per user, shared line, per number, usage, bundles or some combination. Telstra’s published critical information summary is a useful example because it shows the line items clearly: A$19.80 per month GST inclusive for an Individual Line Premium Calling Plan, A$69.30 per month GST inclusive for a Shared Line Premium Calling Plan, and A$4.40 per month GST inclusive for a Teams user add-on for business continuity. The same summary states that the premium plans include unlimited local, national long distance and calls to Australian mobiles.

This is where cost logic changes. If a carrier offers a shared-line or pooled model, you may be able to move part of your estate away from one-user-one-calling-plan economics while still staying native inside Teams. The usual winner profile is the organisation that wants to keep Teams as the user experience, wants a carrier-backed service rather than self-managed SBCs, and has enough scale or uneven usage to negotiate a better commercial shape than Microsoft Calling Plans offer.

Operator Connect is still not automatically cheaper. You still need Teams Phone licensing for users, Microsoft says Operator Connect users must have the required Teams Phone licences, and the operator must be available in your deployment region. Plan for Operator Connect So if your real issue is the Teams Phone licence itself across too many people, Operator Connect only fixes part of the bill. It reduces PSTN cost logic, not the Microsoft phone-system layer.

• Best fit: keep Teams, avoid SBC management, negotiate better PSTN economics
• Weak fit: organisations trying to remove most per-seat telephony licensing altogether
• Watch for: carrier contract terms, number types supported, support boundaries and porting process

04When SIP or Direct Routing becomes cheaper

SIP-based alternatives become attractive when your call volume is better represented by concurrent capacity, call minutes or number inventory than by user count. This is the classic mismatch between collaboration software economics and telephony economics. A 250-person business may only ever have 18 to 25 concurrent external calls at peak. Paying for external calling as though all 250 are full phone users is often where waste starts.

Australian SIP providers publish a wide spread of pricing models, which is exactly the point. Some charge by channel, some by minute, some by call bundle. Examples from current public pages include from A$4.99 per channel per month at Simtex, A$9 per month ex GST for a single PAYG SIP line with A$55 once-off setup at Alltel, 50 cents per month PAYG trunking and unlimited plans from A$20.50 per month GST inclusive at Crazytel, and Twilio’s Australia Elastic SIP Trunking rates starting at US$0.0212 per minute termination with local number pricing shown separately, including US$2.50 per month for a local long-code number.

You should not read those as direct recommendations. They simply show why SIP can be commercially different. If your estate has low concurrency, central call flows, or a front desk and service team doing most of the talking, channel or usage pricing can be materially cheaper than per-seat calling. This is also why some buyers keep Teams for internal meetings and collaboration, but move external telephony to a hosted PBX, contact-centre platform or Direct Routing setup. The point is not to abandon Teams emotionally. It is to stop using a per-user licence where a concurrent-call model better matches reality.

The trade-off is operational. Microsoft positions Operator Connect as attractive when you do not want to deploy and maintain your own SBCs. That is the warning label on Direct Routing and self-managed SIP paths. If you choose raw SIP economics, someone still owns integration, call routing, failover, codec issues, carrier troubleshooting and quality monitoring. If you want help with that engineering and operational layer, that is the space where a team like SyncTrix can help through telephony infrastructure services, cloud infrastructure support and managed services.

• Best fit: low concurrency compared with total staff count
• Best fit: centralised call-handling teams and shared numbers
• Weak fit: buyers who want zero carrier or SBC complexity
• Watch for: internet quality, failover design, PBX ownership and support model

05The checks that matter in Australia: numbers, porting and service obligations

Australian buyers should pressure-test any migration against numbering and porting rules early, not after signing. ACMA states that telcos must follow number management rules under the Telecommunications Numbering Plan 2025 and related industry codes, including local, mobile and inbound number portability codes. Check the phone number rules to follow

For porting, ACMA is clear that customers may port local, mobile, freephone and local rate services when changing provider, and that the losing telco must port the number and cannot refuse or delay because the customer owes money. Rules for porting a phone number That is useful leverage during vendor negotiations, but it does not mean every port is painless. You still need to ask about supported number types, cutover windows, rollback process, and who owns incident handling if a partial port fails.

Do not overlook voice availability and access obligations either. ACMA’s SIP regime pages note that statutory infrastructure providers must provide basic wholesale broadband services in their service areas and that this includes voice services where they operate fixed-line or fixed-wireless networks. Statutory infrastructure provider regime, SIP rules and obligations For most buyers this does not decide between Teams and SIP, but it does remind you that voice continuity, premises connectivity and provider responsibilities are not just product features. They sit inside a regulated telecom environment.

06A practical shortlist: which model is cheaper for which estate

The cheapest option depends less on brand and more on seat shape. Use this shortlist before requesting quotes.

• Mostly identical office users, modest scale, minimal telecom admin appetite: Microsoft Calling Plans can still be defensible because admin simplicity may outweigh some licence overhead.
• Keep Teams, but reduce PSTN cost and avoid SBC ownership: Operator Connect is usually the first alternative to price seriously.
• Large knowledge-worker estate with a small calling-heavy group: SIP or Direct Routing often wins because concurrent calls are far lower than named users.
• Shared reception, queue-heavy service teams, branches with common numbers: shared-line or channel-based models usually deserve immediate attention.
• Replacing only part of Teams: keep Teams for meetings and chat, move external telephony or call-centre functions onto hosted PBX or SIP-based platforms.

07Questions to put to every vendor before you compare the quote

Ask each vendor to price the same estate three ways: named users, concurrent capacity and mixed profile. If they refuse, you are not getting a real comparison. A proper voice cost review also needs an implementation view, not just a monthly fee.

Ask for these specifics: which users actually need Teams Phone, which users only need inbound reachability, whether shared numbers can avoid named-user PSTN plans, whether number porting fees apply, who handles emergency address setup, what happens during internet failure, whether mobile failover is included, and whether call recording, queues or contact-centre features trigger another paid layer. Microsoft’s own setup guidance for Calling Plans includes emergency addresses and phone number assignment as explicit steps, which is a reminder that telephony rollout is never only a licence purchase. Set up Microsoft Calling Plans

Also ask where support boundaries end. Microsoft’s Operator Connect guidance includes a support boundaries section because Microsoft, your operator and your internal IT team do not own the same problems. Plan for Operator Connect If you are evaluating a SIP path, ask who owns SBC patches, codec interoperability, QoS validation, call flow testing and carrier escalations. Those operational costs are easy to ignore in a pricing spreadsheet and expensive to rediscover later.

If the estate is tied to broader platform rationalisation, it helps to treat voice as an architecture decision rather than a procurement line item. That can sit inside a wider technology consulting engagement or a more hands-on API integration programme if telephony has to connect with CRM, service desk or line-of-business systems.

• Price the same estate by named user, concurrent call, and mixed model
• Insist on itemised porting, setup and support charges
• Map support ownership before migration, not after the first outage
• Model low-usage users separately from heavy-call teams