SharePoint version limits target lower storage use

Key insights

• The video says SharePoint AutoSave can create versions as files change and cites a default limit of 500 versions per file.
• The automatic setting is available in SharePoint admin center under Settings and Version history limits.
• The video says the admin center setting covers new sites and new OneDrive accounts.
• For existing SharePoint sites, the video demonstrates enabling automatic trimming with Set-SPOSite.
• Microsoft's documentation describes keeping fewer versions as version history gets older.

Denis Molodtsov [MVP] recently showed how to enable automatic version limits in SharePoint and apply the setting to existing sites with SharePoint Online PowerShell. His short video focuses on a practical distinction: the admin center setting covers new sites, while existing sites need a separate PowerShell step. Microsoft says intelligent versioning can reduce version storage by up to 96%, but that figure is a reported maximum, not a guaranteed result for every environment.

What's new

The video describes SharePoint AutoSave creating a new file version as changes are made and notes a default limit of 500 versions per file. With automatic version limits, SharePoint trims older, lower-value versions rather than retaining an equally dense history indefinitely. The purpose is to save storage while keeping a useful version history.

Administrators can set the automatic option in the SharePoint admin center by going to Settings, then Version history limits, choosing Automatic, and saving. Molodtsov says that setting applies to new sites and new OneDrive accounts. It does not, by itself, configure every existing SharePoint site.

Microsoft's documentation describes the policy as retaining more detail for recent history and progressively fewer versions as versions age. The research notes describe a schedule that retains all versions for the first 30 days, then approximately one per hour between 30 and 60 days, one per day between 60 and 180 days, and one per week after that, subject to applicable limits. This is an age-based approach, rather than a single fixed count for every point in a file's history.

Why it matters

For SharePoint administrators, version history is a storage consideration as well as a recovery tool. Frequently edited files can accumulate many versions, and a fixed maximum may preserve a dense trail of older changes. Automatic limits are intended to reduce that older history without removing version history altogether.

The change may matter to teams that rely on restoring or reviewing recent file edits, since recent versions are retained more densely under the described policy. It may also matter to administrators reviewing storage use across sites. The claimed reduction of up to 96% is a Microsoft figure cited in the video; actual savings can vary, and the video does not provide a calculation for a particular tenant or library.

The distinction between new and existing sites is significant for rollout planning. Setting the admin center default is not the whole migration for an established environment: Molodtsov's example uses PowerShell to enable the setting for an individual existing site or across sites. The clip does not specify a license requirement or a rollout stage, so neither should be assumed from this demonstration.

How it works

For new sites, the video shows the admin center route: open Settings, select Version history limits, choose Automatic, and save. For an existing site, the example connects to the SharePoint admin service and then calls Set-SPOSite with the site's URL and EnableAutoExpirationVersionTrim set to true. The placeholder tenant and site addresses in the example must be replaced with the administrator's own values.

1. Connect to the SharePoint admin endpoint with Connect-SPOService.
2. For one site, run Set-SPOSite with that site's identity and enable automatic expiration trimming.
3. For a bulk update, get all sites with Get-SPOSite -Limit All and pass each URL to Set-SPOSite in a loop.

Molodtsov also says the full video covers checking expiration dates and cleaning up old versions with New-SPOSiteFileVersionBatchDeleteJob. The short description does not provide the complete procedure for those tasks, so administrators should consult Microsoft's documentation before running cleanup operations.

Limitations and open questions

Enabling automatic limits and cleaning up existing version history are separate concerns. The research notes say changing a policy does not necessarily remove versions already stored, so organizations seeking to reclaim space from existing history may need a separate trimming operation. The short video mentions a cleanup job but does not show its full command sequence or explain its effect on every file.

Before deleting historical versions, administrators should consider recovery needs and applicable retention or legal requirements. The research notes caution that versions deleted by trimming may be permanently removed and recommend a What-If analysis before deletion. Those considerations are particularly relevant when applying a bulk command across all sites.

The video does not show measured results from a tenant, explain exceptions, or establish that every file type will produce the same storage savings. Microsoft’s up-to-96% figure should therefore be treated as a potential reduction, not a forecast for a specific organization. Check the documentation and test the planned changes in the relevant environment.

Sources

• Denis Molodtsov's video on SharePoint version storage
• Microsoft documentation on document library version history limits

Frequently asked questions

Does changing the admin center setting update existing sites?

The video says the setting covers new sites and new OneDrive accounts. For existing SharePoint sites, it demonstrates using PowerShell to enable automatic trimming.

How do I enable automatic version limits on one existing site?

Connect to the SharePoint admin service, then run Set-SPOSite for the site with EnableAutoExpirationVersionTrim set to true. Replace the example URLs with your own tenant and site addresses.

Will this immediately remove versions already stored?

The research notes say changing the policy does not necessarily remove existing history. A separate trimming operation may be needed, but the short video does not provide its full procedure.

Is a 96% storage reduction guaranteed?

No. The video cites Microsoft's claim of up to 96% reduction. It does not show results for a specific site or tenant.