Australian IT directors comparing Teams Phone with SIP or older PBX estates often spot one obvious saving first: move auto attendants and call queues onto resource accounts, keep only real people on user licences, and stop paying full voice licences for every shared number. That is still a valid optimisation. Microsoft says auto attendants and call queues need at least one Teams Phone licence in the tenant and a free Teams Phone Resource Account licence for each resource account, and those resource account licences now have no cost associated with them. But there is a second cost trigger that appears later in queue-heavy environments: the Queues app. Microsoft’s own documentation says the Queues app is included in Teams Premium, and authorised users who need to manage queues in the Teams client need both Teams Premium and Teams Phone. If your service desk, reception, clinics, branches or customer service teams want live queue metrics, historical views, opt-in and opt-out control, delegated queue changes, or supervisor actions such as monitor, whisper, barge and takeover, your ‘cheap queue design’ can become expensive again because some of the people around the queue, not just the queue itself, need a higher licence set. This post shows where that trigger appears, how to spot it early, and how to keep the Premium layer limited to the people who genuinely need it.
01The low-cost queue design that still works
The base design is straightforward. Microsoft’s current voice applications licensing reference says auto attendants and call queues need at least one Teams Phone licence to enable the service, plus a free Teams Phone Resource Account licence for each resource account. Microsoft also states that there is no longer any cost associated with acquiring those resource account licences. That is the part many cost comparisons get right.
A resource account is the identity attached to the queue or auto attendant. Microsoft’s documentation says each resource account must have the resource account licence whether or not it gets a phone number, and you should not assign a normal Teams Phone Standard licence to that resource account. In practice, that means your published main numbers, after-hours menus and departmental queues can sit on zero-cost resource licences while only actual staff need user licences.
For Australian estates trying to reduce per-seat voice cost, that design is often the first move before wider telephony cleanup. If you are still sorting shared reception, hunt groups and front-desk patterns, these related reads help frame the trade-offs: shared reception and call queue PSTN design, resource accounts and call queues in late 2026, and when reception should move onto resource accounts.
- Good fit: one main number, simple menu, small queue membership, changes handled by central IT.
- Main saving: published numbers and queue identities do not need paid user licences.
- Common mistake: assuming that because the queue identity is cheap, queue operations will also stay cheap.
| Need | Cheapest workable design | What changes the cost |
|---|---|---|
| Publish a main number or department number | Resource account with free Teams Phone Resource Account licence | Nothing, if IT manages configuration centrally |
| Basic call queue routing | Call queue plus resource account | Nothing, if agents just answer calls |
| Queue member opt in and opt out in the Queues app | User with Teams Phone | Queues app access brings in Teams Premium for supported use cases |
| Supervisor sees live queue metrics and historical views in Teams | User with Teams Phone | Queues app analytics require Teams Premium access path |
| Supervisor changes greetings, business hours or queue membership from Teams | Authorised user | Authorised users for Queues app need Teams Premium and Teams Phone |
| Coach agents with monitor, whisper, barge or takeover | Authorised user with policy | Operational supervision makes Premium the trigger |
02What exactly triggers Teams Premium
Microsoft’s support article on managing call queue and auto attendant settings says the Queues app is included in Teams Premium. Microsoft’s Teams Premium licensing page also lists the Queues app under advanced communication features, and notes a licensing update effective 1 April 2026: some features that were previously only in Teams Premium are now included with Teams Enterprise, but Teams Premium still includes advanced communication features such as the Queues app.
That matters because the trigger is user capability, not merely queue existence. Microsoft’s admin guidance for the Queues app says it is enabled by default for users who are assigned both Teams Premium and Teams Phone and who are voice enabled. Microsoft’s authorised users setup article also says authorised users are the delegated people who can make configuration changes to auto attendants and call queues. The linked guidance for authorised users states that Queues app is available to authorised users with a Teams Premium and Teams Phone licence.
So the cost line is this: if a person only answers queue calls as an agent, you may not need to give that person Teams Premium just because the queue exists. But once that person needs the Queues app for delegated management, reporting, or supervisor controls, the Premium layer appears. This is the licensing detail that gets missed in rough Teams versus SIP comparisons.
- The trigger is usually a subset of users, not the whole company.
- Teams Premium is attached to what people do around the queue.
- A queue-heavy environment can therefore have a cheap core design and an expensive operations layer at the same time.
03Which queue operations create the second licensing layer
Microsoft’s current Queues app documentation describes several capabilities that turn a plain voice deployment into an operations tool. Authorised users can configure call queues and auto attendants from the Teams client, opt agents into and out of queues, and view real-time metrics and historical reporting. Microsoft’s support guidance for analytics says users can see real-time and historical metrics in the app if IT has authorised them, with historical analytics available over a selected time range and queue or agent level views depending on permissions.
The biggest cost trigger is usually supervisor experience. Microsoft lists monitor, whisper, barge and takeover in the Queues app for authorised users. Those are not just nice-to-have features. In a healthcare booking team, service desk or multi-branch reception environment, they are the controls managers ask for once the basic call flow is live. The moment those capabilities are in scope, selected team leads and supervisors stop being standard voice users and become Premium candidates.
A second trigger is delegated change ownership. Many IT teams design a low-cost queue setup on the assumption that central admins will manage business hours, holiday routing, greetings and queue membership. That works until branch managers or service leaders want same-day control in the Teams client. Microsoft’s Queues app guidance is explicit that authorised users can make those changes from Teams. If your governance model allows that delegation, licence scope expands.
- Real-time queue metrics for team leads.
- Historical queue analytics inside Teams.
- Agent opt in and opt out control.
- Delegated queue and auto attendant changes.
- Supervisor coaching actions: monitor, whisper, barge, takeover.
04How many people usually need Premium, and how to keep it contained
The practical answer is rarely 'everyone on Teams Phone'. Microsoft’s own product page for Australia positions Teams Premium as an add-on and says the Queues app requires a Teams Phone licence. That means you should scope Premium around named operational roles, not broad departments.
Start by dividing queue users into four groups. First, callers never see these people, they are admins designing the platform. Second, agents simply answer calls. Third, leads or supervisors need live visibility, staffing control and occasional call coaching. Fourth, business owners want queue changes without IT intervention. In most organisations, only groups three and four need the Queues app experience often enough to justify the add-on.
This is where governance saves money. Keep permanent Premium assignment for stable queue supervisors and service leaders. Avoid assigning it to every queue member 'just in case'. For seasonal or project-based spikes, decide whether central IT can absorb queue changes temporarily instead of licensing more authorised users. If your operating model is immature, it is often cheaper to delay delegation than to licence an entire function prematurely.
If you need help separating platform design from operating model, telephony infrastructure services and technology consulting are the relevant service lenses. This is not only a telephony build issue, it is a control and ownership issue.
- Name the smallest possible supervisor cohort.
- Use Premium for people who need Teams-native queue operations, not everyone who takes calls.
- Revisit access quarterly, because queue leads often accumulate licences after go-live.
05What it means for Australian cost modelling
For Australian buyers, the important point is not the exact future invoice total, because Microsoft pricing and reseller terms can vary. What is sourceable today is that Microsoft lists Teams Premium in Australia as an annual subscription add-on, and Microsoft’s Teams business pricing pages state that listed prices do not include GST. So when you model queue cost, treat Premium as a separate per-user overlay on top of the user’s base Microsoft 365 and Teams Phone stack, not as part of the queue object itself.
That changes the economics of queue-heavy environments. A simple head office main line with one backup receptionist may still be cheap. A distributed operation with branch leads, rostered supervisors, overflow teams and service managers can move very differently. The queue design itself may remain resource-account based and efficient, but the people who need visibility and intervention rights can create a meaningful second licence pool.
One more nuance matters after Microsoft’s 1 April 2026 licensing update. Some features that were Premium-only moved into Teams Enterprise. If you already have Teams Enterprise for the relevant users, recheck whether that changes your add-on need for those users. Do not assume all Premium-era comparisons still hold unchanged. Use current tenant entitlements, not last year’s deck.
- Model queue economics in two layers: queue objects and operating users.
- Add GST to Australian list prices where Microsoft says checkout applies it.
- Check whether any affected users already have Teams Enterprise entitlements before adding Premium.
06Questions to ask before you approve Teams as the voice platform
Most overspend happens because the queue design workshop focuses on numbers, menus and routing, but not on who will run the queues day to day. Before you sign off, ask these questions internally or put them to your vendor.
Who will change business hours, holiday routing and emergency messages? If the answer is branch managers or service supervisors, you are heading towards authorised users and the Queues app.
Who needs live queue visibility during the day? If the answer is team leaders managing abandoned calls or service level, do not model them as plain agents.
Do supervisors need coaching features such as monitor, whisper, barge or takeover? Microsoft lists these as Queues app capabilities for authorised users, so this is a clear Premium trigger.
Will queue analytics in the Teams client replace separate reporting or admin-centre access? Microsoft documents both real-time and historical analytics in the app. That can be genuinely useful, but it is not free from a licensing point of view.
Can central IT own queue changes for six months after go-live? If yes, you may delay Premium assignment until the operation proves it needs delegated control.
Is your comparison against SIP or another hosted voice platform using the same operating assumptions? If the competitor includes supervisor consoles by default and your Teams estimate does not, the comparison is distorted.
For a broader architecture lens, cloud infrastructure and managed services become relevant when Teams voice is part of a larger workplace stack and support model.
- Ask about ownership, not just routing.
- Separate agent needs from supervisor needs.
- Make the vendor cost the delegated operating model explicitly.
07A practical decision rule for IT directors
Use a simple rule. If your queues are static, centrally managed and mainly there to route calls, the resource-account model keeps Teams voice comparatively lean. If your queues are operationally active, with supervisors watching demand, changing settings, coaching staff and managing opt-in status in real time, Premium becomes part of the true cost of ownership for at least a subset of users.
That does not make Teams the wrong answer. It means the wrong comparison is 'resource accounts are free, therefore queue operations are cheap'. The correct comparison is 'resource accounts are cheap, but queue operations may require Premium for the people who run them'. In many Australian environments that is still acceptable if you limit Premium to supervisors, leads and delegated business owners.
The safest next step is a short role-based licensing matrix before procurement. List every queue-related role, what they actually do, whether they need Teams-native supervision or delegated change rights, and whether central IT could absorb that work instead. That exercise usually exposes the real cost trigger earlier than a feature checklist does. SyncTrix can help structure that assessment where Teams voice, queue design and operating ownership are being worked through together.
- Cheap queue object: yes.
- Cheap queue operations: only if control stays central and supervisors do not need the Queues app.
- Budget risk point: queue-heavy service teams with delegated leads and live supervision.
Sources
- Manage your call queue and auto attendant settings in Microsoft Teams
- Reference - Voice applications prerequisites and licensing
- Microsoft Teams Phone Resource Account licenses
- Setup - Authorized Users
- Manage Queues app for Microsoft Teams in your organization
- Get real-time and historical analytics in the Queues app for Microsoft Teams
- Microsoft Teams Premium licensing
Topics
SyncTrix Editorial
SyncTrix · SyncTrix
Writes about the engineering decisions behind production systems - architecture, delivery and the trade-offs that only show up at scale.
Building something like this?
SyncTrix engineers AI, SaaS, platform and cloud systems for enterprises and high-growth teams. Tell us what you're shipping and we'll scope it with you.