Microsoft 365 renewal after 1 July 2026: which users should leave first if you are cutting per-seat cost in Australia

01Start with a cohort map, not a tenant-wide argument

The fastest way to waste time is to ask whether the whole company should stay on Microsoft 365. Most organisations do not have one user type. Microsoft’s own frontline guidance assumes mixed licensing across information workers and frontline workers, because different users need different tools and device models Understand frontline worker user types and licensing. That same logic applies when you are moving users off per-seat cost.

Build a simple four-column inventory before you touch licensing: current SKU, mailbox dependency, document collaboration dependency, and compliance dependency. Mailbox dependency means the user needs a personal Exchange mailbox and calendar. Collaboration dependency means they actively use desktop Office apps, OneDrive, SharePoint and Teams as daily workflow tools. Compliance dependency means legal hold, advanced retention, eDiscovery, or archive requirements would make a cheap move false economy.

If you need help framing the mail and platform split as an engineering programme rather than a one-off licence exercise, this is usually where technology consulting and cloud infrastructure work starts to matter.

• Do not segment by department first, segment by actual workload
• Mark every user as mailbox-heavy, mailbox-light, or mailbox-none
• Separate personal mailbox users from role mailbox users
• Flag regulated and executive users before any cost exercise
• Record which users only need identity plus a few SaaS logins

02Leave role accounts first, because they are often not real users at all

A surprising amount of Microsoft 365 spend sits in accounts that should never have been treated as personal users. Shared mailboxes are the obvious example. Microsoft states that a shared mailbox can store up to 50 GB without assigning a licence to it. It only needs extra licensing if it goes above 50 GB, needs archiving, or is placed on litigation hold About shared mailboxes in Microsoft 365.

That makes role addresses the safest first clean-up step before any user migration. If support@, reception@ or salesadmin@ are currently attached to full user licences, remove the personal-user assumption first. Convert where appropriate, delegate access to a smaller number of licensed users, and document whether any of those mailboxes require more than 50 GB, in-place archive, or hold. Microsoft says a shared mailbox over 50 GB needs Exchange Online Plan 2, and archive or hold also require additional licensing paths About shared mailboxes in Microsoft 365.

This step is not glamorous, but it is low risk and usually uncovers duplicate spend, former staff mailboxes still licensed as live users, and team inboxes nobody owns properly. It also gives you a cleaner baseline before deciding which real people should move.

• List all mailboxes with no recent interactive sign-in
• Find every mailbox attached to a role, queue or function
• Check size, archive status and hold status before changing licence
• Confirm who needs send-as or send-on-behalf rights
• Document any workflow or CRM integration tied to that mailbox

03Next, move mailbox-light frontline and occasional users

After role accounts, the next best candidates are users whose work is operational rather than document-centric. Microsoft describes frontline users as people who often work on tablets or phones and need quick access to communication, tasks and information on the go Understand frontline worker user types and licensing. In practice, some of these users do not need a full Microsoft mailbox and app stack forever, especially if their core systems are line-of-business tools, rosters, mobile apps, shared devices, or non-Microsoft collaboration platforms.

Why this cohort first? Because the business risk is usually lower. These users often have less PST history, fewer calendar delegates, fewer complex mailbox rules, and less dependency on desktop Office. They also tend to be more tolerant of a changed mail experience if their core work already happens elsewhere. At the same time, the 2026 list price rise on Microsoft 365 F3 is one of the more visible ones, from $8 to $10 with Teams, and from $6.93 to $8.93 without Teams Microsoft 365 Pricing and Packaging Updates.

The key is not to move every frontline user. Keep licensed any user who needs a personal Exchange mailbox for shift coordination, compliance capture, or manager communication. Move the truly mailbox-light group first: casual workers, kiosk-style users, project contractors, and staff who only receive occasional notices and can work via alternative identity, portal or shared-mailbox access.

• Pick a pilot group with low calendar usage
• Exclude managers with delegated mailbox access
• Exclude anyone under hold or active HR case management
• Test mobile access, password reset and directory sync before cutover
• Measure service desk tickets during a 2 to 4 week pilot

04Then deal with inactive, retained and legacy mailboxes

The third group to leave is not always a group of active workers. It is often a pile of old accounts: departed staff, low-activity contractors, long-tail project addresses, and mailboxes kept for legal or operational history. These often survive renewals because nobody wants to touch them. That is exactly why they should be an early wave after the low-risk active users.

The decision here is structural. Some accounts should be converted to shared mailboxes, some should be exported under your retention policy, some should remain licensed because of hold or archive requirements, and some should be moved to a different archive strategy. Microsoft’s shared mailbox guidance is clear that archive and litigation hold change the licence requirement About shared mailboxes in Microsoft 365. Microsoft also documents auto-expanding archiving up to 1.5 TB, with a current note that eligible mailboxes are increasing to 3 TB, which matters if you have users whose retained mail volume is driving expensive stay decisions Enable auto-expanding archiving.

