Microsoft 365 renewal in Australia: which users are expensive enough to move off first after the July 2026 change?

01Start with a licence triage, not a tenant-wide migration plan

Before you touch technology, split users into cost and dependency bands. The bands that move first are the ones with low app dependency, predictable workflows and weak justification for bundled Microsoft features.

For most Australian organisations, there are five obvious cohorts to examine first: mail-only users, kiosk and shared-mailbox style users, frontline and task workers, shared-device workers, and voice-heavy users. These groups often sit on licences that include more collaboration, management or security tooling than they actually consume.

Microsoft’s July 2026 change matters here because it hits the broad commercial base. The official FAQ says the increase applies to products including Microsoft 365 Apps, Business Basic, Business Standard, F1, F3, Office 365 E3 and Microsoft 365 E3 and E5. Telstra’s Australian summary also states that pricing updates apply on 1 July 2026, and mentions add-ons such as Teams Phone are affected too.

That means your first pass should be financial, not ideological. Pull twelve months of assigned licences, sign-in data, mailbox use, Teams call records, and device type. Then ask one blunt question per cohort: what is the cheapest safe way to deliver what these users actually do every day?

• Export assigned licences and add-ons by user
• Map each user to one primary work pattern, not job title
• Check whether they really need desktop Office, a mailbox, Teams, telephony, or just identity
• Flag users on shared Windows devices, shared mobiles, or common area endpoints
• Separate users who need compliance features, litigation hold, or advanced security controls

021. Voice-heavy users often have the clearest payback

If you have users carrying a base Microsoft licence plus Teams Phone, these are often the first seats to challenge. Microsoft states that Teams Phone Standard is an add-on licence that provides PBX features such as voicemail, call forwarding, call transfer, auto attendants and call queues, but external PSTN calling still requires a connectivity option.

That matters because many organisations are effectively paying twice, once for a productivity suite and again for telephony, even where the operational requirement is mostly inbound and outbound calling. In those cases the real comparison is not Microsoft versus nothing. It is Microsoft plus telephony add-ons versus keeping Microsoft for collaboration while moving voice to a cheaper carrier and routing model, or leaving Teams for voice altogether.

Put these users first if they spend most of the day in calls, rely on hunt groups or queues, and make little use of SharePoint, OneDrive or Office apps beyond email. This is especially common in reception, sales development, service desks and contact-centre-lite teams.

Before moving them, verify three things: call recording obligations, emergency calling setup, and number porting constraints. Microsoft highlights PSTN and emergency calling options on its Teams Phone product page, so if those are business-critical you need a design review, not just a licence cutover.

If your question is specifically whether Teams should remain the telephony front end, the related guidance in Teams Phone in Australia: when Operator Connect or SIP is cheaper than more add-on licences helps narrow that decision, and /services/telephony-infrastructure is the practical service area if you are redesigning voice rather than just renewing it.

• Best early targets: reception, queue-based support, outbound sales, branch phones
• Highest savings potential: users with both suite licences and Teams Phone add-ons
• Do not move first: executives or mobile staff tied to Teams meetings and calling in one workflow

032. Mail-only users are the next easiest cohort to pull out

Mail-only users are often the cleanest exit group because their requirement is narrow. They need a business email address, basic calendaring, and mobile access. They usually do not need desktop Office, SharePoint collaboration or advanced workflow tooling.

Microsoft’s own service description says each user who accesses Exchange Online must be assigned a subscription plan, while shared mailboxes and room mailboxes do not need user subscriptions if licensed users access them by delegation. That distinction matters. Many tenants carry lightly used user mailboxes that could be restructured, converted, or moved instead of renewed on a broad suite.

This is where finance and IT should work together. Look for users with low mailbox activity, almost no OneDrive use, no Teams meeting history, and no installed Office apps. These users are expensive enough to move when their suite licence exists mainly to keep an inbox alive.

Do not assume every mail-only user needs Microsoft-hosted mail. Some will, especially where retention, legal hold or Microsoft-native admin workflows matter. But where the need is simply reliable business mail, a lower-cost platform or a tightly managed self-hosted design can produce faster payback than trying to optimise higher-tier Microsoft bundles. If you are comparing those options, Microsoft 365 renewal shock in Australia: should you self-host mail now? and Self-hosted mail vs Google Workspace vs Microsoft 365: when self-hosting is worth it are useful decision companions.

The workload here is usually modest: mailbox migration, autodiscover and DNS changes, mobile profile resets, archive decisions, and anti-spam tuning. The users themselves are not usually the hard part. Policy and deliverability are.

• Good candidates: warehouse supervisors, casual staff, field technicians, low-traffic admin mailboxes
• Check first: mailbox size, archive use, shared calendar dependence, delegated access
• Plan for: SPF, DKIM, DMARC, mobile reprovisioning, historical mailbox access

043. Frontline users on F3 deserve a hard look before you renew them

Microsoft’s Australian pricing pages show Microsoft 365 F3 at AU$15.00 per user per month, paid yearly, and Microsoft 365 F1 at AU$4.50, both excluding GST. That gap is large enough that every frontline F3 seat should now be justified by actual usage, not by a historic rollout decision.

