Microsoft's Mission Critical engineering blog has published detailed guidance on SharePoint Online's Automatic version history cleanup feature, also referred to as intelligent versioning. The post explains how Automatic mode works, how administrators can enable it org-wide, and what it means for storage consumption in SharePoint Online and OneDrive for Business.
Read on Microsoft Community Hub
What is Automatic versioning?
SharePoint Online has always allowed admins to set a maximum version count per library, with the default standing at 500 major versions per file. Under that fixed-count model, SharePoint keeps every version until the ceiling is reached; then the oldest version is dropped each time a new one is created. There is no distinction between a three-year-old version that nobody will ever need and one saved last Tuesday that is genuinely useful for recovery.
Automatic mode changes this by applying a time-decay policy. Instead of treating all versions equally until the count cap is hit, Automatic mode retains a high density of recent versions and prunes older versions progressively as they age. A file actively edited today has plentiful recovery points from the past few days, a reasonable number from the past month, and only sparse checkpoints further back in history. Versions that are statistically unlikely to ever be needed for recovery are removed, while recent saves remain fully accessible.
How Automatic mode compares to Manual mode
| Behaviour | Manual (fixed count) | Automatic (intelligent) |
|---|---|---|
| Version retention basis | Count only (e.g. keep last 500) | Time-decay: more recent versions kept at higher density |
| Treatment of old versions | Kept until count cap is reached | Progressively pruned as they age beyond useful recovery windows |
| Storage impact over time | Grows linearly with edits until cap | Stabilises over time as background cleanup removes aged versions |
| Short-term recovery access | All saves retained up to cap | All recent saves retained; no practical difference for short-term recovery |
| Long-term version history | Full history up to cap, then rolling drop | Sparse checkpoints; older history is thinned by background jobs |
| Hard cap | Admin-defined (max 50,000; default 500) | 500 versions per file (hard cap remains in place) |
How to enable Automatic versioning org-wide
- Sign in to the SharePoint admin center (
https://<your-tenant>-admin.sharepoint.com). - Select Settings in the left navigation.
- Choose Version history limits.
- Under the organisation-wide default, select Automatic.
- Save the setting.
The change applies to new document libraries created after the setting is saved. Existing libraries are not immediately updated. To apply Automatic mode to libraries already in use, update the version settings on each library individually or use the SharePoint PowerShell module to update limits across libraries in bulk. Background jobs process these updates asynchronously; Microsoft's documentation notes that processing can take up to 24 hours depending on library size and tenant activity.
What this means for SharePoint storage
For organisations running on the default 500-version limit for years without a deliberate version policy, switching to Automatic mode can meaningfully reduce version history storage over the months that follow. Files with old, low-recovery-value versions will shed storage gradually as background cleanup jobs run. New files created after the setting change will accumulate less version storage from the outset.
Automatic mode is not a substitute for a one-time bulk trim of historical version storage already accumulated. If your tenant carries significant version bloat from years of unmanaged versioning, a targeted bulk trim is still the most efficient way to reclaim that storage quickly. See the SharePoint Version History Storage Cost analysis for context on how version accumulation works, and the SharePoint Versioning Defaults Reference for a full breakdown of per-library and per-tenant default settings.
Impact on ShareMaster users
Enabling Automatic versioning at the tenant level does not change how ShareMaster's Space Master Version Trimmer works. The Version Trimmer operates on version history that currently exists and applies the retention policy you configure, such as keeping the last 20 versions per file or removing versions older than 90 days. It is compatible with libraries under either Manual or Automatic mode.
The practical combination for most tenants is: run a one-time Space Master trim to clear historical bloat, then switch the org-wide default to Automatic so that future version accumulation manages itself. That pairing gives you immediate storage reclamation plus a self-regulating policy going forward, without ongoing PowerShell scripting.
Summary
Automatic versioning is available now as an org-wide default in the SharePoint admin center. For most standard document libraries, it represents a meaningful improvement over the fixed-count model: storage stabilises over time, recent recovery access is preserved, and the administrative burden of version governance is reduced. Admins managing tenants with growing storage costs should consider enabling Automatic mode as part of a broader version governance plan, paired with a one-time historical trim on existing libraries that have already accumulated significant bloat.