Many Australian tenants have a hidden user class at renewal time: accounts that are barely used for work, but still carry a full Microsoft 365 licence because someone once said legal, audit or retention might need them. After Microsoft's commercial pricing updates took effect on 1 July 2026, that habit became harder to defend. The renewal question is no longer only "who needs email?" It is also "who is still licensed only because nobody redesigned compliance access?" This matters most in governance-heavy environments with long retention periods, investigations, regulated records and frequent requests from HR, legal, finance or internal audit. In those tenants, the wrong pattern is common: keep a departed user, low-activity contractor, archived project owner or dormant executive mailbox fully licensed just in case someone needs to search it later. Microsoft now provides cleaner patterns for several of these cases, especially inactive mailboxes retained under Microsoft 365 retention, and shared mailboxes where a separate licence is not needed up to 50 GB. The cost decision is not just about saving a seat. It is about reducing licence sprawl without breaking retention, eDiscovery, auditability or access control.
01Start with the right test: is this account paying for productivity, or only for future evidence?
A full user licence is usually defensible when the person actively uses Exchange, Teams, Office apps, OneDrive, device management or security controls tied to their daily work. It is much harder to defend when the account survives mainly because the organisation may need to keep messages, search them later, or let a small number of authorised staff inspect the data. Microsoft states that inactive mailboxes exist precisely to retain former employees' mailbox content after the account is removed, provided a hold is applied before deletion and the mailbox is then converted into an inactive mailbox that authorised staff can search and export through compliance tools](https://learn.microsoft.com/en-us/purview/inactive-mailboxes-in-office-365).
body
The practical screening question for IT and finance is simple: if you removed the end user's sign-in, desktop apps and day-to-day collaboration access tomorrow, would the business outcome still be met? If the answer is yes because the real requirement is retention, investigation, occasional lookup or mailbox continuity, you are looking at a redesign candidate, not a normal licensed user.
A useful three-part test is: who needs access, how often, and for what exact action. If the only real users are compliance officers, eDiscovery managers, HR, legal or a small admin team, that often points away from a full end-user licence. Microsoft notes that inactive mailbox contents can be accessed by authorised people with eDiscovery permissions, not by preserving the old user's normal working account](https://learn.microsoft.com/en-us/purview/create-and-manage-inactive-mailboxes).
- Keep a full licence when the person still works in the tenant and uses Microsoft 365 productively.
- Redesign when the account exists mainly for retention, evidence, mailbox continuity or rare admin lookups.
- Be precise about the required action: receive mail, send mail, search history, export evidence, or just retain data.
| User population | Typical reason licence survives | Usually better pattern | Key check before changing |
|---|---|---|---|
| Departed employee kept for legal or record retention | Need to preserve historical mailbox for years | Inactive mailbox under retention hold | Apply retention or other hold before deleting the account |
| Former executive or project lead with rare investigation requests | Occasional search by legal, HR or audit | Inactive mailbox plus eDiscovery access for authorised staff | Confirm who actually needs search and export rights |
| Shared operational address such as finance@ or reception@ | Continuity of incoming mail, multiple people handle it | Shared mailbox | Check size, archive, litigation hold and advanced compliance needs |
| Dormant service account with mailbox but no human workflow | Legacy notifications or system ownership | App redesign, shared mailbox or no mailbox at all | Map the sending, receiving and authentication dependency |
| Low-activity contractor or seasonal user kept only for occasional reading | Someone might need old messages later | Offboard to inactive mailbox if no ongoing work, or move function to shared mailbox | Decide whether they need active sign-in or only retained evidence |
02The clearest redesign case: ex-staff kept licensed only for archive or investigations
This is usually the first and largest pool. Microsoft says that when an employee leaves, mailbox data is normally recoverable for 30 days after account removal, but if a hold is applied before deletion, the mailbox becomes inactive and remains retained for the retention period](https://learn.microsoft.com/en-us/purview/inactive-mailboxes-in-office-365). Microsoft also says the mailbox must be licensed correctly so a hold can be applied before deletion, but after the user account is deleted, the Exchange Online licence becomes available to assign to a new user](https://learn.microsoft.com/en-us/purview/create-and-manage-inactive-mailboxes).
For an IT director, that means many ex-staff licences are a process failure, not a compliance requirement. The business requirement is usually one of four things: retain records for a fixed period, preserve material for litigation or investigations, search old content occasionally, or restore selected content later. None of those automatically requires the departed person to remain an active, licensed user.
The design work is operational rather than technical: define the offboarding trigger, ensure the right retention policy has been applied and has taken effect, document the hold confirmation step, delete the account in sequence, and give search rights only to authorised roles. Microsoft recommends using Microsoft 365 retention for this pattern rather than old in-place holds](https://learn.microsoft.com/en-us/purview/inactive-mailboxes-in-office-365).
In Australia, this redesign is often easier to justify than teams expect. The governance risk is not that former staff lose sign-in. The risk is poor retention discipline, unclear legal hold handling, and over-broad administrator access. The OAIC's guidance on the Notifiable Data Breaches scheme focuses on serious harm from unauthorised access, disclosure or loss. Carrying unnecessary live accounts increases the attack surface and can complicate breach response.
Where this becomes a board-level decision is scale. A tenant with dozens or hundreds of ex-staff accounts still carrying full suites is effectively funding a shadow archive platform through user licences. Renewal is the right point to quantify that and redesign the offboarding control. If you are already assessing mailbox estate changes, mail infrastructure work is the natural place to couple licence cleanup with retention workflow changes.
- Review every licensed account with no recent interactive sign-in and no current manager.
- Separate retention requirements from restoration requirements. Most mailboxes never need full restore.
- Require a named business owner for every ex-staff account left licensed beyond the offboarding window.
- Test one end-to-end inactive mailbox workflow before bulk remediation.
03Shared mailboxes are valid, but only for the right continuity cases
A second large category is the mailbox that no longer belongs to a person but still belongs to a function. Microsoft says shared mailboxes are intended for addresses such as support, reception and company information aliases, and that a shared mailbox can store up to 50 GB without a separate licence.
That makes shared mailboxes a strong answer when the requirement is ongoing operational continuity, not personal retention. If several licensed users need to read and send as the same address, this is usually cleaner than keeping a departed employee's mailbox alive. It also creates a cleaner access model because active staff use their own licensed identities to access the shared mailbox. Microsoft also notes that users accessing a shared mailbox must themselves have a licensed Exchange Online mailbox](https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes?view=o365-worldwide).
But finance teams should not assume every shared mailbox is free. Microsoft lists scenarios that require additional licensing, including a shared mailbox above 50 GB, in-place archiving, litigation hold, and some advanced compliance or security features](https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes?view=o365-worldwide). This is where redesign can go wrong. If a team converts personal mailboxes into shared mailboxes without checking size growth, archive needs, hold status and compliance features, it simply hides rather than removes the licensing problem.
The practical distinction is this: use an inactive mailbox when the person has gone and the need is evidence retention. Use a shared mailbox when the address still serves an active business function. If you mix the two, you usually end up with weak governance, poor ownership and avoidable licence exceptions.
If your estate already includes many no-reply, finance, HR or project addresses, related cleanup often overlaps with governance and compliance review and cloud infrastructure decisions, because mailbox type, access control and lifecycle policy all need to line up.
- Shared mailbox is a continuity pattern, not a legal archive pattern.
- Check 50 GB, archive, hold and advanced Purview needs before calling it licence-free.
- Do not leave personal mailboxes active when the business really needs a team-owned mailbox.
04Audit and occasional search needs usually belong to authorised reviewers, not end users
Many renewal debates become confused because people say the account must stay licensed for audit. In practice, audit and discovery usually belong to a small group of authorised reviewers, not to the dormant account owner. Microsoft says inactive mailbox contents can be searched and exported by people who have been granted eDiscovery permissions](https://learn.microsoft.com/en-us/purview/create-and-manage-inactive-mailboxes). Microsoft also documents that Purview search tools can search Exchange mailboxes for eDiscovery, and that search results can be exported in formats such as PST or individual messages](https://learn.microsoft.com/en-us/purview/edisc-search-mailboxes) and exported from eDiscovery cases.
That changes the licensing conversation. If the real use case is, "internal audit may need to inspect this mailbox twice a year", a full productivity suite for the dormant user is usually the wrong answer. The right answer is role-based access for the auditors or legal team, plus retained mailbox data in a searchable state.
There is a second governance point here. Microsoft Purview licensing guidance says Purview compliance capabilities are user-based and that organisations must appropriately license any user who directly or indirectly accesses, uses or benefits from a service, regardless of whether technical enforcement exists](https://www.microsoft.com/licensing/guidance/Microsoft-Purview). So the redesign should not be "remove licences and hope". It should be "license the people and features that genuinely use compliance services, and stop licensing the people who do not".
Microsoft also notes that Audit Standard is enabled by default for most Microsoft 365 organisations, while premium audit features need further setup](https://learn.microsoft.com/en-us/purview/audit-get-started). That matters for CFOs because not every governance scenario needs the most expensive feature path. The first job is to map which searches, exports, holds and retention actions are actually used, by whom, and how often. Often the surprise is that only a handful of compliance users need advanced rights, while a much larger tail of dormant accounts keeps carrying expensive suites with no active business use.
- Design for reviewer access, not ghost-user access.
- Check which Purview capabilities are actually required, not just historically enabled.
- Treat compliance licensing as role-based and evidence-based.
05Australian governance factors: retention discipline matters more than preserving live accounts
Australian organisations often over-license because they blend privacy, employment, legal and corporate record concerns into one blunt control: never fully offboard anything. That is understandable, but weak. The better approach is to define the record class and the retention path for each mailbox population.
On privacy, the OAIC notes that a private sector employer's handling of employee records for current and former employment relationships is exempt from the Australian Privacy Principles in certain circumstances](https://www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/organisations/employee-records-exemption). That exemption does not mean mailbox governance can be casual. It means you should separate the employment record question from the security and breach question. The OAIC's NDB guidance makes clear that covered entities must notify eligible breaches likely to cause serious harm](https://www.oaic.gov.au/privacy/notifiable-data-breaches). Too many dormant live accounts increase unnecessary exposure.
On corporate recordkeeping, section 286 of the Corporations Act 2001 requires companies to keep written financial records that correctly record and explain transactions and financial position and performance. That does not mean every record has to stay inside a licensed user mailbox forever. It means records must remain accurate, accessible and defensible. For many tenants, mailbox retention, export, and controlled restoration satisfy that outcome better than indefinite user licensing.
This is why the redesign conversation should involve legal, records, HR and finance early. The IT team should not decide retention classes alone, and finance should not cut dormant licences without checking the hold and search model. If these stakeholders are not aligned, you get the worst of both worlds: licence savings on paper, but ad hoc exports, side archives and emergency mailbox restores later.
- Do not use live licensing as a substitute for a records policy.
- Reduce breach exposure by removing unnecessary active accounts.
- Align HR offboarding, legal hold, records retention and IT deletion steps.
06A practical renewal review: what to check in 30 days
For most organisations, this review can be done as a controlled licensing and governance workstream rather than a major migration. The fastest path is to inventory the populations that survive mainly for compliance-only use and decide their target state.
Week 1: pull all licensed accounts with low activity, terminated HR status, no device use, or no recent sign-in. Group them into ex-staff, shared function addresses, seasonal users, contractors and system-linked mailboxes. Week 2: document the actual reason each group is still licensed, such as retention, mailbox continuity, archive size, legal hold, audit lookup or application dependency. Week 3: map each group to a target pattern, inactive mailbox, shared mailbox, active user, or application redesign. Week 4: pilot the change on a small cohort and validate retention, search, delegated access and restoration.
Ask your team or vendor these questions before you change anything:
A vendor who can support this work should be comfortable spanning Exchange, Purview, offboarding workflow and governance controls, not only mailbox moves. If the redesign exposes adjacent legacy dependencies, such as scanners, line-of-business notifications or brittle mail routing, it may need legacy modernisation, API integration or a broader technology consulting engagement rather than a narrow licence cleanup exercise.
- Which accounts are licensed with no current productive user?
- For each one, what exact business requirement justifies survival?
- Has a retention policy or hold been applied and confirmed before deletion?
- Who needs to search or export the content later, and are those people correctly licensed and permissioned?
- Is the mailbox really a shared business function that should become a shared mailbox?
- Does any mailbox require archive, litigation hold or advanced compliance features that change the licensing model?
- What application, relay or workflow still depends on the mailbox existing as a user object?
07What not to do at renewal
Do not bulk-remove licences from dormant users before confirming the hold and deletion sequence. Microsoft is explicit that to make a mailbox inactive, the mailbox must be licensed correctly so a hold can be applied before it is deleted](https://learn.microsoft.com/en-us/purview/create-and-manage-inactive-mailboxes).
Do not convert every historical mailbox into a shared mailbox. Shared mailboxes are for active shared functions, and licensing exceptions appear quickly once size, archiving, litigation hold or advanced compliance requirements are involved](https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes?view=o365-worldwide).
Do not let compliance teams rely on the fact that a feature is technically accessible without checking licensing guidance. Microsoft's Purview licensing guidance says proper licensing is required regardless of current technical enforcement](https://www.microsoft.com/licensing/guidance/Microsoft-Purview).
Do not leave this as an annual procurement exercise. Once the redesign is done, encode it in joiner-mover-leaver processes, records schedules, delegated admin roles and quarterly licence reviews. Otherwise, the same compliance-only users quietly reappear before the next renewal.
- No hold, no deletion.
- No shared mailbox by reflex.
- No assumption that dormant equals harmless.
- No procurement-only fix without governance changes.
Sources
- Microsoft 365 Packaging and Pricing Updates Public FAQ | Microsoft Licensing Resources
- Learn about inactive mailboxes | Microsoft Learn
- Create and manage inactive mailboxes | Microsoft Learn
- About shared mailboxes in Microsoft 365 - Microsoft 365 admin | Microsoft Learn
- Microsoft Purview Licensing Guidance
- Finding content in mailboxes in eDiscovery | Microsoft Learn
- Export search results in eDiscovery | Microsoft Learn
- Get started with auditing solutions | Microsoft Learn
- Employee records exemption | OAIC
- Notifiable Data Breaches | OAIC
- Part 4: Notifiable Data Breach (NDB) Scheme | OAIC
- CORPORATIONS ACT 2001 - SECT 286 Obligation to keep financial records
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.