If you are reviewing former-employee mail after the 1 July 2026 Microsoft 365 pricing change, the wrong choice is usually not technical, it is governance. A shared mailbox looks simple because people can open it in Outlook. An inactive mailbox looks less convenient because it sits behind Microsoft Purview and eDiscovery. But Microsoft positions inactive mailboxes for retaining former employees’ email, and shared mailboxes for ongoing multi-user operational addresses such as support or reception. The practical decision is this: do you need retained mail for compliance and discovery, or do you need a live mailbox that other staff still use day to day? This post compares the two for Australian IT and compliance leads who want to remove paid licences without losing retention coverage, archive access or legal defensibility. The pressure is higher now because Microsoft’s commercial suite and standalone pricing updates took effect on 1 July 2026, applying to new and renewing customers globally.
01Start with Microsoft’s intended use case, not the cheapest-looking mailbox
Microsoft’s own documentation draws a clear line. Shared mailboxes are for addresses used by multiple people, such as support, reception and other common-function mailboxes. By contrast, inactive mailboxes are specifically for retaining a former employee’s email after the account is deleted, provided a hold is applied before deletion.
For an ex-staff account, that distinction matters. If the person has left and the mailbox is no longer meant to send or receive normal business mail, an inactive mailbox is the cleaner retention pattern. It lets you delete the user account and free the Exchange Online licence after the hold is in place. Microsoft says the mailbox then remains preserved for the duration of the retention period, or indefinitely if your retention settings require that, and can be searched by authorised personnel through compliance tools rather than treated as a live mailbox in the GAL.
A shared mailbox is the better fit only if the mailbox is still operational. Typical examples are where an employee mailbox is being deliberately repurposed into a team address during a transition, or where a role account is genuinely still active and other licensed users need direct Outlook access. If the real requirement is evidence preservation, search, export and controlled access, using a shared mailbox as a retention shortcut usually creates more policy drift than it saves. If you are already reviewing other low-value paid mailboxes, this sits alongside the same rationalisation work covered in Australia Microsoft 365 renewal after July 2026: which shared mailboxes and service accounts should leave first?.
- Use an inactive mailbox when the employee has left and the need is retention, legal hold, eDiscovery or records access.
- Use a shared mailbox when the mailbox is still actively used by multiple current staff.
- Do not choose a shared mailbox just because it feels easier to open in Outlook.
02What you actually save after the July 2026 increase
The cost trigger is straightforward. Microsoft’s public FAQ states that the new commercial pricing became effective on 1 July 2026, and applies to both new and renewing customers globally. It specifically lists impacts across products including Microsoft 365 E3 and E5, Office 365 E3 and E5, Microsoft 365 Business Basic and Business Standard, Microsoft 365 Apps, Frontline plans, EMS, Windows and other standalones. For many organisations, that moved former-staff mail from a tolerated waste line to a renewal issue.
An inactive mailbox can reduce recurring licence cost because Microsoft says the mailbox must be licensed correctly only so a hold can be applied before deletion, and after the user account is deleted the Exchange Online licence becomes available to assign to a new user, as described in Create and manage inactive mailboxes. In other words, you preserve the retained data without continuing to pay for that departed user’s active mailbox seat.
A shared mailbox can also avoid a separate mailbox licence, but only within limits. Microsoft says an unlicensed shared mailbox can store up to 50 GB. If you need more than 50 GB, the shared mailbox must be assigned Exchange Online Plan 2 to reach 100 GB. If you need in-place archiving, auto-expanding archiving, or litigation hold on the shared mailbox, Microsoft also requires licensing such as Exchange Online Plan 2, or Exchange Online Plan 1 with the Exchange Online Archiving add-on. That is where the apparent savings often disappear.
So the savings question is not simply shared versus inactive. It is this: will your ex-staff mailbox remain under 50 GB with no archive and no hold, and do you genuinely want it to stay operational? If not, the shared mailbox route often becomes a disguised licensed mailbox with weaker governance.
| Scenario | Inactive mailbox | Shared mailbox |
|---|---|---|
| Former employee, retention required for years | Strong fit, hold before deletion, licence can be reallocated | Weak fit unless mailbox must stay live |
| Mailbox still used by several current staff | Poor fit, not a live collaboration mailbox | Strong fit |
| Mailbox over 50 GB | Can fit retention use case if hold exists before deletion | Needs a licence above 50 GB |
| Need archive capability | Possible, but check archive and restore limitations carefully | Needs qualifying licence for archiving |
| Need legal hold or defensible eDiscovery | Strong fit through Purview retention and eDiscovery | Needs qualifying licence and is usually harder to justify as an ex-staff mailbox |
| Need someone to read mail in Outlook every day | Not the main operating model | Strong fit if still a live mailbox |
03Where shared mailboxes go wrong for former staff
The most common mistake is converting every departed user to a shared mailbox because managers want easy access. That solves short-term convenience but can create four longer-term problems.
First, storage. Microsoft documents that shared mailboxes are limited to 50 GB without a licence. Many long-serving staff mailboxes exceed that, especially if archives were enabled. Once the mailbox is above 50 GB, you are back into paid licensing.
Second, compliance features. Microsoft states that to place a shared mailbox on litigation hold, the shared mailbox must have Exchange Online Plan 2, or Exchange Online Plan 1 with Exchange Online Archiving. The same licensing logic applies if you need archive growth or advanced Purview capabilities. If the mailbox matters enough to preserve formally, the cheap shared mailbox usually stops being cheap.
Third, operational ambiguity. A shared mailbox is meant to be used by multiple current staff. Once a former employee mailbox is converted into that form, your environment starts to blur the line between records retention and active communications. That can affect mailbox ownership, access approvals, naming conventions and user expectations. The cleanup work often lands later with your governance and compliance team, not at renewal time when the shortcut was taken.
Fourth, discoverability and principle of least privilege. Shared mailbox access is often delegated broadly to managers or assistants. Inactive mailboxes, by contrast, are intended for access by authorised administrators, compliance officers and records managers through Content Search and eDiscovery processes. That is usually a better fit for HR disputes, legal matters and regulated records handling.
- Check mailbox size before any conversion decision.
- Check whether archive, litigation hold or retention already exists.
- Check who really needs access, daily users or only authorised compliance staff.
- Check whether the mailbox is evidence to preserve, or a live operational inbox to keep running.
04Where inactive mailboxes are the better answer, and the catches to watch
Inactive mailboxes are purpose-built for the ex-staff scenario. Microsoft says a mailbox becomes inactive when a hold is applied before the Microsoft 365 account is deleted. After deletion, the mailbox is preserved according to the applied retention settings and can be retained for a fixed period or indefinitely through Microsoft 365 retention policies or retention labels.
This is usually the strongest answer when your requirement is one of these: keep former employee mail for a defined records period, preserve potential evidence, remove the licence, keep the mailbox out of normal address lists, and allow only controlled compliance access. It also aligns with Microsoft’s recommendation to use Microsoft 365 retention rather than older Exchange in-place hold methods, which Microsoft notes are retired for new creation and modification scenarios.
There are still catches. The first is sequencing. The hold must be applied and allowed to take effect before you delete the account. If you simply delete the user without the hold in place, Microsoft says the mailbox data is retained for 30 days, after which it is permanently removed.
The second catch is access model. Inactive mailboxes are not normal live mailboxes. Microsoft says they cannot receive email and are not displayed in the shared address book. Access is through eDiscovery and content search workflows, or through restore and recovery actions when needed. If your HR team expects to click directly into the mailbox every day, you need to redesign the access process, not force the wrong mailbox type.
The third catch is archive behaviour. Microsoft’s guidance on auto-expanding archiving says that after this feature is enabled, it cannot be turned off, and it prevents administrators from recovering or restoring an inactive mailbox in the usual way. In that case, recovery is limited to content search export and import. If former employees have large archives, you should review archive state before standardising your offboarding runbook. If you need help mapping that runbook into your tenant operations, it often sits with the same mail and tenant engineering work as mail infrastructure services and broader cloud infrastructure.
05A practical decision framework for Australian IT and compliance leads
For most Australian organisations, the decision is less about local law changing the Microsoft feature set, and more about internal defensibility. You need to show that ex-staff mail is handled consistently, access is controlled, and licence reduction did not weaken retention or legal response.
Use this simple framework.
Question 1: Is the mailbox still an active business address used by current staff? If yes, shared mailbox is likely appropriate. If no, keep going.
Question 2: Is there a retention, legal, HR, audit or records requirement after departure? If yes, inactive mailbox is usually the right default.
Question 3: Does anyone need day-to-day Outlook-style access, or only occasional controlled search and export? If it is occasional and controlled, inactive mailbox fits better. If it is daily operational use, shared mailbox may still be justified.
Question 4: Is the mailbox or archive above 50 GB, or already using archiving or hold? If yes, test the licensing consequences of the shared mailbox path before calling it a saving.
Question 5: Do you have a documented offboarding workflow that checks holds, retention assignment, mailbox size, archive state, delegated access removal and audit trail? If not, fix the process before bulk licence cleanup. This is the same kind of rationalisation discipline discussed in Australia Microsoft 365 after the 1 July 2026 increase: when does archived staff mail cost too much to keep licensed?.
If you run a mixed estate, it can be worth classifying former-employee mailboxes into three buckets: operational reassignment, formal retention, and export-and-delete. Only the first bucket should commonly become shared mailboxes.
- Operational reassignment: convert only where the mailbox stays live for current staff.
- Formal retention: hold, delete user, keep as inactive mailbox.
- Export-and-delete: use only where policy allows no ongoing cloud retention need.
06What to ask your Microsoft partner or internal admin team before you switch
Before you remove licences at scale, ask these questions and insist on written answers tied to Microsoft documentation.
What exact retention policy or retention label will create the inactive mailbox, and how will you confirm it applied before deletion? Microsoft explicitly says the hold must be in place before the account is removed, in Learn about inactive mailboxes.
How will you handle mailboxes with archive mailboxes or auto-expanding archiving already enabled? Microsoft’s auto-expanding archiving guidance changes what can later be recovered or restored.
Which shared mailboxes would still require paid licensing because they exceed 50 GB, need archiving, or need litigation hold? Microsoft lists each of those triggers in About shared mailboxes in Microsoft 365.
Who will have permission to search and export inactive mailboxes, and is that aligned with HR, legal and records roles? Microsoft states that inactive mailboxes are accessed by authorised people granted eDiscovery permissions in Create and manage inactive mailboxes.
What is your exception path when a departed employee returns, or another person inherits the role? Microsoft provides specific recover and restore options for inactive mailboxes, and those options should be part of your runbook.
How will you evidence the decision for auditors or employment disputes? A simple matrix showing mailbox purpose, retention basis, selected mailbox type and approver is often enough, but only if it is applied consistently.
07The short answer: default to inactive mailbox for ex-staff retention, use shared mailbox only for live operational reuse
If the mailbox belongs to someone who has left and your goal is to cut licence cost without breaking retention or discovery, inactive mailbox should usually be your default. That is the model Microsoft documents for former employees, and it is the cleaner way to preserve content while reallocating the user licence after deletion.
Choose a shared mailbox only where the mailbox is genuinely staying in service for current staff, and you have checked the licensing consequences of size, archiving and hold requirements. Otherwise you risk paying nearly as much while making the governance story worse.
For teams that need help turning this into a repeatable offboarding pattern, SyncTrix can support the mailbox, retention and handover workflow through its mail infrastructure service. The practical deliverable should be a runbook, not just a one-off clean-up: classify mailbox purpose, apply hold where required, confirm retention, remove the user, document access, and review exceptions monthly.
Sources
- Microsoft 365 Packaging and Pricing Updates Public FAQ | Microsoft Licensing Resources
- About shared mailboxes in Microsoft 365 - Microsoft 365 admin
- Create and manage inactive mailboxes | Microsoft Learn
- Learn about inactive mailboxes | Microsoft Learn
- Enable auto-expanding archiving | Microsoft Learn
- Exchange Online Archiving service description | Microsoft Learn
- Recover an inactive mailbox | Microsoft Learn
- Restore an inactive mailbox | 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.