When SharePoint and OneDrive storage runs short, it is often down to content that nobody actively uses any more: version histories, duplicates, recycle bins, files in Teams channels and migrated legacy data. With SharePoint Storage Monster we have built our own tool that makes these causes visible in a Microsoft 365 tenant and shows the potential savings in Swiss francs. Even so, you should only delete after an approval that takes retention, legal holds and recovery into account.
What fills the storage
In our work as a Microsoft partner, we see the same causes again and again:
- Version history: by simple arithmetic, a single 50 MB file with 200 versions can take up to 10 GB.
- Duplicates: the same presentation on five SharePoint sites, the same document in three Teams channels.
- Migrated legacy data: data from on-premises systems that nobody has opened for years.
- Recycle bins and hidden storage: deleted files still take up storage for up to 93 days; on top of that come files in Teams channels and hidden libraries.
What Storage Monster shows
SharePoint Storage Monster is our own SaaS product. We built it with Replit as part of the Replit Agent 4 Buildathon. It connects to your Microsoft 365 tenant, analyses storage use and presents the results in a dashboard.
The scan
The scanner covers:
- Stale files: documents that have not been opened for months or years
- Duplicates: identical or near-identical files across sites and libraries
- Versions: files whose version history takes up many times the original size
- Recycle bins: deleted files that still take up storage
- Teams storage: files in Teams channels and chat attachments
The savings dashboard
- Potential savings in Swiss francs: calculated on current Microsoft prices
- Priorities: the biggest storage consumers first, ranked by potential savings
- Clean-up from the dashboard: direct actions, without searching manually
- History: track the savings over time
An interface for other agents
Other AI agents can control Storage Monster directly. A Copilot Studio agent or a Power Automate flow can trigger a scan, evaluate the results and initiate measures. That turns storage housekeeping into an ongoing process. You decide which measures may run without human approval; in our view, deletions should always go through an approval step.
What to clarify before cleaning up
A scan shows where storage is used. Whether something can go is for your organisation to decide.
- 1Business need: who still needs the content, and who decides?
- 2Retention and legal holds: automated deletion should only happen after retention requirements and legal holds have been checked.
- 3Recovery: establish how deleted content can be restored if needed.
- 4Approval and audit trail: administrators should be able to review each recommendation before a change; audit logs, rollback and role-based approvals are part of this.
- 5Permissions and data flow: for every tool, ours included, clarify which Microsoft Graph permissions it needs, whether it only reads or can also change and delete, and where tenant data and logs are processed.
- 6Measure the effect: a displayed savings potential is not a guaranteed cost reduction. Measure the actual change on your Microsoft invoice over a defined period.

