SyncTrix logoSyncTrix
All articles
Cloud11 min read

Microsoft 365 renewal in Australia: when do free Teams resource accounts still not remove queue and agent licence cost?

Free Teams resource accounts can cut some queue costs after the 1 July 2026 changes, but they do not remove user-side Teams Phone and queue app licensing. Here is where the spend still sits.

By SyncTrix Editorial
Microsoft 365 renewal in Australia: when do free Teams resource accounts still not remove queue and agent licence cost?

If you renewed Microsoft 365 in Australia after 1 July 2026 expecting free Teams resource accounts to make call queues cheap again, the surprise is that the free part only covers one layer of the design. Microsoft’s 2026 packaging and pricing update made the Teams Phone Resource Account licence a zero-cost licence that you still have to acquire and assign, but Microsoft’s current Teams documentation also says each auto attendant or call queue resource account still needs that specific licence, and each user who uses Teams Phone still needs a user Teams Phone licence of their own. If you want the Queues app features in Teams, Microsoft also documents extra licensing on the people side, not the resource-account side. For many Australian renewals, that means the queue number looks free, but the agents, supervisors and any PSTN path still keep the design paid. This post isolates exactly where the remaining licence cost comes from, when it is unavoidable, and what to check before you lock in another term.

01What changed on 1 July 2026, and what did not

Microsoft’s public pricing and packaging FAQ says the commercial Microsoft 365 pricing updates took effect on 1 July 2026. Separately, Microsoft’s Teams documentation now says the Teams Phone Resource Account licence has a cost of zero, but must still be bought and assigned to each resource account used for auto attendants and call queues.

That sounds like a cost removal, but only for the resource account itself. Microsoft is explicit that all resource accounts must be assigned a Teams Phone Resource Account licence, even if they do not have a phone number. Microsoft is also explicit that for each user who uses Teams Phone, you must assign a Teams Phone licence to that user. So the free resource-account change does not replace user licensing.

This is the key buying mistake at renewal. Buyers often compare an older queue design, where a queue endpoint was tied to a more expensive licence pattern, against the new zero-cost resource account and conclude the queue is now free. In practice, only the queue identity is free. The people answering calls often are not.

If you are already reviewing this at renewal, it helps to separate three cost buckets: the queue or auto attendant endpoint, the human users who answer or supervise calls, and the external calling path. If you keep those three apart, the post-renewal bill becomes much easier to explain to finance.

  • Resource account: can now be a zero-cost Teams Phone Resource Account licence, but still must be assigned
  • Agent user: still needs a user-side Teams Phone licence if they use Teams Phone
  • Supervisor or lead: may need extra licensing if you want Queues app capabilities
  • External call path: may still need numbering, trunking, pay-as-you-go or credits depending on design
Design componentWhat Microsoft saysFree after 1 July 2026?Why cost may still remain
Call queue or auto attendant resource accountEach resource account must have a Teams Phone Resource Account licenceYes, licence cost is zeroYou still need to acquire and assign it, and this does not cover users
Agent answering calls in TeamsEach user who uses Teams Phone must have a Teams Phone licenceNoHuman agents remain licensed users
Lead or supervisor using Queues appQueues app is enabled for users assigned both Teams Premium and Teams PhoneNoAdvanced queue management in Teams client remains user-licensed
Resource account making outbound or external transfersIf used to transfer calls externally, assign pay-as-you-go or Communications CreditsNoPSTN-related functions still bring usage or service cost
Where the licence cost still sits after free resource accounts

02Why a free queue account does not remove agent licence cost

Microsoft’s voice applications licensing reference says it covers the licensing requirements for Teams Phone Agent, Auto Attendant and Call Queue, and points admins to the prerequisites and licensing model for those workloads in current documentation. The practical reading for a buyer is simple: the queue object is not the same thing as the person answering the queue. Microsoft keeps those licence boundaries separate in voice applications prerequisites and licensing and in the main Teams Phone setup guidance.

That means any design where real staff answer calls in the Teams client still carries user-side telephony licensing. If your architecture routes inbound calls to a queue, then to named staff, then lets those staff answer, transfer, consult or make outbound return calls in Teams, the savings from free resource accounts are narrow. You saved the queue identity licence, not the agent experience licence.

