Australia Microsoft 365 after the 1 July 2026 increase: when does archived staff mail cost too much to keep licensed?

01What changed after 1 July 2026, and why dormant mail suddenly matters

Microsoft’s pricing update took effect on 1 July 2026 for new purchases and renewals, and Microsoft states that existing customers stay on current pricing until renewal. That means two organisations with the same tenant can feel the increase at different times, depending on contract dates: Microsoft 365 Pricing and Packaging Updates, Microsoft 365 Packaging and Pricing Updates Public FAQ.

For Australian budgeting, the easiest concrete reference point is local partner pricing. Telstra lists Microsoft 365 Business Basic at $12.14 per user per month on a 12 month term from 1 July 2026, up from $10.40, while Business Premium shows no change at $38.01. Telstra notes those figures include GST. Even if your reseller price differs, the direction is the same: every dormant seat you leave in place now compounds through renewal cycles: Microsoft 365 pricing updates.

That is why low-activity mailboxes deserve separate treatment from active staff. If a mailbox no longer needs sign-in, mail flow, Teams, OneDrive, endpoint management, or day to day Outlook access, keeping a paid user licence on it is often an administrative habit rather than a requirement. Before you discuss self-hosting or export projects, review whether the mailbox should simply be converted into an inactive mailbox under the retention model you already own. For broader tenant clean-up, finance teams often pair this with a seat rationalisation review across active, shared and service identities: Microsoft 365 renewal in Australia: which users are expensive enough to move off first after the July 2026 change?, mail infrastructure services.

• Treat former staff, long-leave users, low-touch retained accounts and legal hold custodians as separate cost categories
• Review mailbox purpose before reviewing licence tier
• Model costs at renewal date, not announcement date

02The cheapest legitimate option is often an inactive mailbox, not a live licence

Microsoft says an inactive mailbox lets you retain a former employee’s email after they leave, and authorised compliance or records staff can search and export that content. Microsoft also states that to make a mailbox inactive, a hold must be in place before the mailbox or account is deleted, and after the user account is deleted the Exchange Online licence becomes available for reassignment: Create and manage inactive mailboxes.

Microsoft also explains the timing risk. When you remove the Microsoft 365 account, mailbox data is retained for 30 days. After that, it is permanently removed unless a hold had already been applied. If the hold exists first, the mailbox becomes inactive and is retained for the hold duration. Microsoft recommends using Microsoft 365 retention policies or retention labels for this process: Learn about inactive mailboxes.

That matters because many finance teams assume they have only two choices: keep paying for the user, or export everything somewhere else. In practice there is a third option, usually the better one, where the mailbox remains in Microsoft 365 for legal and records purposes without consuming the former user’s ongoing licence. For ex-staff estates, that is typically the first cost crossover to test.

There are limits to this strategy. Inactive mailboxes cannot receive email and are not normal end-user mailboxes. They are for retention, search, export and potential recovery workflows, not for somebody casually opening Outlook next month. If HR, payroll or line managers still expect a live mailbox to be monitored, you have not reached the inactive mailbox state yet. You may need a shared mailbox design, delegation model, or a real active licence instead. If you are sorting these edge cases alongside other low-use identities, this related review helps frame the same cost question for shared and service accounts: Australia Microsoft 365 renewal after July 2026: which shared mailboxes and service accounts should leave first?.

• Apply retention hold before deleting the account
• Confirm the hold is active before licence removal
• Expect compliance access, not day to day user access
• Do not treat an inactive mailbox as a backup strategy

03When keeping the licence is still justified

You should usually keep a paid Microsoft 365 licence when the mailbox still needs normal user behaviour. That includes sign-in, sending and receiving mail, delegated access patterns built around a user identity, Teams or calendar continuity, OneDrive retention tied to the user lifecycle, or return-to-work scenarios where rebuilding later will create more operational risk than the licence saves.

Long-leave users are the classic example. If a person is on parental leave, secondment, extended medical leave or a fixed-term absence, deleting the account just to save a licence can create needless rework. If they are expected to return to the same mailbox, keep the account if the business expects continuity of access, calendar, mobile setup and identity. The same applies to executives or regulated roles where assistants still need live mailbox workflows rather than retrospective search.

Archive size is another trap. Microsoft documents that Exchange Online archive mailboxes provide extra storage, with up to 100 GB initially available after enabling archive, and auto-expanding archiving providing up to 1.5 TB, with Microsoft increasing the maximum for eligible mailboxes from 1.5 TB to 3 TB. That storage can make Microsoft 365 economically sensible for large retained mailboxes that still need direct user access, because the storage burden is bundled into the service you already operate: Learn about auto-expanding archiving, Enable auto-expanding archiving, Enable archive mailboxes for Microsoft 365.

So the question is not only licence cost. It is whether the mailbox still needs interactive service. If yes, compare Microsoft 365’s ongoing cost with the real effort of redesigning access, archive, retention, security controls and support. If no, inactive mailbox is usually the cleaner route.

• Keep licensed if the mailbox still needs sign-in
• Keep licensed if assistants or delegates need live workflow continuity
• Keep licensed if the person is likely to return and you want low-friction reinstatement
• Re-test storage-heavy users separately because Microsoft archive capacity can change the economics

