We put your Microsoft 365 and cloud data in order.
We measure what is in your Microsoft 365 and cloud storage and give every file one outcome. Nothing deleted without your approval.
Your storage today
Assessment
Every file gets one outcome
- Delete
- Move
- Archive
- Keep
What can be cleared
In use 38% · 62%
- ActiveOpened, used or required.
- 38%
- Inactive filesUntouched for years, no retention hold. Almost always the largest line item.
- 20%
- DuplicatesIdentical copies, matched on hash rather than filename.
- 14%
- Version buildupStorage that is mostly old versions.
- 12%
- Orphaned dataSites, OneDrives and volumes with no active owner.
- 9%
- Wrong storage tierCold data on expensive storage. Nothing to delete.
- 7%
Proportions illustrative. Yours are whatever the assessment finds.
- 52%
- is dark data: stored, but of unknown value.
- 33%
- is ROT: redundant, obsolete or trivial — and therefore known to be useless.
- 15%
- was identified by IT decision makers as business-critical.
If your tenant continues to operate above your storage limits, you risk the environment being put into read-only mode. Users may then be unable to add or modify content until storage usage is reduced or additional capacity is purchased.
Microsoft Learn — SharePoint limits, footnote 8 (paraphrased)
Every file ends up with one of four outcomes
You get a complete recap of your data: every object with an outcome and the reasoning behind it.
- Delete
- Duplicates, old versions and orphaned files under no retention hold — with the evidence attached.
- Move
- Data that belongs somewhere else: into a team site with an owner, or onto a storage tier that matches how it is used.
- Archive
- Keep it, just not on your most expensive storage. Compressed, findable and retrievable.
- Keep
- Active data. You also see why the rest stays.
Our speciality is that first audit. Carrying it out afterwards — deleting, moving, archiving, compressing and setting the storage tiers right — we are glad to do as a separate engagement, or your own administrators do it from our plan. In neither case do we skip your approval.
What lands on the last day
A findings register: what is there, why it can go, and how much space clearing it frees.
Findings register
Example
| Finding | Location | Volume | Evidence |
|---|---|---|---|
| Inactive files | Microsoft 365 — SharePoint and OneDrive | 0.9 TB | Not opened since 2022 |
| Old versions | Microsoft 365 — SharePoint, 14 sites | 0.5 TB | 84% of storage sits in old versions |
| Duplicates | Microsoft 365 — 14 sites, 52 OneDrives | 0.4 TB | Identical hash, 3 to 7 copies |
| Wrong storage tier | Azure — Blob Storage, 2 containers | 0.8 TB | Read under once a year |
Reclaimable in this example
2.6 TB
Illustrative example for an organisation of roughly 60 users, with 1.6 TB of included SharePoint storage. The locations and figures above are not from a real engagement and are shown to explain the format of the deliverable.
- Stored today
- 4.2 TB
- After cleanup
- 1.6 TB
If you stayed inside your storage quota, the cash saving is zero. We measure that before the engagement; if you are not over, the conversation is about risk and the quality of your Copilot answers instead. We will not put a saving in a proposal that you never see materialise.
Measure first, then monitor
One measurement, and after that only what you want.
Our speciality
Assessment
One measurement across all your platforms, every object with an outcome and its reasoning. Two to four weeks from access.
Optional, second step
Execution
We clean up what you approved, in batches and with a restore window.
Optional, ongoing
Monthly monitoring
A short monthly report, so it does not build back up.
A fixed price before we start. No price list, and no percentage of the saving — that would reward us for recommending deletion.
What we handle
Microsoft first, because that is where most of the pollution sits. The rest comes along in the same engagement.
Microsoft 365
The metadata comes straight out of Microsoft Graph: provable, not estimated.
- SharePoint Online
- OneDrive
- Microsoft Teams
- Exchange Online
- Version history
- Microsoft Graph
Microsoft Azure
Unattached disks and snapshots of machines long since gone.
- Blob Storage
- Azure Files
- Managed Disks
- Snapshots
Amazon Web Services
Version buildup and lifecycle rules that were never written.
- S3
- EBS volumes
- Snapshots
- Lifecycle rules
Google Cloud and Workspace
Buckets and Shared Drives with no owner.
- Cloud Storage
- Persistent Disks
- Google Drive
- Shared Drives
Send a message