This matters most in reception, service desk, branch operations and small contact-centre style teams. Those teams often have many people intermittently handling queue traffic. If every one of those people is still a Teams Phone user, the design remains licence-heavy even though the queue endpoint itself is not.

For this reason, some organisations end up redesigning rather than simply renewing. They reduce the number of licensed answering users, centralise queue handling, move some roles to shared endpoints, or compare whether a non-Teams voice path is cheaper for queue-heavy operations. If your queue estate is large, the decision often belongs with technology consulting rather than a simple seat-by-seat procurement review.

  • A resource account represents the queue or attendant identity
  • An agent is still a person using Teams Phone features
  • Free queue identities do not convert human agents into free users
  • The more people who answer, the less impact the free resource-account change has

03When the Queues app makes the cheap design expensive again

Some buyers are not just paying for call answering. They want team leads or reception supervisors to manage queue membership, monitor activity or make changes from inside Teams. Microsoft’s current documentation says the Queues app is enabled by default for users assigned both a Teams Premium and Teams Phone licence and who are voice enabled. Microsoft’s Teams Premium licensing page also describes the Queues app as part of Teams Premium’s advanced communications capabilities and notes that tenants with licences purchased before 1 April 2026 have transitional access terms until those licences expire.

This is where a design that looked cheap on paper often becomes expensive after renewal. Resource accounts are free, but the supervisors or leads who need the Queues app are not. If you have ten queue agents and three supervisors, you may end up with a mixed licence estate: resource accounts at zero cost, agents on Teams Phone, and supervisors on Teams Phone plus Teams Premium.

The buyer question to ask is not, 'Are resource accounts free?' It is, 'Which people need which queue functions in the Teams client?' If the answer includes delegated queue management, real-time operational actions or lead-level controls, the user-side licensing can outweigh the queue-side savings quickly.

This is the exact crossover point explored in Teams Queues app in Australia: when does Teams Premium turn a cheap queue design expensive again?. It is useful when procurement is being told the queue itself is now free, but operations still want the premium control surface.

  • Basic queue endpoint cost and advanced queue management cost are different things
  • Queues app capability sits on licensed users, not on the resource account
  • Renewals are where old assumptions about bundled access usually break
  • Supervisory users often become the hidden cost centre

04The PSTN and external transfer layer can still keep the design paid

Even if your resource accounts are free and your user licensing is under control, the external calling path can still preserve cost. Microsoft’s getting started reference says that if a resource account is used to transfer calls externally, assign a pay-as-you-go licence or Communications Credits. The resource account licence itself does not cover that external transfer scenario.

Microsoft also states in the resource-account licensing guidance that a Microsoft calling plan is not required unless you want the resource account to be able to dial out. That is another common confusion point. Buyers hear 'not required' and think there is no telephony service cost. What Microsoft actually means is that the zero-cost resource-account licence is sufficient only until you need outbound PSTN behaviour or external transfer behaviour.

In Australia, this becomes a design question rather than a pure licence question. If your queue only receives calls and routes internally, the queue side can be very cheap. If your attendants transfer to mobiles, overflow externally, route to third parties or make outbound callbacks from queue-linked identities, you are back into service and usage design decisions.

That is why queue reviews should sit alongside your broader telephony infrastructure services plan, not inside a narrow Microsoft renewal spreadsheet. The licensing line items and the call-routing line items interact.

  • Inbound only, internal routing only: often the cheapest case
  • External transfer from resource account: extra PSTN-related entitlement may apply
  • Outbound dialling from resource account: zero-cost resource licence is not enough
  • Numbering and trunk design still matter even when the queue account is free

05The designs that still stay expensive after renewal

You should expect free resource accounts to have limited impact in four common designs.

First, large hunt-group style teams where many named staff answer queue traffic in Teams. The queue endpoint is free, but every answering user still needs the right Teams Phone entitlement, so the cost base follows headcount more than queue count.

Second, reception and switchboard setups with delegated control. As soon as reception leads need the Queues app inside Teams, Microsoft’s documentation points you to Teams Phone plus Teams Premium. The free resource accounts do not help with those user-side features.