04When self-hosting or moving archived mail off Microsoft 365 starts to make sense

Self-hosting is usually not the first answer for a few ex-staff mailboxes. It starts to make sense when dormant mail is part of a wider platform decision: large numbers of low-activity mailboxes, a broader move away from per-seat SaaS licensing, strong internal mail operations capability, and a clear design for security, backup, patching, monitoring and compliance.

The hidden mistake is comparing only licence spend with server spend. For dormant mail, you must also compare the cost of preserving searchability, legal hold behaviour, export workflows, mailbox restore options, identity boundaries and mail hygiene. Microsoft keeps all of that inside the service. If you self-host retained mail, your team now owns those controls, the operational runbook and the risk. In Australia that risk has become harder to dismiss, especially for teams still considering on-prem Exchange or similar legacy mail stacks. The security control burden is not theoretical, and it should be assessed alongside current ACSC-oriented hardening expectations and patch discipline: Self-hosted Exchange in Australia: what controls should you add first after the latest ACSC guidance?, Self-hosted Exchange in Australia after September 2026 guidance: keep it or get out?.

A useful threshold is organisational, not technical. If your review finds a handful of former staff mailboxes, fix them with inactive mailboxes. If it finds hundreds of low-value licensed seats, mixed with shared accounts, kiosk users, service accounts and historical mail, then the issue is your mail platform shape. That is where a mailbox redesign, archive strategy and possible partial self-hosting programme can be worth serious modelling, especially if it sits with a wider cloud infrastructure or governance review.

• Self-hosting makes more sense at estate level, not one mailbox at a time
• Do not compare licence cost with storage cost only
• Include security operations, compliance handling, backup and restores in the model
• Treat archived mail as part of mail architecture, not just procurement

05A finance and infrastructure checklist: calculate the crossover properly

Start with three counts: ex-employees still holding paid licences, long-leave or suspended users on paid licences, and low-activity active users with oversized historical mailboxes. Then separate them by business need: retain only, occasional compliance access, occasional business access, or full interactive access. Without that split, any cost model will be wrong because it assumes all dormant mailboxes need the same outcome.

Next, document what licence capability is actually being used. Microsoft’s documentation makes an important distinction: the mailbox must be licensed correctly before deletion so that hold can be applied, but once the account is deleted and the mailbox is inactive, the Exchange Online licence becomes available to reuse: Create and manage inactive mailboxes. If you skip that step and discover it after deletion, you can lose the low-cost path entirely.

For Australian buyers, use your real renewal pricing, not US list prices from a product page. Telstra’s current public figures are a usable benchmark if you need a quick external reference, but your reseller and term will vary: Microsoft 365 pricing updates. Multiply that by 12 and then by the number of mailboxes in each category. Compare it with the one-off engineering and admin effort to convert mailboxes properly now.

Then estimate effort, not just software. A sensible mailbox rationalisation project usually needs inventory, policy review, retention validation, pilot conversions, legal sign-off, access model changes, and helpdesk documentation. Even a modest programme can take several weeks of part-time work across infrastructure, security, compliance and finance. If you are evaluating an external delivery team, ask them to price the decision and migration work separately from ongoing support. That keeps the business case honest, whether you stay in Microsoft 365 or redesign part of the estate.

• Count by mailbox purpose, not by licence SKU only
• Use renewal pricing in AUD including your actual term assumptions
• Check whether retention and hold are already configured correctly
• Estimate internal labour and compliance review time
• Price one-off clean-up separately from recurring run operations

06Questions to ask before you remove licences or choose self-hosting

Ask your compliance owner: which former staff mailboxes must remain searchable, for how long, and by whom? Microsoft inactive mailbox guidance supports compliance search and export use cases, but only if the hold exists before deletion: Learn about inactive mailboxes, Create and manage inactive mailboxes.

Ask infrastructure: does this mailbox need human access, or only retention? If it still needs a person in Outlook, an inactive mailbox is not the right state. If it only needs legal, records or audit access, paying for a live user licence is often hard to justify.

Ask security: if we move archived mail off Microsoft 365, who owns patching, authentication, monitoring, anti-malware controls, backup validation and restore testing? If the answer is vague, the self-hosted option is not ready.

Ask procurement and finance: are we solving a few accidental licences, or redesigning mail economics for a meaningful part of the estate? If it is only a few seats, fix the process. If it is a structural cost bucket, run it as an architecture and operating model decision.

If you want a quick rule of thumb, use this one. Former staff mailboxes that only need retention should usually not stay on paid user licences after the 1 July 2026 increase. Convert them properly to inactive mailboxes and reclaim the seats. Keep licensing only where the mailbox still behaves like a real user mailbox. Consider self-hosting only when the dormant mail problem is large enough that you are rethinking the whole mail estate, not just tidying leftovers. That is typically the point where a specialist team such as SyncTrix can help assess the technical and commercial trade-offs without jumping straight to a migration.

• What exact retention obligation applies to each mailbox?
• Who still needs direct mailbox access?
• Has hold been applied before deletion?
• What security controls must be recreated outside Microsoft 365?
• Is this a process fix or a platform redesign?