This is the point where finance often sees the first serious savings, because you stop paying for historical clutter as if it were active productivity. But this wave needs legal and records input. A badly handled archive cut is harder to reverse than a live user migration.

• Review licence assignment for every disabled account
• Map each inactive mailbox to delete, export, shared, archive, or retain
• Get legal sign-off on retention categories
• Test eDiscovery and restore path before removing licences
• Document chain of custody for exported mail data if regulated

05Only after that, target apps-only users and split mail from productivity

Some estates have a group that needs Office apps but does not need Exchange Online. Microsoft’s own admin guidance says Microsoft 365 Apps for business does not include email About shared mailboxes in Microsoft 365. That matters because it lets you separate two questions buyers often bundle together: who needs business email, and who needs Office apps.

Be careful though. Apps-only users are not always the best first move. The July 2026 list price for Apps for Business rises from $8.25 to $10 Microsoft 365 Pricing and Packaging Updates, so there is clear budget pressure, but the migration work can be messy if local file workflows, macros, OneDrive sync, Teams meeting add-ins, or Outlook profile assumptions are still embedded in day-to-day work. That is why this cohort is usually fourth, not first.

Where this group is attractive is in controlled environments: call centres using a separate CRM, finance users with fixed desktop workflows, or teams already running non-Microsoft email but retaining Office for documents. If your strategy is to reduce Microsoft to an apps layer for selected users while taking mail elsewhere, design the identity, autodiscover, mobile config and archive path properly. This is where mail infrastructure, API integration and governance and compliance can stop a licensing exercise turning into a user support backlog.

• Confirm whether the user truly needs desktop apps or only web viewing
• Check dependencies on OneDrive known folder move and Teams add-ins
• Test Outlook profile behaviour if Exchange is removed
• Review macro, template and plugin dependencies
• Plan coexistence for contacts, calendars and mobile devices

06Keep the complex users until last: executives, regulated teams, and collaboration-heavy staff

The most expensive users are not automatically the first users to move. In many organisations, they should be last. Executives, legal, finance leadership, sales leadership, project coordinators, and regulated teams usually have the most painful dependency stack: shared calendars, delegates, mailbox rules, mobile device policies, archive, hold, Teams workflows, document permissions, and security tooling.

Microsoft’s 2026 update is explicitly tied to added value in security, compliance, AI and IT management Microsoft 365 Packaging and Pricing Updates FAQ. Whether you value those additions or not, the practical point is this: if you remove Microsoft 365 from users who rely on those integrated controls, you are not just cutting mail cost. You are replacing a connected bundle of workflow, governance and support assumptions.

So treat this last cohort as a separate business case. Some of these users should stay. Others can move, but only after you have proven coexistence, archive access, delegated calendar behaviour, device management and security controls elsewhere. If you are specifically weighing self-hosted or hybrid mail paths for Australia, these related posts may help frame that next stage: Microsoft 365 renewal shock in Australia: should you self-host mail now? and Microsoft 365 E3 vs self-hosted mail in Australia after the 1 July 2026 price change.

• Executives and executive assistants
• Users with delegated mailbox or calendar rights
• Users on legal hold or advanced retention
• Security-sensitive admins and privileged users
• Teams that live inside SharePoint and OneDrive collaboration

07Questions to ask before you sign a vendor or internal migration plan

A seat-reduction programme fails when the commercial goal outruns the operating model. Before you approve a migration sequence, ask questions that expose hidden effort.

First, ask about coexistence. Can the proposed target support staged coexistence for mail flow, calendar lookups, mobile devices and address books, or does it assume a big-bang cutover? Second, ask about archive and compliance. Exactly how will retained mail be accessed, searched and exported, and what licence or infrastructure assumptions sit behind that? Third, ask about support load. What is the expected ticket curve for each wave, and which wave is likely to trigger Outlook, mobile or identity issues?

Also ask for a user-by-user exception process. The cheapest plan on paper becomes expensive if every manager can override the cohort logic. Require an exception register with reasons such as delegated calendar, legal hold, mobile MDM requirement, line-of-business plugin, or regulatory retention. That keeps the programme honest.

If you need an external team to run the technical work in phases rather than as a rushed renewal response, SyncTrix can support the mail and migration engineering side through its mail infrastructure service.

• What percentage of accounts can be removed before any live-user migration starts
• Which cohorts can move with no calendar coexistence requirement
• How are shared mailboxes, archives and ex-staff accounts handled
• What exact rollback exists for each migration wave
• Which users are declared out of scope for phase one and why