Third, branch or service teams with heavy outbound call handling. If the queue design requires external transfers, return calls or PSTN-connected workflows, Microsoft’s documentation keeps separate service requirements around external calling and transfer behaviour. Again, the queue identity being free does not remove that layer.

Fourth, estates with many old configurations that were never normalised. Microsoft now says all resource accounts should use the Teams Phone Resource Account licence and not Teams Phone Standard. If you renew without cleaning that up, you can carry legacy assignment mistakes and still not get the expected savings.

If this is your situation, compare your current design with adjacent options, such as shared reception approaches or non-per-user voice paths. These trade-offs are discussed in Australia call queues after the 2026 Teams changes: when should reception move off user licences and onto resource accounts? and Australia Teams Phone licensing in late 2026: when do resource accounts and call queues push costs past SIP?.

  • Many answering users
  • Supervisor controls in Teams
  • Outbound or external transfer needs
  • Legacy licence assignments carried into renewal

06What to check before you sign the renewal order

Do not ask your reseller only for the new Microsoft price. Ask for a queue-design licensing map. The aim is to identify which components are genuinely free, which are still per-user, and which depend on calling behaviour.

Start with the resource-account inventory. Count every auto attendant and call queue, then confirm each one is using the current Teams Phone Resource Account licence. If any still carry older user-style licensing, you have cleanup work before you can even estimate savings accurately.

Then map agent roles. How many people only receive transferred calls, how many answer queues directly, how many need outbound telephony, and how many need queue management in the Teams client? That role split determines where the paid licences remain.

Then review call flows. Do calls ever transfer to external numbers from the queue path? Do resource accounts need to dial out? Are there mobile escalation paths? Microsoft’s own getting-started guidance is clear that external transfer scenarios may need pay-as-you-go or Communications Credits.

Finally, get the commercial view in writing. Ask your provider to show the delta between your current state and the proposed state: number of resource accounts, number of Teams Phone users, number of Teams Premium users, and any PSTN or calling-service assumptions. Without that, buyers often approve a 'cheaper' design that only moved cost from one column to another.

  • Inventory every queue and auto attendant resource account
  • Confirm each resource account has the correct zero-cost licence assigned
  • Classify users by actual telephony behaviour, not job title
  • Identify which users need Queues app features
  • Check any external transfer or outbound requirement
  • Ask for before-and-after licence counts by component

07Effort, risk and the decision rule for Australian buyers

The effort is usually modest if your environment is already clean, and higher if you have inherited telephony sprawl. A tidy tenant may only need a short review of resource-account assignments, queue membership and supervisor roles. A messy tenant may need a full voice-application audit because cost depends on how people actually handle calls, not how the org chart says they should.

The main risk is buying on the basis of one true statement that is too narrow: 'resource accounts are free'. That statement is true according to Microsoft’s current documentation, but incomplete. A better decision rule is this: free resource accounts reduce queue-endpoint cost, but they do not remove user-side Teams Phone needs, they do not include Queues app rights for leads and supervisors, and they do not eliminate external calling requirements where your flows need them.

For many buyers, the question is not whether Microsoft is wrong. It is whether the current Teams voice design is still the right commercial shape after renewal. If most of your spend sits with licensed people and queue operations rather than with queue identities, the real savings may come from redesigning call handling, not from relying on the resource-account rule change alone.

That is the point where a team such as SyncTrix can help review the telephony architecture, licensing assumptions and operational workflow together, rather than treating renewal as a pure procurement exercise.

  • Use the free resource-account change as a design input, not as the whole business case
  • Model cost by endpoint, user role and external call path separately
  • Expect supervisors and advanced queue workflows to stay paid
  • Focus on redesign where the user count, not the queue count, drives spend

Topics

free Teams resource accounts still not remove queue and agent licence cost AustraliaMicrosoft 365 renewal Australia Teams resource account costTeams call queue agent licence AustraliaTeams Phone resource account licence free but users still paidTeams Queues app Teams Premium cost AustraliaMicrosoft 365 July 2026 pricing Teams Phone renewal

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.