
How to use SProbot to free up storage
Now that your SharePoint data has been crawled by SProbot, the fastest way to free up storage is to start with Cleanup recommendations on your dashboard.
Cleanup recommendations show you the sites with the biggest savings to be had from version trimming and archiving, along with the total savings potential for your whole tenant. You can start bulk cleanup jobs for each site with a couple of clicks, and SProbot processes them in the background. For most admins, that means you can spend about 15 minutes reviewing your tenant, start the bulk jobs, and then get on with your day.
SProbot's detailed reviews and cleanup tools are still there when you need more control, such as reviewing sites individually, finding specific problem areas, or choosing exactly which sites and files to clean up. This guide covers both approaches:
- Quick cleanup with Cleanup recommendations: recommended for most people, and the best place to start.
- Granular cleanup: for when you want to drill into individual sites and be selective about what gets cleaned up.
Quick cleanup: Use Cleanup recommendations (start here)
Cleanup Recommendations do most of the analysis for you. During each crawl, SProbot checks every single file in your tenant and flags two groups:
- Active large files: files over 50MB that have been modified in the last 3 years. Their old versions are often the biggest hidden storage consumer.
- Inactive files: SProbot treats files older than 3 years as inactive, whatever their size. These can be archived to cheaper storage.
SProbot then calculates how much each site would save from trimming and archiving, and lists the sites with the most savings at the top.

Before you start: Enable file-level archiving
Version trimming works straight away. To archive inactive files, you first need to enable file-level archiving on your tenant. This only needs to be done once.
Step 1 - Review your savings potential
Open the Cleanup recommendations section on your tenant's dashboard. Start with the total savings potential for your tenant to see what's achievable, then work down the list of sites from the top. The sites with the most savings appear first, so the first few rows usually account for most of the storage you can free up.
For each site, decide whether you're comfortable cleaning it up in bulk. If a site is business-critical, regulated, or you're unsure how its owners use version history, you can skip it for now and review it more closely in the granular cleanup.
Step 2 - Trim versions from active large files
Click Trim in the Active large file versions column to remove old versions from the site's large, active files.

The savings shown assume you keep only the latest version, but you can choose to keep the latest 25, 10, or 5 versions instead. Because these files are still in use, keeping some recent versions is often a sensible compromise (see How many versions should I keep?).

Important: Version trimming is permanent and bypasses the recycle bin. Consider bulk trimming at this scale carefully before you proceed.
Step 3 - Trim and archive inactive files
Click Trim & archive in the Inactive files column to archive all inactive files in the site.

The savings shown assume old versions are trimmed so that only the latest version is archived, but you can choose to keep existing versions. Archived files are moved out of active storage into Microsoft 365 Archive, which costs much less, and they can be reactivated if someone needs them again.

Repeat steps 2 and 3 for each site on the list that you're happy to clean up.
Step 4 - Let SProbot do the rest
That's it. Each job is queued and processed in the background, so you don't need to keep SProbot open. Depending on the size of the job, it can take anywhere from a few hours to a day or two.
While a job is running, the cleanup buttons for that site are disabled. Open the site to see a progress counter.

Storage freed by trimming versions is reclaimed as the job completes, but may take a day or two to reflect in the total consumption figure in the admin center. Archived files usually leave your active storage within a day or two, after which you'll see your available active storage increase.
For more on how recommendations and savings are calculated, see Use Cleanup Recommendations to see and action savings.
Granular cleanup: When you want more control
For many tenants, Cleanup recommendations will deliver most of the available savings. The granular cleanup uses the same two levers (trimming versions and archiving inactive files), but one site at a time, with the full file-level detail in front of you. It's useful when you want to:
- See exactly what will be affected. Review the file report for a site before taking action.
- Involve site owners. Export a site's file report to CSV so owners can review and approve it before anything changes.
- Be selective about version trimming. Choose how many versions to keep for individual files, or leave some files out.
- Find specific problem areas. Investigate why a particular site is growing, or find files that don't belong in SharePoint at all, such as videos, backups or PSTs.
The granular cleanup starts with the two highest-impact actions, then moves on to more gradual, time-intensive steps.
Tip: The Clean up sites with active large files and Clean up sites with inactive files buttons on your dashboard take you straight to the reviews used in the first two steps. You can also find them under Reports > Reviews.
Granular cleanup phase 1 – High-impact actions
Trimming old versions from large, active files and archiving inactive files are the two actions that free up the most storage. In Phase 1, you'll work through them site by site, starting with the sites that have the most to gain.
Cleanup step 1 - Trim versions from active large files
SharePoint's versioning is very useful, but a file's storage footprint can explode when hundreds of versions accumulate, especially for large files that are still being worked on.
SProbot customers have seen seemingly harmless 300MB files sprawl to ~1500 versions with a total size of >600GB. This means older versions are consuming ~99% of the space!
Trimming version history reclaims storage immediately. Unlike deleting files or sites, deleting file versions bypasses the recycle bin, so the space is freed at once without waiting for a retention period.
The Storage section of the Health check shows how much storage your whole tenant uses for latest versions compared to all other versions. This shows how much you could free up by trimming.

