Fast retail growth creates a slow Microsoft 365 disaster: site collections multiply, version histories balloon, and empty project folders accumulate across dozens of locations before anyone notices the storage bill.
The Situation
Halcyon Retail is a specialty homewares chain operating 60 franchise locations across Australia and New Zealand. The company migrated from an on-premises file server to Microsoft 365 three years before Tom, the IT Systems Manager, inherited the SharePoint environment. Each franchise operates its own SharePoint team site for store-level operations: rosters, training materials, price lists, compliance checklists, and local marketing assets. A set of central sites handles head office functions: finance, HR, marketing, and supply chain.
Tom received a notification from the Microsoft 365 admin centre in March. The tenant had consumed 87% of its pooled storage allocation. The finance director, on seeing the Microsoft 365 storage add-on pricing, asked whether IT could avoid purchasing more storage before the end of the quarter. Answering that required finding out exactly where the storage had gone.
What the Audit Revealed
Tom ran a storage utilisation export through Report Master, pulling file counts, storage consumed, and version counts across the full tenant. The results arrived in an Excel workbook within a few minutes. Three patterns stood out immediately.
Version history was the dominant factor. SharePoint versioning had been left at its default setting on every library since the migration: unlimited major versions, no minor version limit. Over three years, high-turnover documents had accumulated enormous version tails. The head office price list had 312 saved versions. The national training manual had 287. Store-level rosters, updated weekly, averaged 90 versions each across 60 sites. Version history alone accounted for over 4 TB of the total storage consumption, most of it content that nobody would ever retrieve.
Marketing images were the second issue. The marketing team stored master asset libraries in SharePoint, including full-resolution product photography used for catalogue and online campaigns. Original image files ran between 15 MB and 40 MB each. Because the team also kept versioned copies of images (to preserve previous campaign assets), even the image library had deep version tails. The marketing site libraries consumed 1.4 TB.
Empty folders rounded out the picture. Three years of project activity had left hundreds of abandoned folder structures in both the central and store-level sites: closed campaign folders, completed compliance audit folders, and onboarding folders for staff who had left the company. None contained files, but collectively they added noise and made the site structures harder to navigate.
The Three-Week Cleanup Sprint
Tom ran the cleanup in phases over three weeks, using ShareMaster's Space Master suite for all three operations. No scripts were written. Each tool connected directly to the tenant using Tom's SharePoint administrator account.
The first phase used the Version Trimmer. Tom set a policy of keeping the 10 most recent major versions for all document libraries across the tenant, which matched what the legal and compliance team said was sufficient for their record-keeping requirements. The Version Trimmer previewed the projected storage saving before committing: 3.8 TB across all sites, removing over 2 million redundant version records. Tom approved the operation. It ran overnight and completed without incident.
The second phase targeted the marketing image libraries with the Image Reducer. It processed the high-resolution JPEG and PNG files stored in the central marketing sites, compressing them to a size appropriate for SharePoint document storage without discarding the originals (Tom retained the originals on an external DAM system the marketing team already used). The Image Reducer reduced the marketing library footprint from 1.4 TB to under 400 GB, freeing roughly 1 TB of quota.
The third phase used the Empty Folder Remover, which scanned all sites and surfaced every empty folder for review. Tom exported the list to Excel, filtered out a small number of intentionally-empty template folders that the compliance team used as structural placeholders, and ran the removal on the remainder. Tom removed approximately 1,400 empty folders across the tenant.
Explore what Space Master's Version Trimmer, Image Reducer, and Empty Folder Remover can do
Results
After the three-week cleanup, the tenant's storage consumption had dropped from 87% to 38% of the allocated pool. The total reclaimed was just over 6 TB. The storage add-on purchase was deferred indefinitely. Finance closed the quarter without an additional Microsoft 365 line item.
The version trimming alone would have been sufficient to avoid the immediate cost pressure, but the combined cleanup gave Tom a much healthier baseline to work from. At the tenant's current growth rate, the IT team now has an estimated 18 months before storage becomes a concern again, compared to the 6-8 weeks of headroom that existed before the sprint.
What Changed in the Governance Process
Tom made two structural changes after the cleanup to prevent the same accumulation from recurring.
First, he set versioning limits on all existing and newly created document libraries using the Version Trimmer's policy application feature: a maximum of 20 major versions on standard libraries and 50 on compliance-critical libraries. He removed the unlimited versioning default that had been in place since the original migration.
Second, he scheduled a quarterly storage review using Report Master. Each quarter, a fresh storage export identifies the top 20 sites by consumption and flags any library where version counts have grown beyond the configured limit. The review takes about 30 minutes and catches creep before it becomes a crisis.
The experience also surfaced a communication gap. The franchise operators had no idea that every edit to a roster or price list was generating a new stored version. A short note in the monthly IT newsletter explaining how SharePoint versioning works, and asking store teams to delete working drafts before saving final versions, reduced the monthly version creation rate visibly within two months.
For a step-by-step guide to reducing SharePoint storage using versioning policies, see how to reduce SharePoint storage fast.