The trap is simple. Organisations often standardise on F3 because it feels safer, then discover many shift-based workers mainly read announcements, acknowledge rosters, open a couple of web pages and maybe check a mailbox. If that is the reality, those users may be over-licensed.

Another important detail is that Microsoft’s Exchange service description states Microsoft 365 F1 does not include rights to an Exchange mailbox. So an F3 to F1 move is not just a downgrade calculation. It is a work-pattern decision. If the user genuinely needs email, F1 may not be the right landing point on its own.

This is why frontline migration should be split into two groups. First, F3 users who really need email, editable apps, workflows or device management. Keep or redesign them carefully. Second, F3 users who are mostly consuming information or completing narrow tasks. They are strong candidates for F1, alternate communication tools, or even no dedicated mailbox if shared workflows cover the use case.

If your organisation has branch, retail, logistics or manufacturing patterns, this is where role-based packaging beats department-based packaging. The same job family can contain both keeper and mover users depending on whether they create content, approve work, or only receive instructions.

• Review F3 users who have low mailbox activity and no desktop app use
• Do not downgrade anyone who needs a personal mailbox without planning the replacement
• Test role packs by activity pattern: creators, approvers, readers, voice-only

054. Shared-device and kiosk environments can be over-licensed in a different way

Shared-device estates are expensive when you licence them as if each person had a personal digital workspace. Microsoft’s guidance on shared computer activation says it is required where multiple users share the same computer and sign in with their own account. Microsoft also notes support for shared computer activation only on plans that include Microsoft 365 Apps, with examples such as enterprise plans and Business Premium.

That creates a common mismatch in warehouses, shop floors, nursing stations, labs and dispatch points. The physical device is shared, the tasks are narrow, and the shift handover matters more than a rich personal app estate. Yet licensing is often assigned as if each worker needs a full user-centric bundle.

Microsoft’s frontline device guidance also recommends shared device mode for supported mobile scenarios so staff can sign in once and sign out once, reducing cached data exposure between users. That is a security and usability signal: shared-device design needs its own architecture. It should not be treated as a cut-down knowledge worker deployment.

These users are expensive enough to move early when the current model combines per-user suite licensing with weak personal app usage. The payback does not always come from removing Microsoft entirely. Sometimes it comes from moving to device-based design, thinner user entitlements, or isolating mail from app access.

If you are reshaping the device and identity side as part of the exit, /services/cloud-infrastructure and /services/cybersecurity-risk are relevant because the control model changes with it.

• Look for desktops or mobiles used across shifts or hot-desk pools
• Measure sign-in friction, cached data risk and app switching time
• Compare user-based suite licensing against device-led access design

065. Leave broad collaboration users until last, even if their licence looks pricey

It is tempting to go after Business Standard, Business Basic or E3 seats because there are many of them. But these users are often the hardest to move cleanly because they genuinely consume multiple services: Outlook, Teams meetings, OneDrive, SharePoint, desktop apps and identity controls.

For example, Microsoft lists Business Basic at AU$10.50 per user per month in Australia, excluding GST, and Telstra’s Australian page shows Business Basic at $12.14 including GST on a 12 month term after the July 2026 rise. Those numbers matter at scale, but savings can disappear quickly if moving them creates fragmentation across mail, files, meetings and identity.

So for these users, start with downgrade and rationalisation before exit. Remove unused add-ons, check whether some seats need no Teams or no desktop apps, and only then test full alternative stacks. The goal is not to prove a point about Microsoft. It is to avoid swapping visible licence cost for hidden support cost.

This is also the point where finance leads should ask IT to quantify operational drag, not just subscription savings. How many helpdesk tickets will a split stack create. How much retraining is required. Which regulated records stay where. Which teams depend on external tenant collaboration. Those costs are real, even if they do not appear on the renewal invoice.

• Downgrade before exit for broad-collaboration users
• Count support and training cost alongside licence savings
• Protect external collaboration, file sharing and meeting workflows

07Questions to ask before you move any cohort off Microsoft 365

A vendor or internal team proposing a migration should be able to answer these questions clearly. If they cannot, you are not looking at a savings plan yet, just a licence reaction.

First, what exact Microsoft features are being replaced for this cohort, and which are simply being dropped because nobody uses them. Second, what data has to move, mailbox contents, contacts, calendars, files, recordings, or only future traffic. Third, which compliance or retention controls change when the cohort moves.

Fourth, what is the user cutover effort per person. A mail-only move may be minutes, a voice move with number porting and softphone retraining can be much more involved. Fifth, how will you protect deliverability, authentication and rollback. Sixth, what is the coexistence model while part of the estate remains on Microsoft 365.

If you need outside help, SyncTrix can be brought in as a delivery team for mail and related infrastructure changes, but the important thing is the scope discipline. A good migration partner will tell you which users not to move yet, not just how to move everybody.

For a more implementation-focused next step, /services/mail-infrastructure is the relevant service path, especially if your cost reduction plan involves partial exit, hybrid mail, archive decisions or a self-hosted design.

• Which users have the highest annual spend relative to actual feature use
• Which cohorts can move with less than one day of user disruption
• Which cohorts need a pilot because legal hold, PSTN or shift workflows complicate the cutover
• What is the fallback if mail flow, voice routing or mobile config goes wrong