How to trim versions in a specific site
1. Open the Sites with active large files review
Click Clean up sites with active large files on your dashboard, or go to Reports > Reviews and select Sites with active large files. Active large files are files over 50MB that have been modified in the last 3 years.
For each site, the review shows its size, the number of files over 50MB, and how much storage is used by the Latest version (GB) compared to All other versions (GB). Sort by All other versions (GB) to see the sites where old versions use the most storage. You can also use Download CSV to export the list of sites.

2. Review the site's active large files report
Click a site name to open its Content tab, which shows the Active large files report. The bar at the top compares the storage used by latest versions with all other versions in the site.
The report lists each file with its location, number of versions, last modified date, and the size of its latest version compared to all its versions. Sort by All versions (MB) to see the files with the heaviest version history. You can use Filters to narrow the list down, for example by file extension.

Before you trim, you can use Download CSV to export the report and share it with the site owner(s) to agree on how many versions to keep.
Tip: Look out for files that don't need to be in SharePoint at all, such as videos, executables, database backups or PST files. Rather than trimming their versions, consider deleting or moving them (see Evaluate very large, unsuitable files).
3. Trim versions
You can trim versions for the whole site or for individual files:
- Whole site: Select Version trim all active large files in this site from the action dropdown and click Start.
- Individual files: Select one or more files, click Cleanup, and choose to keep only the latest 25, 10 or 5 versions, or only the latest version.

Important: Version deletions are immediate and permanent, unlike deleting whole files, which sends them to the recycle bin. You'll be asked to confirm the action whether you're trimming one file or many.
Once you've started a cleanup action, it's added to the queue and processed in the background. You can track it in Activity history.
How many versions should I keep?
The ideal number of versions to retain depends entirely on each specific department or team's requirements. Some teams only ever reference the latest versions of the files they produce, while others actively collaborate, view and restore previous versions as part of their workflow.
We recommend enabling automatic version limits for newly created sites (which is based on the design principle that restore value of a version degrades as the version ages), and to then use the degradation principle when trimming versions on existing sites. This means that it's safer to trim old files to only the latest version, but to keep say 25 versions when trimming newer files. In each instance, you should discuss the trim threshold with the site owner(s) to ensure that trimming isn't too aggressive.
Cleanup step 2 - Archive inactive files
A SharePoint site can be in active use but still contain hundreds or thousands of files that no one has touched in years. Across a tenant, these files add up to a lot of storage, and they also clutter search results and AI answers.
Archiving moves inactive files out of active storage into Microsoft 365 Archive, which costs 75% less. Unlike deleting, it's reversible: archived files can be reactivated if someone needs them again. Archiving also works with retention policies, because archived files stay in retention scope.
To archive inactive files, you first need to enable file-level archiving on your tenant.
How to archive inactive files in a specific site
1. Open the Sites with inactive files review
Click Clean up sites with inactive files on your dashboard, or go to Reports > Reviews and select Sites with inactive files. SProbot treats files older than 3 years as inactive.
For each site, the review shows its size, last activity, total number of files, and the number and size of its inactive files. It's sorted by Inactive GB, so the sites with the most to gain are at the top. Look out for sites where most of the files are inactive, even if the site itself shows recent activity.

Tip: To see the age analysis of files across your entire tenant, go to Reports > Health check.

2. Review the site's inactive files report
Click a site name to open its Content tab, then click View report on the inactive files card (or select Inactive files from the report dropdown).
The bar at the top breaks down the site's storage by how long ago files were last modified: active, more than 3, 5 and 7 years ago. The report lists each inactive file with its location, number of versions, last modified date and size. Files you've already archived with SProbot are hidden by default.

To make it easy for site owners to confirm, use Download CSV to export the report for them to review.
3. Archive the site's inactive files
Select Archive all inactive files in this site from the action dropdown and click Start. You can choose to trim inactive files to their latest version before archiving them, or keep their existing versions.

