Brief overview
Microsoft Teams channel files are stored in SharePoint document libraries. Over time, file version history can grow quickly and consume storage.
With Bulk > Delete File Versions, you can select one or multiple teams and delete older versions of files, while keeping the last N most recent versions. The cleanup runs in the background, and you receive an email when it’s done.
How to run a file version cleanup
1) Open the Bulk module
In Microsoft Teams, open the nBold app.
Open the top-right menu and go to Bulk.
2) Select the teams to clean
Use search and filters to find the teams you want to process (template, owners/members, last activity, etc.)
Select one or more teams using the checkboxes.
3) Launch Delete File Versions
Click Actions
Select Delete File Versions (Beta)
4) Choose how many versions to keep
In the Delete File Versions modal:
Keep Keep Recent Versions enabled
Set Keep last versions to the number of most recent versions you want to keep (example:
2)Click Delete
5) Monitor progress and wait for the email notification
The cleanup runs as a background job (it can take a few minutes to a few hours, depending on how many files/versions exist).
After launching any bulk action, you can track it from the History page.
When the job completes, you receive an email notification with the outcome.
6) How to read the results (History + Full Reports)
Each “Bulk Delete File Versions” job shows:
Total files processed
Versions deleted
Total space saved
A Full Reports link for details
Click Full Reports to open the Storage Cleanup Summary, where you can review:
Total saved across all teams
Per-team totals
Per-file breakdown: file name, space saved, and number of deleted versions
Tips & troubleshooting
Recommended best practices
Start with a small set of teams first to validate your “keep last versions” choice.
Keep at least 2–5 versions for important collaboration spaces (project docs, contracts, etc.).
If your organization uses retention / legal hold in Microsoft 365, some versions may not be deleted (or storage savings may be lower than expected).
“0 files processed / 0 versions deleted / 0 bytes saved”
Common reasons:
The selected teams don’t have files with more versions than your “keep last versions” value.
Files exist, but version count is already low (nothing eligible to delete).
The job could not access some content due to permissions (ensure the nBold service account has access to the teams being cleaned).
The job takes a long time
This is usually expected when teams contain many files and/or many versions. Microsoft 365 processing and throttling can impact duration.