If your Microsoft 365 renewal lands after 1 July 2026, you have a new cost review point. Microsoft says the commercial pricing update took effect for new and renewing customers from that date, and existing customers stay on current pricing until renewal (Microsoft Licensing Resources). That means every renewal is a fresh chance to ask a useful question before you touch active staff licences: how many paid user mailboxes are only being kept because they still contain old project correspondence, handover trails, approvals, client decisions or delivery history? This is a different problem from ex-staff mail, room accounts or shared mailboxes. In many Australian firms, the expensive waste sits inside still-licensed accounts owned by current staff, often project managers, delivery leads, operations staff or generic project identities that became personal over time. The account stays licensed, not because the person needs the full mailbox for current work, but because nobody wants to lose years of searchable project history. If that sounds familiar, the fastest renewal saving may be to separate active communication from retained history. The key is not to delete blindly. Under APP 11, an entity must take reasonable steps to protect personal information it holds and, where it no longer needs that information, take reasonable steps to destroy or de-identify it unless law or an order requires retention (OAIC Chapter 11). So the right move is a retention-led mailbox review, not just a cost-cutting exercise. For firms already reviewing mailbox categories, it helps to look at related licence waste patterns too, such as room mailboxes, scanners and no-reply accounts, shared mailboxes and service accounts, and ex-staff retention choices. This post focuses on the less obvious category: archived project mail that still sits inside paid user accounts.
01Why this mailbox category gets missed at renewal
Most licensing reviews start with headcount, leavers and obvious shared accounts. They often miss a quieter category: current users whose mailbox is acting partly as a records repository. The person may still be employed, but most of the mailbox storage and search value sits in completed projects, old client disputes, historical approvals or tender correspondence. The licence survives because nobody has broken out the historical record from the active mailbox.
That is exactly why these accounts matter at renewal. Microsoft’s pricing update applies from 1 July 2026 for new and renewing customers globally, and Microsoft’s published tables show higher list pricing for several suites, including Microsoft 365 Business Basic rising from US$6.00 to US$7.00, Business Standard from US$12.50 to US$14.00, Office 365 E3 from US$23.00 to US$26.00 and Microsoft 365 E3 from US$36.00 to US$39.00, with country and currency variation noted by Microsoft (Microsoft Licensing Resources). If you renew after 1 July 2026, every avoidable paid mailbox matters more than it did before.
In Australia, Microsoft’s own Exchange pricing page also makes the point that local prices vary by market and exclude GST, so finance teams should validate any saving against their actual tenant and channel price, not just US list numbers (Microsoft Australia Exchange pricing).
- Look for users with very large mailboxes but low current send volume
- Check accounts tied to completed projects, programmes, bids or major client migrations
- Check current staff who inherited old distribution lists or project aliases
- Check whether a mailbox is being kept for searchability, not for day-to-day communication
- Check whether project history could be retained under Purview retention instead of by keeping the user fully licensed
| Mailbox situation | Usually the better first move | What to confirm first |
|---|---|---|
| Current staff member actively using mailbox, but most historical content belongs to closed projects | Split active use from retained history, then reduce what must stay on a paid mailbox | Retention requirement, search needs, whether project history must remain discoverable |
| Mailbox only being kept so old project correspondence can be found later | Move to a retention-led inactive mailbox path if the mailbox can be retired | Whether a hold or retention policy is in place before deletion |
| Mailbox is still active but only needs archive access, not broad suite features | Compare lower-cost mail plan or archiving design against keeping full suite licensing | Current app needs, compliance features, mailbox growth, admin overhead |
| Project history no longer has a valid business or legal retention basis | Delete under approved retention schedule rather than preserve by default | Legal hold status, records schedule, APP 11 obligations |
02What Microsoft actually supports for retention, and what it does not
If the mailbox can truly be retired, Microsoft’s supported retention pattern is clear. Microsoft says making a mailbox inactive requires a hold on the mailbox and then deleting the mailbox or corresponding user account. After the user account is deleted, any Exchange Online licence associated with that user account becomes available to assign to a new user (Microsoft Learn, Create and manage inactive mailboxes).
Microsoft also says the recommended approach is to use Microsoft 365 retention to apply the hold. Its documentation explains that if you want to retain mailbox content indefinitely after a person leaves, or for a fixed period and then delete it, you apply the retention settings first and then remove the account (Microsoft Learn, Create and manage inactive mailboxes). That is useful because it shows the licensing principle: the licence is needed to put the mailbox into the right state before deletion, not forever afterwards.
For current project-history cases, that creates an important design question. If the person is still active, you cannot just convert their live mailbox into an inactive mailbox. You first need to decide whether the historical content should be separated, exported into a governed records system, kept in place for a defined period, or whether the project identity itself can be retired. Microsoft’s retention settings documentation also notes that retention policies can apply broadly across Exchange mailboxes, with options for all mailboxes or selected inclusions and exclusions (Microsoft Learn, retention settings). That makes targeted policy design possible, but it also means sloppy scoping can retain far more than intended.
What Microsoft does not support is the lazy middle ground many firms drift into: keep paying indefinitely for a live user mailbox simply because it is the easiest place to leave old project mail. That is operationally simple, but financially weak and poor from a records-governance perspective.
- Inactive mailbox is for a mailbox you are retiring, not a live mailbox still in daily use
- Apply hold or retention before account deletion, not after
- Design retention scopes carefully so you do not capture every mailbox unnecessarily
- Separate the question of business need from the question of technical convenience
03The real decision: archive in place, retire the mailbox, or delete on schedule
Before renewal, classify archived project mail into three buckets.
First, keep and search: some project mail genuinely has ongoing commercial, contractual or dispute value. If the mailbox itself can be retired, an inactive mailbox may be the cleanest Microsoft-native option because the retained content remains discoverable by authorised people for compliance or legal reasons, while the old user licence can be reused (Microsoft Learn, Create and manage inactive mailboxes).
Second, keep but not on a live user account: this is the category that produces savings fastest. The user still needs email, but the project history does not need to remain mixed into their everyday mailbox forever. Here, firms usually compare a lower-cost mailbox architecture, archive design, or migration of old project records into a governed repository. The right answer depends on search expectations, legal discovery needs and how often those old threads are actually accessed.
Third, dispose on schedule: if closed-project correspondence no longer has a valid retention basis, keeping it just because storage exists is the wrong default. OAIC guidance is explicit that where personal information is no longer needed for a permitted purpose, reasonable steps should be taken to destroy or de-identify it, unless an exception applies (OAIC Chapter 11).
This is why mailbox clean-up is not merely an IT licensing task. It needs records, legal and security input. If your team also supports broader tenancy and infrastructure decisions, a review across mail infrastructure, cloud infrastructure and governance and compliance usually gets to a cleaner answer faster than doing licence arithmetic in isolation.
- Do not preserve everything just because a search bar exists
- Retained history should have an owner, a retention basis and an access model
- If the mailbox cannot be retired, challenge whether all old project content really belongs there
- Treat current staff project-history mail separately from ex-staff mail
04A practical review process for Australian firms before renewal
A workable review takes one to three weeks for a mid-sized tenant if you keep the scope tight and use data rather than anecdotes. Start with mailbox analytics and stakeholder interviews, not migration scripts.
Step 1: identify candidate mailboxes. Look for licensed users with large mailbox size, high age profile of content, low recent send activity, or known ownership of completed projects. Finance can usually provide the licence baseline, while Exchange and Purview admins provide mailbox and retention visibility.
Step 2: classify the mailbox purpose. Ask whether the licence exists for active communication, compliance retention, delegated search, project handover history, or simple organisational caution. Those are different reasons and should not be funded the same way.
Step 3: check retention and legal posture. Confirm whether mailbox content is already under Microsoft 365 retention settings, whether any matter is under hold, and whether any industry or contractual retention schedule applies. This is also the point to map Australian privacy obligations around keeping personal information only while justified and protecting what you keep (OAIC Chapter 11).
Step 4: choose the target state per mailbox. Some stay licensed. Some should move to a lower-cost model. Some should become inactive mailboxes after the right retention step. Some should be deleted under policy. The mistake is forcing one answer across all historical project mail.
Step 5: run a pilot before the renewal date. Pick five to ten representative mailboxes, test search, delegation, legal access and user acceptance, then document the standard pattern. If the pilot shows heavy dependence on old project email for delivery operations, the review may lead into a wider technology consulting or mail redesign exercise rather than a pure licence reduction.
- Use actual mailbox data, not manager guesses
- Separate legal retention from convenience retention
- Pilot with high-volume project mailboxes first
- Document the access path for historical searches before moving anything
- Make finance, legal, records and IT approve the same target-state rule set
05Questions to ask your Microsoft partner or mail vendor
Many firms get poor advice here because they ask only for the cheapest licence mapping. Ask instead for a mailbox-category design with retention consequences.
A competent vendor should be able to explain which historical mailboxes can be retired into inactive mailboxes, which need live access, which can move under a different architecture, and what prerequisites exist before any licence is removed. They should also distinguish Microsoft-supported retention outcomes from improvised workarounds that look cheaper but create discovery or governance problems later.
Ask them to show the exact Microsoft source for every licence, hold and retention claim. That matters because published pricing, capabilities and support conditions do change. It also prevents the kind of drafting error that often slips into blog content and internal business cases, where a neat price point is repeated without a source.
If the answer stays vague, the vendor probably has not done the records side of the problem. SyncTrix can help with the mail and retention design work, but the useful test for any provider is whether they can reduce cost without weakening search, retention or privacy controls.
- Which mailbox categories can be removed from paid user licensing before active staff are touched?
- For each category, what is the supported Microsoft retention method?
- What exact prerequisite must exist before a mailbox can become inactive?
- How will authorised users search retained project history after the move?
- Which content should be deleted instead of archived, and on what policy basis?
- Which local prices, excluding GST or including GST, are you using in the business case, and where are they published?
- What admin effort and user change effort should we expect in the pilot and rollout?
06How to build the business case without inventing savings
Use only numbers you can source. Microsoft’s official pricing update gives you the renewal trigger and the published list-price change in USD for the affected commercial suites from 1 July 2026 (Microsoft Licensing Resources). Microsoft’s Australian pricing pages give you local list pricing for relevant standalone Exchange plans and explicitly state that listed prices do not include GST (Microsoft Australia Exchange pricing). Your reseller quote then becomes the final commercial input.
From there, the business case is straightforward. Count candidate mailboxes. Estimate how many can be retired, reduced or deleted after retention review. Multiply only by a sourced current or renewal-period price. Then set aside effort for policy validation, pilot, admin work, search testing and stakeholder sign-off. If you cannot source a price for a supposed intermediate add-on or archive option, leave that number out until your partner quotes it or Microsoft publishes it clearly.
The effort cost is usually not in tooling. It is in classification, policy checks and exception handling. That is why archived project mail is worth targeting early. The number of accounts may be smaller than active staff, but the change is often less disruptive because you are moving history first, not changing how current teams communicate today.
- Base the case on published Microsoft pricing and your own renewal quote
- Do not rely on uncited price points for add-ons or archive products
- Include governance and testing effort, not just licence deltas
- Savings are strongest where a mailbox can be retired or materially simplified without harming access
07When this move is worth doing first
Move archived project mail off licensed user accounts first when three conditions are true.
One, your renewal is after 1 July 2026, so the higher Microsoft commercial pricing is now relevant at renewal rather than theoretical (Microsoft Licensing Resources).
Two, you have a visible set of licensed accounts whose main reason for existing is retained project history, not active messaging. These are often easier to change than core executive, sales or engineering user accounts because the review is about historical access, not present-day productivity.
Three, you can make the retention basis explicit. If the content must be kept, design for governed retention and search. If it does not need to be kept, delete it properly. The expensive mistake is to fund indefinite mailbox licensing as a substitute for records decisions.
If that is your position, this category often deserves attention before you start licence disputes with active staff. It is less political, more defensible, and more likely to survive scrutiny from finance, legal and audit.
- Best first move when historical mail is the real reason the licence survives
- Less disruptive than changing active user toolsets first
- Produces a clearer governance outcome than leaving old project mail mixed into live accounts
- Works best when paired with a documented retention and search model
Sources
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.