Australia Teams Phone licensing in late 2026: when do resource accounts and call queues push costs past SIP?

01What Microsoft actually requires once you add shared voice functions

The licensing trigger is not just the person who answers calls. Microsoft says a resource account is required for each auto attendant or call queue. That means shared main lines, department queues, hunt groups, after-hours attendants and similar voice app objects each add administrative objects to manage, even though the resource account licence itself is free. See Manage resource accounts for voice applications and Teams Phone Resource Account licences.

Microsoft also says that auto attendant and call queue features require at least one Teams Phone licence to enable the services, and that a free resource account licence is needed for each resource account. If the resource account is used to transfer calls externally, Microsoft’s getting started guidance says you must assign pay-as-you-go licensing or Communications Credits to that resource account. This is where ‘free’ voice apps start to become a real operating model, not a zero-cost add-on. See voice applications prerequisites and licensing and getting started for Teams Phone Agents, auto attendants and call queues.

For an IT leader, the practical consequence is simple: the more shared call handling you build, the less useful a plain per-user comparison becomes. The live cost is a mix of user seats, PSTN connectivity, resource account count, outbound transfer needs, number management, and support effort.

• One resource account per auto attendant or call queue
• Resource account licence is free, but still must be acquired and assigned
• At least one Teams Phone licence is needed to enable the services
• External transfer from a resource account adds pay-as-you-go or Communications Credits requirements
• Complexity rises with every shared number, routing branch and overflow path

02Use the current Australian price base, not old drafts

The rejected draft used uncited figures. The current Microsoft Australia pages now give you a clean baseline to work from. Microsoft lists Microsoft 365 Business Premium at AU$32.90 user/month, paid yearly. Microsoft also lists Microsoft 365 E5 at AU$89.80 user/month, paid yearly. If you are building a late 2026 business case, these are the numbers your finance team will recognise from Microsoft’s Australian pages, not older cached screenshots or partner quotes.

For Teams Phone itself, Microsoft’s Australia pricing pages show Teams add-ons and business plan pricing, but the exact mix you can buy depends on whether you are on a business or enterprise suite and whether Teams is already included. That is why the first question is not ‘what does Teams Phone cost?’. It is ‘what are we already paying for the base suite, and which users actually need telephony?’. Microsoft’s business plans with Teams pricing page, Teams business options page and additional services pricing page should be your source of truth when you refresh the model.

If your organisation is already reassessing Microsoft seat cost after the July 2026 change cycle, this voice decision should sit beside that broader suite review, not outside it. The same users who no longer justify a higher Microsoft 365 tier may also be the users who do not justify Teams-native calling. That is covered in our related post on Microsoft 365 renewal after 1 July 2026.

• Cite the live Australian Microsoft pages, not old reseller PDFs
• Separate base suite cost from telephony add-on cost
• Review which users genuinely need Teams Phone, not just Teams meetings
• Fold voice review into your Microsoft 365 renewal analysis

03Where Teams Phone stays cost-effective

Teams Phone remains commercially sensible when your call design is simple. Typical examples are a small office where named users answer direct inbound calls, a modest receptionist function, or a few departmental queues with limited branching. In those cases, Operator Connect or Direct Routing can keep telephony inside the Microsoft admin model without much design sprawl. Microsoft positions Operator Connect as a simplified PSTN option managed through approved operators, while Direct Routing is intended for organisations that need an SBC and more control.

It also stays attractive when your users live in Teams all day. If call handling, presence, chat, meetings and internal transfer are tightly integrated into one client, some operational friction disappears. You may accept a higher pure telephony cost if it removes another handset estate, another admin console, and another support process. That is not a licensing argument, it is an operating model argument.

In Australia, that often means Teams Phone still wins for knowledge-worker heavy businesses with low queue complexity and limited contact-centre style routing. If you are mainly deciding between Microsoft PSTN options rather than between Teams and non-Teams voice, compare Operator Connect, Direct Routing and other PSTN connectivity options. You can also see our own breakdown in Teams Phone in Australia when Calling Plans are not the fit: Operator Connect, Direct Routing or leave Teams for voice?.

• Few call queues and attendants
• Mostly named users, not shared functions
• Low need for external transfers from resource accounts
• Minimal after-hours, overflow and branch logic
• Strong value in keeping calling inside the Teams client

04Where the hidden cost starts to tilt towards SIP or self-hosted voice

The crossover usually appears when shared functions grow faster than user seats. Examples include multiple front-door numbers, state-based routing, language menus, department queues with overflow, separate after-hours behaviour, voicemail branches, contractor hotdesking, warehouse phones, lift or gate lines, and service desks that need different call treatment by time of day. None of these are exotic. Together, they create a voice application estate.