Archiving applies to all inactive files in the site. If you only need to archive specific files, you can do this in SharePoint itself.
Archived files usually leave your active storage within a day or two, after which you'll see your available active storage increase.
Note: Sites that are no longer used at all are covered by this step too, because all of their files are inactive. Archiving their files gives you the same storage saving as archiving the whole site.
Granular cleanup phase 2 - Medium-impact, gradual actions
Phase 2 involves a bit more analysis and coordination, because you'll be looking at individual files and engaging site owners to decide what can go. The storage is also freed more gradually, because deleted files go to the recycle bin first.
Cleanup step 3 - Evaluate very large, unsuitable files
Some very large files don't belong in SharePoint at all. You'll often find outliers like huge video files, database backups, PST files, installers, or other heavy content that would be better stored elsewhere, or not at all. For example, a single 125 MB file with 350 versions can consume ~44 GB of storage due to version history.
These files don't need to be inactive to be unsuitable, so look for them in the Active large files report rather than the inactive files report. That's where the biggest storage wins are.
How to find and manage unsuitable large files
1. Find sites with large files
Use the Sites with active large files review (see step 1) and open a site's Active large files report. Sort by Latest version (MB) to see the biggest individual files.
2. Look for unsuitable file types
Look at the file names and extensions. Are they videos, zip archives, executables, database files, email PST archives, etc? These types of files might not need to live in SharePoint at all. Use Filters and the Extension field if you're hunting for specific file types.

3. Decide on the action for each file
- If the file is not needed: Select it, click Cleanup and choose Delete entirely to send it to the site's recycle bin.
- If the file is needed but doesn't need to be in SharePoint: If it doesn't benefit from versioning, co-authoring, metadata or other SharePoint functionality, consider moving it to more appropriate, likely cheaper storage. For instance, huge video files could reside in a streaming service or a media container within Azure blob storage; large archives might also belong in blob storage.
- If the file is needed in SharePoint: Keep it, and trim its versions if needed (see step 1).
It's not uncommon to find, for example, an outdated 10 GB database backup or an email PST that someone uploaded to a SharePoint library “just to have a copy”, with no one realising it was chewing up storage. Removing these often has no negative impact on users (sometimes the users themselves forgot the file was even there!).
Deleted files go to the site's recycle bin, where they are retained until they are automatically cleared. If you need to free up the storage immediately, you will need to delete them from the recycle bin as well.
Granular cleanup phase 3 - Remaining nuggets
Once you've dealt with the biggest storage consumers, there are a few governance issues worth chasing down. These won't free up much storage, but they reduce risk and clutter in search results and AI answers.
We recommend addressing these using Cleanup > Tools.
Orphaned sites
Sites can become orphaned in two ways:
- When there is a single group owner (for Microsoft 365 group-connected sites) or one site owner (for communication sites or other non-group-connected sites) and this person's account is deleted, usually when they leave the organisation.
- When a site falls under a retention policy, and the group is deleted but the site remains in place due to the retention hold. The site is then group-orphaned.
You can use Cleanup > Tools > Orphans to identify and take action on orphaned sites.


In the example above:
- Azure Research & Development is a group-connected site (because it's a team) which does not have a group owner.
- Carryx Investments is a group-connected site which doesn't have a group owner, but it does have a site owner (Joanna De Vries). This is risky because when looking at this workspace from the Teams perspective, this owner won't be listed, and she won't have access to the team (because she's only in the site and not the group) so won't be aware of conversations or communication at group level.
- Special Development is a group-connected site which was group-orphaned when its group was deleted but the site remained. Because it does not have any site owners, it is completely unmanaged (with neither group owners nor members).
It's good practice to investigate orphaned sites and either assign an owner, or archive or delete them if they turn out not to be needed anymore.

Duplicate-named teams
It’s surprisingly common to find duplicate SharePoint sites/Teams in most organizations.
Microsoft Teams does not prevent people from using a name that’s already taken – it will just create a site with a numeric suffix in the URL (e.g., Project Alpha and another Project Alpha which ends up as projectalpha2.sharepoint.com).
This can result in:
- User confusion ("which Project Alpha do I use?")
- AI confusion ("which Project Alpha is the authoritative one?")
You can use Cleanup > Tools > Duplicates to view a list of teams with duplicate names.

SProbot does not offer any automated migration/merging functionality, but we recommend you look at the affected sites in more detail to determine possible options and then work with owners to devise a plan.
- Check if one of them is clearly more active or up-to-date. Often one is the “real” one and the other was a false start.
- Look at membership/owners: sometimes the two groups of people overlap heavily (indicating an accidental duplicate by the same team), or they might be different (which could indicate two different things that just coincidentally got the same name).
- Reach out to the owners of the teams/sites and ask if they’re aware of the other instance. Often, they’ll say “Oh, I didn’t realize there was another site named that!” which confirms it’s a duplicate scenario.



