Version History Issues

How to Configure SharePoint Online Version Limits and Delete Old Versions

Maira Mehtab Sep 24, 2026 869 views

Question details

Users need to know how to configure document version limits in SharePoint Online, enforce the deletion of older file versions, and understand the expected timeframe for these background deletion processes to complete.

Product: SharePoint Online
Device & OS: not provided
Scenario: A user has set a version limit to 100 in SharePoint Online but notices that older versions are not removed immediately after 24 hours.
Observed behavior: SharePoint version trimming is a background process taking up to 48 hours. Old versions are not deleted instantly and may be retained longer due to legal holds, retention policies, or requiring the file to be updated first.

Before you start

Ensure you have SharePoint Administrator privileges to run management PowerShell commands, and verify that there are no active retention policies or legal holds that would prevent file deletion.

Solution 1Recommended

Check the Status of the Version Policy Job

Use this solution to verify if the automated background version trimming process is still running or stuck.

SharePoint Online processes version trimming in the background. It is entirely normal for this process to take up to 48 hours after you configure your version limits. Furthermore, versions exceeding count limits are often removed gradually as files are actively updated by users.

Open SharePoint Online Management Shell

Launch the SharePoint Online Management Shell as an administrator on your computer.

Run the Progress Check Command

Execute the command: Get-SPOSiteVersionPolicyJobProgress -Identity $siteUrl (replacing $siteUrl with your actual site URL).

Wait for Processing

If older versions are still present after 24 hours, allow additional processing time (up to 48 hours) for the background job to finish.

Policy Precedence: Retention policies and legal holds take absolute precedence. If these are active on your library, SharePoint will not delete the older versions, regardless of the limit you configured.

Solution 2

Manually Trigger Batch Deletion for Older Versions

Use specific PowerShell commands to manually force the deletion of older versions if appropriate for your administrative scenario.

Free Microsoft Office alternative

Looking for a Simpler Way to Manage Documents? Try WPS Office

If managing complex SharePoint version histories and PowerShell scripts is slowing down your workflow, consider WPS Office. It provides a lightweight, highly compatible alternative to Microsoft Office, featuring intuitive version history management and seamless cloud storage out of the box.

1. Download the Installer: Visit the official WPS Office website and download the free installation package.
2. Install the Software: Run the installer and follow the on-screen instructions to complete the setup.
3. Manage Files and Versions: Open your documents and easily track or restore previous file versions via the built-in backup and cloud features.

Fully compatible with Microsoft Office formats (DOCX, XLSX, PPTX).Built-in, easy-to-use version history tracking without complex scripts.Free and lightweight, ensuring smooth performance on any device.Integrated WPS Cloud for seamless team collaboration and file recovery.

microsoft office alternative - wps office

Frequently Asked Questions

Why aren't older SharePoint versions deleted immediately after changing the version limit?

SharePoint version trimming is a background operation that can take up to 48 hours to complete. In many cases, versions exceeding the limit are only gradually removed as the respective files are opened and updated.

Do retention policies override version limits in SharePoint?

Yes. Microsoft 365 retention policies and legal holds always take precedence over standard version limits. If a file is subject to a hold or retention rule, its older versions will not be deleted.

What should I do if the version deletion job is stuck for days?

First, check the job status using the Get-SPOSiteVersionPolicyJobProgress command. If there is no progress after 48 hours and manual commands like New-SPOSiteFileVersionBatchDeleteJob do not resolve the issue, you should contact Microsoft Support.

Document & File Issues