The resource account licence itself is free, so the spend does not show up as a neat line item. Instead it appears as design complexity and supporting cost. Someone has to create every resource account, bind it to the right call queue or auto attendant, assign numbers where needed, manage transfer behaviour, track external calling requirements, and test every routing change. Microsoft’s guidance makes clear that these are separate objects with separate licensing and numbering considerations, not just labels inside one queue. See resource account management and PSTN connectivity options.

That is the point where SIP trunking or a self-hosted PBX can become cheaper overall. Not because the Microsoft seat is always more expensive, but because a SIP platform may price shared numbers, ring groups and routing logic more naturally than a per-user collaboration stack does. If 40 shared call-handling objects support 15 real call agents, a Teams-first design can look elegant in architecture diagrams and still be the wrong cost model.

• Shared functions outnumber named answering users
• High count of auto attendants and queues
• Frequent external transfers and complex routing
• Large service-number estate
• More administration per voice object than per user

05How to model the comparison properly

Use a four-part model. First, calculate the base suite position by user cohort. Separate users who already need Microsoft 365 Business Premium or E5 for non-voice reasons from users whose only premium need is calling. Use Microsoft’s live Australian pages for the base figures, such as Business Premium at AU$32.90 and E5 at AU$89.80.

Second, price the Teams telephony layer. Include the Teams Phone entitlement path, your PSTN choice, service numbers, any pay-as-you-go or Communications Credits requirements for external transfer scenarios, and the operational cost of maintaining queues and attendants. Microsoft’s Teams Phone licensing, Operator Connect planning and Direct Routing planning are the right starting points.

Third, price the SIP or self-hosted option as a whole service, not just trunks. Include PBX or platform licensing, SBC if relevant, call recording if required, DDI ranges, number porting, failover, support, and the admin work to manage routing. If you keep Teams for collaboration but move calling elsewhere, also include user experience compromises such as a separate softphone or handset.

Fourth, add change cost. This is the part most business cases skip. Ask how often your call flows change, how many sites or departments request changes, how often after-hours schedules shift, and how much testing is needed after every change. The busier your operations team is, the faster shared-function complexity starts to dominate the licence maths.

If you need help redesigning the telephony estate rather than just pricing licences, this is the sort of work covered in telephony infrastructure services, often alongside cloud infrastructure and governance and compliance support.

• Model by user cohort, not one blended seat price
• Include resource-account-driven admin effort
• Include external transfer charging requirements
• Include change and testing effort
• Compare operating model, not only licence lines

06Questions to put to Microsoft partners, operators or SIP vendors

A good vendor comparison is less about features and more about billing triggers and operating effort. Ask each supplier to map your exact call flows, not a generic seat count. Require them to show which objects are billable, which are free but still need configuration, and which actions trigger usage charging.

For a Teams-based design, ask: how many resource accounts will the proposed call flow need, which of them need service numbers, which require outbound external transfer capability, and what administrative roles and processes will your team need to manage them safely. Ask them to point to Microsoft documentation, not only their own estimate. Microsoft’s resource account licence page and voice application licensing reference are useful benchmarks.

For a SIP or PBX design, ask: how are shared functions priced, what happens when queues double, what is included for failover and number porting, and whether your users can stay inside Teams for collaboration while calling runs elsewhere. If they say it is cheaper, make them show the assumptions for admin effort, support tier and change requests.

If your telephony estate connects to line-of-business systems, site devices or existing mail and directory services, the integration work can matter as much as the voice bill. Relevant capabilities often sit across API integration, managed services and telephony engineering, not inside a simple telco contract.

• How many resource accounts are needed for the proposed design?
• Which resource accounts need service numbers?
• Which flows need external transfer and what billing applies?
• What daily admin tasks stay with your internal team?
• How are changes, testing and after-hours updates charged?
• What breaks if you later move from Teams voice to SIP, or back again?

07The practical late 2026 answer for Australian IT leaders

In late 2026, Teams Phone is usually still the cleaner choice for straightforward office telephony, especially when Teams is already central to collaboration. But once your voice estate is driven by shared functions rather than named users, the cost question changes. Microsoft’s licensing model clearly separates base suites, Teams Phone licensing and specialised resource accounts. The resource account licence may be free, but the queue and attendant estate it enables is not free to design, maintain or support.

That is why the right crossover test is not ‘is SIP cheaper per line?’. It is ‘are we now paying collaboration-style licensing and administration for what has become a routing-heavy telephony platform?’. If the answer is yes, reprice against Operator Connect, Direct Routing and non-Teams voice options immediately. Our related post, Teams Phone in Australia: when Operator Connect or SIP is cheaper than more add-on licences, goes deeper into that choice.

For many Australian mid-market organisations, the break point arrives when call queues, attendants and shared numbers become an operational system in their own right. That is the moment to stop arguing over headline user plans and start costing the voice architecture you actually run.