Daniel is the SharePoint admin at a 900-user professional services firm. Every December he books two weeks in his calendar and calls it "SharePoint cleanup." He audits permissions, reviews external sharing links, trims version history, clears the tenant recycle bin, and chases down stale sites that nobody has touched since the previous year. The problem is not that the work is difficult. The problem is that two weeks is not long enough to undo eleven months of accumulation - and by the time December arrives, the worst of the damage has already sat unaddressed for nearly a year.
The annual SharePoint cleanup is one of the most common governance patterns in Microsoft 365, and one of the most counterproductive. This post makes the case for moving to a quarterly cadence instead. Not because you need to do more work, but because spreading the same work across four shorter sessions is structurally better than compressing it into one painful project.
1. Storage Usage Grows Continuously, Not in Spikes
Version history, meeting recordings synced from Microsoft Teams, image assets uploaded for intranets, and files left behind after a migration: storage usage in SharePoint Online accumulates every single day. It does not pause between cleanups and politely wait for your annual review window.
The practical consequence is that by the time an annual cleanup starts, it has become a large project. You are trimming hundreds of gigabytes rather than tens, and deleting thousands of old versions rather than hundreds. That scale compounds with every month that passes between cleanups.
Quarterly storage reviews keep each session manageable. A version trim run every ninety days removes the most recent accumulation before it layers on top of last quarter's growth. Organisations that run quarterly version trims and quarterly recycle bin reviews rarely face the emergency storage conversation that organisations on annual cycles know well. For the mechanics of trimming version history across a tenant, see the guide on trimming SharePoint version history.
2. Permission Drift Follows Project Timelines, Not Calendar Years
A contractor joins a project in February. They are granted unique permissions on a client library: site member on the project site, contribute access on two specific document folders. The project wraps up in May. Nobody removes the permissions.
Under an annual cycle, those permissions sit until December. Under a quarterly cycle, they are caught in July at the latest. Seven months of lingering access versus two. The difference matters because the contractor may have moved to another client's organisation, taken a competitor role, or simply no longer has any legitimate reason to access the data. The permission is not necessarily being abused. But it represents an unresolved risk that gets resolved far faster with quarterly reviews.
Project-based access is the most common source of permission drift in SharePoint Online. Projects do not align to calendar years. They complete in March, June, September, and October. An annual audit aligned to December will always have between seven and twelve months of drift baked in before it even starts. Quarterly reviews align better with the rhythm of actual work.
3. External Sharing Links Have No Memory
A sharing link granted in January has nine months to be forwarded, saved to a personal device, or used by someone outside the original scope before a December audit catches it.
External sharing links in SharePoint Online, particularly "Anyone" links that require no sign-in, do not expire by default unless your tenant policy enforces an expiry. A link created for a one-time vendor review in Q1 remains functional and shareable through Q2, Q3, and Q4 unless someone actively revokes it.
The risk is not just the original share. Links get forwarded in emails and pasted into chat messages. The person who received the link may share it with a colleague who shares it with a client who stores it in their own systems. The longer a link exists without review, the further it has travelled from its original context.
Quarterly external sharing reviews reduce the worst-case exposure window from twelve months to three. You are limiting how long a link that should have been revoked can continue to circulate. A shared links audit that would take hours to untangle annually becomes a routine 30-minute review quarterly.
See how ShareMaster's Shared Links and Permissions tool handles bulk link revocation
4. Quarterly Cleanup Fits in a Single Session; Annual Cleanup Requires a Project
There is a meaningful psychological and logistical difference between a task and a project. A project requires planning, stakeholder sign-off, a maintenance window, communication to users, and probably several days of focused work. A task is something you open a tool, run a report, act on the results, and close.
Annual SharePoint cleanups are almost always projects. They are large enough that they need to be scheduled, resourced, and managed. That means they also get deferred. The December cleanup slips to January. The January cleanup gets squeezed by other priorities. It ends up being March before anything meaningful happens, which means the cycle was really fourteen months rather than twelve.
A quarterly cleanup, done with tooling that surfaces the data quickly, stays a task. A version trim run with Space Master takes minutes to configure and run. Generating a shared links report takes seconds. An external sharing review takes twenty minutes to work through and act on. Four short sessions per year total less calendar stress and less context-switching than one long project that expands to fill the time available.
5. Microsoft Changes the Rules More Than Once a Year
In the past twelve months alone, Microsoft has shipped automatic versioning mode for SharePoint Online document libraries, changed how storage quota is enforced for tenants on specific licence plans, updated the default expiry settings for external sharing links in new tenants, and retired several legacy authentication mechanisms that affected third-party integrations. The platform is not stable between your annual reviews.
This matters because your cleanup strategy depends on how the platform works. Automatic versioning mode, for example, changes how version storage accrues: libraries that opt in to automatic expiration behave differently from those on manual limits. A governance policy written before that feature existed may be actively wrong now. An annual reviewer discovers this discrepancy eleven months too late.
Quarterly reviews create a natural forcing function for keeping your governance approach current. Each session includes a brief check on whether any Microsoft 365 changes since the last review affect what you are about to do. Over four reviews per year, that is four opportunities to catch a platform change before it causes a problem, compared to one opportunity per year on the annual model. The ShareMaster Alerts feed tracks relevant Microsoft 365 changes to make this check fast.
Building the Quarterly Habit
Switching from annual to quarterly does not mean quadrupling the work. It means distributing the same work more evenly. One practical approach: anchor each quarter to a single focus area, with a light pass over the others.
- Q1 (January): Storage and version history. Trim old versions, clear the recycle bin, identify large files.
- Q2 (April): External sharing links. Revoke links from completed projects, check for "Anyone" links on sensitive libraries.
- Q3 (July): Permissions. Review unique permissions on project sites, remove stale contractor and guest access.
- Q4 (October): Full sweep. A lighter version of the annual cleanup, but done in October rather than December to avoid year-end pressure.
The key is to schedule each session as a fixed calendar block rather than a project to be planned. Ninety minutes, four times a year, with the right tooling available before you start. That is a sustainable cadence for a single SharePoint admin at organisations up to several thousand users.
Daniel, from the opening scenario, switched to a quarterly model. His December session is now shorter than it used to be by several days. Not because SharePoint is cleaner by magic, but because the accumulation never builds to the same scale when you chip away at it every three months.