Meet Sarah, the sole IT administrator at Halcyon Legal, a 120-person law firm with offices in Melbourne and Brisbane. Sarah manages the firm's Microsoft 365 environment including SharePoint Online, Exchange, and Teams. The firm's SharePoint tenant holds matter documents, HR records, precedent libraries, and internal knowledge bases built up over eight years of active use.
The situation
Sarah received an automated alert: the firm's SharePoint Online storage was at 89% of its allocated quota. A quarterly IT budget review was three weeks away, and the CFO had announced a cost freeze on all discretionary spend for the following quarter. Purchasing additional Microsoft 365 storage was technically possible, but getting it approved in the current climate would take time Sarah did not have.
Her options were either to find the storage somewhere within the existing allocation or to start preparing a business case for additional quota that might not be approved before the tenant hit its limit.
What the environment looked like
- Eight active team sites covering different practice areas, plus an intranet home site.
- Versioning enabled on all document libraries with no version cap set.
- Libraries in active use for legal drafting, with some documents going through 200 to 300 save cycles during litigation preparation.
- Recycling bin not cleared in over fourteen months.
- Approximately 450 GB used of a 500 GB allocated quota.
Sarah knew version history was probably part of the story, but the SharePoint admin center's storage report only showed total usage per site. It gave no breakdown of how much was live content versus version history versus recycling bin. She needed a more detailed picture before deciding where to act.
Phase 1: Get a real storage breakdown with Report Master
Understand the breakdown before you act
Sarah connected ShareMaster to the Halcyon Legal tenant and ran Report Master across all nine sites. The Excel export gave her a storage breakdown per site and per library, split into three buckets:
- Live content: the current file versions actually in use.
- Version history: all historical versions stored behind the scenes.
- Recycling bin: deleted items still within the 93-day retention window.
The results were immediately revealing:
- Version history accounted for 54% of total storage across all sites.
- Three litigation support libraries alone represented 65% of all version history by volume.
- The recycling bin held 38 GB that had never been cleared, largely outdated draft files from completed matters.
Live content (the files actually being worked on) was only 172 GB. The rest of the quota was occupied by history and bin entries.
Phase 2: Trim version history with Space Master
Reclaim the bulk of the storage
Sarah consulted with the firm's managing partner and practice group leads. The consensus was that keeping 15 major versions per file was more than adequate for their audit needs. No regulatory requirement mandated a longer version history for the types of documents in those libraries.
She opened Space Master and ran the Version Trimmer across all eight team sites with a keep count of 15. The three heavy litigation libraries were prioritised first. The trim ran overnight on a Thursday.
By Friday morning, version storage across the tenant had dropped from 243 GB to approximately 42 GB. The three litigation libraries went from a combined 158 GB of version history to under 28 GB.
Phase 3: Clear the Recycling Bin with Recycle Master
Recover the remaining storage
After the version trim, Sarah turned to the recycling bin. She used Recycle Master to page each site collection's bin down and review it on screen, sorted by deletion date. The grid shows the item name, its original location, its type and size, the author, the deletion date and who deleted it, and it filters on any of those. What it does not do is export: the review happens in the tool, one site collection at a time, so plan on reading rather than forwarding.
A quick scan confirmed what she expected: the bin was almost entirely old draft documents from matters closed between six and fourteen months ago. For the managing partner she attached the tenant recycling bin report instead, which is a CSV of every selected site with its first and second-stage item counts and sizes. It carries no file names, so it answers "how much, and where" rather than "what exactly", which was all the sign-off needed. The response was to clear the lot.
Sarah ran a bin clear across every site collection in one operation. The 38 GB disappeared within a few minutes.
Results
| Metric | Before cleanup | After cleanup |
|---|---|---|
| Total storage used | 450 GB (89% of quota) | ~247 GB (49% of quota) |
| Version history | 243 GB | 42 GB (15-version keep policy) |
| Recycling bin | 38 GB | 0 GB |
| Live content | 172 GB | 172 GB (unchanged) |
| Additional storage purchased | None required | |
| Time to complete | One working day plus an overnight trim run | |
What came next
With the tenant at 49% utilisation instead of 89%, Sarah had breathing room. At the budget review, she presented the cleanup results alongside a recommendation to set a 20-version limit on all document libraries going forward using Explore Master. The version limit was approved and applied across all sites within the same week.
At the current content growth rate, the firm now has an estimated 18 to 24 months before storage becomes a concern again; this time with a version cap in place to prevent the same accumulation from happening.
The key lesson
Sarah's storage problem was not a shortage of quota; it was a visibility problem. The SharePoint admin center showed a total usage number but not where the usage came from. With a proper storage breakdown from Report Master, the solution was obvious: nearly all of the recoverable space was in version history and an untouched recycling bin, not in files that anyone needed.
The same pattern applies to almost any SharePoint environment that has been running for more than two years without active version management.