If your Microsoft 365 renewal lands after 1 July 2026, the first reaction is often to strip shared reception, auto attendants and call queues off paid user licences and move them onto free Teams resource-account licences. That part is valid. Microsoft’s pricing update applies to new and renewing customers from 1 July 2026, and renewing customers see the new prices at their next renewal, not before. The catch is that resource accounts are now a required licence type for call queues and auto attendants, not a paid user substitute you can improvise with. Microsoft’s current Teams guidance says every resource account that directly answers calls must have a Microsoft Teams Phone Resource Account licence, and that licence has no cost. But the free licence only removes the cost of the queue or attendant identity itself. It does not remove the costs tied to agents, outbound handling, supervision features, toll-free usage, or the PSTN path you choose. This is why some Australian buyers cut a visible line item and still see reception and queue spend creep upward after renewal.
01What changed after 1 July 2026, and what did not
Microsoft’s March 24, 2026 public FAQ states that the commercial pricing changes are effective from 1 July 2026 and apply to both new and renewing customers globally. For a buyer reviewing renewal options now, that means Microsoft 365 seat pressure is real and current, especially where shared or non-human accounts were quietly left on full licences.
For Teams voice workloads, the more important operational change is in Microsoft Learn: resource accounts for auto attendants and call queues must be assigned a Teams Phone Resource Account licence and Microsoft explicitly says do not assign a Teams Phone Standard licence to a resource account. In other words, free resource accounts are now the correct baseline design, not a clever optimisation.
What did not change is where the telephony work actually happens. Callers still need a number to dial, the queue still needs somewhere to send calls, agents still need the right phone capability, and any outbound or toll-bearing action still has to be funded somewhere. If you budget only for replacing paid queue identities with free resource accounts, you will miss the larger cost drivers in the call flow.
If you want the licensing clean-up before the renewal conversation, this sits naturally alongside a broader technology consulting review of which Microsoft 365 identities should still exist as licensed users and which should become service, shared or resource identities.
- Renewal impact starts at your next renewal after 1 July 2026
- Resource accounts are required for auto attendants and call queues that directly answer calls
- The resource-account licence itself is free
- The free licence does not include agent, PSTN, premium supervision or consumption costs
02Where the cost shifts after you move the queue identity to a free resource account
The first hidden cost is the human endpoint. Microsoft’s Teams Phone licensing guidance is clear that end users need Teams Phone licensing to use Teams as their phone system. The free resource account only covers the voice application identity, not the people who answer calls. So if ten reception or service staff still answer PSTN calls in Teams, those ten users still need the relevant Teams Phone entitlement on their own accounts.
The second hidden cost is the queue design itself. Microsoft’s voice applications prerequisites say that if your auto attendant, call queue or Teams Phone Agent needs to transfer calls to an external phone number, use callback, or use a resource account for representative on-behalf-of outbound calling line ID control, then the resource account needs more than the free licence. For Microsoft-provided numbers, Microsoft requires a funded pay-as-you-go licence, Communications Credits, or telco pay-as-you-go overage. So the minute your reception flow calls mobiles, sends overflow to an answering service, or offers callback, your “free” account starts creating metered usage again.
The third hidden cost is the phone number path. Microsoft’s setup guidance says you should get service numbers for the auto attendants and call queues that phone callers from outside the organisation will call. Those numbers can come through Microsoft, Operator Connect or Direct Routing. The resource account may be free, but the number and carrier model are not.
The fourth hidden cost is advanced queue operations. Microsoft’s Queues app requires users to have both Teams Phone and Teams Premium. If your service desk or reception leads want live metrics, historical views, delegated management, or monitor, whisper, barge and takeover workflows, the bill shifts from the queue identity to supervisor and lead user licences.
- Agent users still need Teams Phone
- External transfer and callback can trigger funded PSTN requirements
- Published numbers still need a PSTN connectivity model
- Queue supervision and analytics can require Teams Premium
03The three Australian call-flow patterns that keep surprising finance teams
Pattern one is the simple main number with internal-only routing. An inbound caller reaches a main number, hears an auto attendant, then gets sent to a queue whose agents are all internal Teams users. If the queue never transfers externally, never offers callback and uses a carrier design that fits your tenancy, the free resource-account model does remove a paid queue identity without adding much else. This is the best-case scenario.
Pattern two is reception with external escape paths. Many Australian organisations forward after-hours calls to a mobile, overflow to an outsourced answering service, or let staff return queue calls showing the main business number. Microsoft’s licensing prerequisites specifically flag external transfer, callback and on-behalf-of outbound calling line ID control as scenarios needing additional PSTN funding or policy. This is where a buyer thinks they eliminated a licence but actually moved cost into metered telephony and more careful routing policy.
Pattern three is the semi-contact-centre pattern. The queue itself may be free, but team leads ask for real-time oversight, call intervention and delegated control. Microsoft now positions the Queues app as an advanced communication capability, and the current management guidance says users need Teams Phone plus Teams Premium. Once you add supervisors, not just agents, the monthly cost grows again.
If you are weighing whether Teams remains the right voice platform once these extras are counted, this is the same strategic question explored in Australia Teams Phone with shared reception and call queues: when the PSTN design makes per-user licensing the wrong model.
| Call-flow element | What the free resource account covers | What still creates cost |
|---|---|---|
| Auto attendant or call queue identity | The resource account licence itself | Any published number, PSTN connectivity and outbound usage |
| Queue agents | Nothing | Teams Phone on each agent user who answers calls |
| External transfer or callback | Nothing | Pay-as-you-go, Communications Credits, or carrier-funded PSTN path depending on design |
| Supervisors and leads using Queues app | Nothing | Teams Phone plus Teams Premium for those users |
| Toll-free inbound usage | Nothing | Per-minute usage through Communications Credits where applicable |
04PSTN design is where the biggest hidden difference appears
Microsoft’s own planning guidance for PSTN connectivity points buyers toward Calling Plans, Operator Connect and Direct Routing, and its Operator Connect planning guide tells you to assess regional availability, number availability, porting support, service offerings and existing carrier relationships. For an Australian buyer, that means the licence conversation is only half the budget. The other half is how your numbers and call paths get in and out of Teams.
Operator Connect is often operationally simpler. Microsoft’s prerequisites also note that when an Operator Connect number is assigned, there are no other requirements for that resource account in that specific numbering scenario. That can reduce Microsoft-side complexity for inbound numbers. But it does not make agent licensing disappear, and it does not guarantee the lowest whole-of-service cost if your call flows have lots of outbound mobility, branch survivability or legacy integration constraints.
Direct Routing can fit buyers who need tighter carrier control, more custom routing or legacy estate coexistence, but it moves cost and effort into SBC design, policy work and operational ownership. Free resource accounts do not offset that engineering overhead. They only stop you paying a user-style licence for the queue identity.
For many Australian estates, the cost question is therefore not “Are resource accounts free?” but “Which PSTN architecture leaves the fewest paid users, the least metered usage and the lowest operational overhead for our specific call flows?” That is usually where telephony infrastructure work adds more value than another round of licence trimming.
- Operator Connect may simplify number assignment and reduce Microsoft-side requirements for certain resource-account scenarios
- Direct Routing may fit complex routing and coexistence, but adds engineering and support effort
- Calling model, not just licence model, determines the real reception and queue cost
05Questions to ask a vendor before you approve the renewal design
Start with the identities. Ask how many current paid user licences are being replaced by resource accounts, and how many human users still need Teams Phone. If the answer is vague, the savings model is probably overstated.
Then ask about every external leg in the call flow. Does the queue ever transfer to mobiles, branch landlines, outsourced reception, or another PSTN destination? Does it offer callback? Does any user place outbound calls showing a main-number caller ID on behalf of the queue? Microsoft’s own prerequisites identify these as scenarios needing additional funding or policy, so they must be costed upfront.
Next ask which users need queue management and supervision features. If managers expect the Queues app, call intervention or reporting in the Teams client, confirm exactly which users need Teams Premium-linked queue capabilities. A common budgeting mistake is assuming only front-line agents need voice-related add-ons.
Also ask how numbers are being delivered in Australia: Microsoft-provided number, Operator Connect or Direct Routing. Ask who owns porting, service assurance, outage handling and emergency calling configuration. A telephony proposal that leads with free resource accounts but leaves PSTN ownership fuzzy is not really finished.
Finally ask about lifecycle management. Microsoft’s getting-started guidance warns that Teams Phone Agent, auto attendant and call queue configurations are not synchronised with Microsoft Entra ID lifecycle events. When staff leave, queue and attendant configurations may still need manual clean-up. That is not just an admin nuisance. It is an operational control issue that can leave stale routing, stale authorised users and bad reporting if no one owns it.
If you are already restructuring shared identities elsewhere in Microsoft 365, related clean-up work is often worth doing in parallel, for example Australia Microsoft 365 renewals in 2026: should room mailboxes, scanners and no-reply accounts leave first and Australia Microsoft 365 renewal after July 2026: which shared mailboxes and service accounts should leave first?.
- How many paid user licences are actually being removed?
- How many agents still need Teams Phone?
- Which flows transfer externally or use callback?
- Who needs Queues app and supervisor features?
- What PSTN model is being used in Australia, and who owns it?
- Who removes stale queue and attendant configuration when staff change?
06What this costs in effort, even when the new resource-account licences are free
The licence itself costs nothing, but there is still project effort. Microsoft’s setup sequence requires you to design call flows, obtain enough free resource-account licences, create a resource account for each voice application that directly answers calls, assign the licences, get service numbers, and then build the attendant and queue configuration in order. That is not a one-click conversion.
In practice, a clean migration usually means four work packages. First, audit the current state: existing call queues, auto attendants, main numbers, agent lists, after-hours paths and any queue-linked outbound calling behaviour. Second, redesign the target state around free resource accounts and the right PSTN pattern. Third, reassign numbers, policies and licences. Fourth, test every inbound and outbound branch, especially external transfer, callback and failover.
The finance-side lesson is simple. Free resource accounts reduce one class of Microsoft licence spend. They do not remove the engineering time needed to untangle old queue designs, and they do not erase monthly spend on user voice entitlements, premium queue tooling or PSTN usage. For many organisations, the real savings come from simplifying call flows and reducing the number of users who genuinely need full Teams Phone, not from the resource-account SKU by itself.
If you need that redesign done without treating voice as a side issue inside a general Microsoft 365 clean-up, SyncTrix can support it through its telephony infrastructure service.
- Audit current voice identities and published numbers
- Map every inbound, overflow and outbound call path
- Separate free queue identities from paid human users
- Cost premium supervision features separately
- Confirm carrier model and ownership before renewal
Sources
- Microsoft 365 Packaging and Pricing Updates Public FAQ | Microsoft Licensing Resources
- Microsoft Teams Phone Resource Account licenses - Microsoft Teams | Microsoft Learn
- Reference - Voice applications prerequisites and licensing - Microsoft Teams | Microsoft Learn
- Reference - Getting Started - Microsoft Teams | Microsoft Learn
- Manage Queues app for Microsoft Teams in your organization - Microsoft Teams | Microsoft Learn
- Microsoft Teams Premium licensing - Microsoft Teams | Microsoft Learn
- What are Communication Credits? - Microsoft Teams | Microsoft Learn
- Cost and connectivity options for Teams Phone extensibility | Microsoft Learn
- Plan for Operator Connect - Microsoft Teams | Microsoft Learn
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.