Free, read-only early access CloudSniff connects via Microsoft's standard OAuth — the same sign-in flow every Microsoft 365 app uses. The consent screen shows "unverified publisher" because I haven't filed business-entity paperwork yet. Your files are not touched. Read-only.
CloudSniff · Early access · read-only diagnostic
The job: figure out what's actually eating your storage. I scan your OneDrive and SharePoint metadata — about a minute for typical accounts, longer for very large tenants due to Microsoft Graph rate limits — and show you version history, abandoned files, the worst offenders, and the monthly dollar number you didn't know about. Read-only. No file contents. No changes written.
Microsoft's built-in storage view shows total usage by folder — not which specific versions are the problem. CloudSniff shows you that breakdown.
No credit card. Read-only access. Revocable anytime.
Show me the view for…
SharePoint Extra File Storage costs $0.20 per GB per month — about $2.40 per GB per year (per Microsoft's published pricing). A tenant with 500 GB of accumulated version history nobody knows about pays $1,200 a year for storage that could likely be cleaned up.
Sample annual exposure for the Acme Demo Tenant shown above. The storage bloat is the real problem — but a dollar number is usually the cheapest way to explain it to the person paying the bill.
$7/mo Microsoft 365 Personal — avoid one year of upgrades.Illustrative only; your real scan will recompute against your tenant's actual version inventory.
Today CloudSniff is a deliberately small read-only product. The destructive cleanup path is gated behind entity formation, insurance, and a lawyer-reviewed TOS — none of which exist yet.
I'm Andrei Antipenko — years of IT support work, first inside the company I work at, then watching the same pattern repeat with their partners, then realizing every IT forum had the same posts every week. People paying for storage they couldn't account for. Old versions piling up silently. Microsoft's tools assuming you could write PowerShell. Most people gave up trying to clean up and just paid the upgrade. If the platform vendors had shipped effective version-cleanup and file-archival tools, CloudSniff wouldn't need to exist.
In my own work, with clients and partners I've supported, across the forums I follow. These are the patterns I keep running into — paraphrased from public discussions, names removed.
Showing 12 of 12 quotes.
All quotes are paraphrased from public discussions across Reddit, Microsoft Tech Community, and Microsoft Q&A. No real names, no specific posts, no direct copies.
Confusion“A document-heavy student described discovering only by accident that a single frequently-edited PDF in their OneDrive had accumulated over two hundred saved versions, and that this one file alone explained most of their storage problem.”
— Personal M365 user, /r/Office365 thread
Confusion“A solo accountant running a small practice said their OneDrive had become so cluttered with old versions of client tax workpapers that just locating the current copy of a return had started to cost them measurable time during busy season.”
— Solo accountant, /r/Accounting thread
Confusion“The office manager at a small construction firm said they had been quietly designated 'the Microsoft 365 person' despite no IT background, and the storage-usage reports in the admin center made them feel less informed about what was wrong, not more.”
— Small-biz accidental admin, /r/smallbusiness thread
Accumulation“A home user with a large personal music library said their roughly 80 GB of actual music had somehow ballooned into more than a terabyte of OneDrive usage, and they only learned later that metadata changes had silently spawned more than fourteen retained versions of every single track.”
— Personal M365 user, /r/onedrive-adjacent thread
Accumulation“A bookkeeper supporting a handful of small-business clients said that one frequently-edited reconciliation spreadsheet had silently produced more than 3,500 retained versions, and that this single file accounted for hundreds of megabytes of their plan's quota.”
— Bookkeeper, /r/Accounting thread
Accumulation“A sysadmin at a mid-size organization described being shocked to find that PowerPoint files in their tenant were collectively consuming close to 900 GB — driven almost entirely by the default 500-version retention setting that nobody had ever changed.”
— Sysadmin, Microsoft Tech Community thread
Lockout“A newly-appointed admin at a small services firm shared that they had inherited a SharePoint environment sitting at 2.76 TB of 2.89 TB used, with years of accumulated old folders, and had no idea where to even begin cleaning it up without risking accidentally deleting something important.”
— Small-biz accidental admin, Microsoft Q&A thread
Lockout“An IT lead at a small regional firm shared that when a long-tenured employee left and their OneDrive was migrated into a SharePoint site, the organization went from 'plenty of storage' to 'overage charges' overnight — and the surprise of that conversion was the moment they realized how opaque the entire storage model is.”
— Sysadmin, /r/sysadmin thread
Gave up“A consultant running a one-person shop said they stopped trying to manually clean their OneDrive after realizing it would take them an entire weekend, and they would rather just upgrade the plan than spend Saturday clicking through version-history menus.”
— Solopreneur consultant, /r/sideproject thread
Gave up“A sysadmin running a multi-tenant managed-services practice said they had eventually given up on Microsoft's native tooling for version cleanup and had written their own PowerShell scripts because nothing in the admin console actually let them see or act on the bloat at scale.”
— Sysadmin, /r/sysadmin thread
Cost shock“A parent on a Microsoft 365 Family plan said their OneDrive kept reporting 'storage full' even though the family pool clearly had room, and they were tempted to just pay for the next tier up rather than spend another evening trying to figure out what was wrong.”
— Personal M365 parent, /r/microsoft365 thread
Cost shock“A boutique-law-firm associate shared that their firm kept paying for additional Microsoft 365 storage every renewal cycle because nobody on staff had the time or expertise to figure out whether the underlying problem was really 'too many files' or just 'too many versions of the same files.'”
— Law firm associate, /r/lawpracticemanagement thread
Illustrative numbers only — your real scan recomputes against your tenant's actual version inventory.
Free, no credit card. Donations are optional.
Read-only access. CloudSniff never asks for write, delete, or file contents. Microsoft's consent screen shows the exact scope.
Revocable anytime. Disconnect at your Microsoft account permissions page. CloudSniff can't re-access without you re-approving.
Auto-deletes after 90 days. Your scan data clears itself, even if you forget about CloudSniff.
Tokens live ≤15 minutes. CloudSniff mints a fresh access token from Microsoft for each scan, uses it for at most 15 minutes, then discards it. The access token never sits in the database.
Honest note on Microsoft's own version-cleanup tooling. Microsoft is shipping Intelligent Versioning and PST-specific version controls, and admin-center defaults let you cap new-library version counts. If you can drive PowerShell — New-SPOSiteFileVersionBatchDeleteJob, New-SPOSiteManageVersionPolicyJob and friends — you can trim a SharePoint tenant for free today. I'm not pretending otherwise.
Where the native tooling has documented carve-outs: Intelligent Versioning is disabled when retention policies are applied (per Microsoft's own announcement on Tech Community); admin-center defaults are not retroactive — they only apply to new libraries; file-type-specific controls cover only audio, video, and Outlook PSTs (no PDFs, CAD, design assets, ZIP archives, source code); and policy authoring below the tenant level is PowerShell-only, with no admin-center UI for site or library policy composition. Trim jobs bypass the recycle bin, so the friction for non-PowerShell admins is real.
Today, this tool is just visibility — see your version inventory, see what your retention policies are doing to it, see the dollar number. If I add paid cleanup later, the wedge is in the gaps Microsoft hasn't closed: arbitrary file-type policy, folder/path exceptions, retention-policy-aware exclusions, and a durable audit trail outside the M365 boundary. Not a fictional restore promise — Graph offers no undelete primitive for trimmed versions, and I won't pretend it does.
About a minute, free, read-only.
Want cleanup? Join the waitlist below.
I'll turn on one-click cleanup once I have the company, insurance, and lawyer-reviewed TOS to do it responsibly. Until then I'm collecting interest. Drop your email via the "I'd pay if cleanup comes back" button in the footer and I'll ping you when it's ready.