M365 Playbooks

SharePoint · OneDrive· Deploy

Deploy intelligent versioning in SharePoint

Written by

Last reviewed · Version 1 · 5 min read

Purpose

Reduce the storage that old file versions consume in SharePoint and OneDrive, so the organization stops buying storage it does not need, while people keep the versions they actually restore. Done well, it also removes stale versions that add risk without adding value.

Overview

Automatic version history limits set as the organization default, piloted on representative sites and extended to existing libraries in waves.

Effort
About 8 to 12 person-days
Duration
4 to 8 weeks
Complexity
Low
Who's in the room
SharePoint admin, records or compliance lead, storage or finance owner, a few site owners
Licensing
Version history limits are part of SharePoint in Microsoft 365. Tenant-wide trimming of existing versions needs SharePoint Advanced Management or a Microsoft 365 Copilot licence.

Risk of not doing it

Storage keeps growing with versions nobody restores, and the organization pays for extra storage or hits quota limits that block people from saving work.

Key activities

The plan in order: what must be true first, what to decide, then how to configure the pilot and production.

Prerequisites

  1. Measure where storage goes today

    Pull current storage use for the largest sites and libraries, and run a version storage report on a handful of heavily edited sites to see how much of their storage is versions.

    Who
    SharePoint admin
    Produces
    A baseline of total storage and version storage on sample sites

  2. Confirm retention and hold requirements

    List the retention policies and eDiscovery holds that cover SharePoint and OneDrive. Items under retention or hold ignore library version limits until their retention ends, so limits will not shrink that content.

    Who
    Records or compliance lead
    Produces
    A list of covered sites and what the limits will not change

  3. Check backup and recovery expectations

    Confirm how people recover earlier work today. Versions deleted by limits or trim jobs bypass the recycle bin and cannot be restored from it, so agree what recovery the organization still needs.

    Who
    SharePoint admin with the service owner
    Produces
    Agreed recovery expectations, and whether a backup solution is in scope

Decisions

  1. Decision: Which default limit should new libraries use?

    The organization default applies to new libraries on sites without their own setting. Microsoft recommends the automatic setting, which keeps more recent versions and thins older ones as they age.

    Options

    • Automatic (recommended by Microsoft)
    • Manual count limit, e.g. 500 major versions
    • Manual count and expiration, e.g. 500 versions or 365 days

    Recommended default: Automatic (recommended by Microsoft)

    Who
    Service owner, with the records lead
    Produces
    The organization default limit

  2. Decision: Which sites need an exception?

    Some sites may need a different limit, such as regulated content or long drafting cycles. Site and library settings can break inheritance from the organization default.

    Options

    • No exceptions; retention policies cover regulated content
    • A small, documented exception list
    • Let site owners set their own limits

    Recommended default: No exceptions; retention policies cover regulated content

    Who
    Records lead, with site owners
    Produces
    A short exception list with a reason for each

  3. Decision: What happens to existing libraries and versions?

    Changing the default does not touch existing libraries. Decide whether to leave them, update their limits going forward, or also trim versions that already exceed the new limits.

    Options

    • New libraries only
    • Update existing library limits, keep existing versions
    • Update limits and trim existing versions

    Recommended default: Update existing library limits, keep existing versions

    Who
    Service owner
    Produces
    A decision for existing content and the order sites will follow

Pilot configuration

  1. Run what-if analysis on the pilot sites

    Run the version storage what-if report on each pilot site to see the effect of automatic limits, and of trimming, before changing anything.

    Who
    SharePoint admin
    Produces
    Expected storage savings per pilot site

  2. Apply automatic limits to the pilot sites

    Set the pilot sites' version history limits to automatic and update existing libraries on those sites. Hold any trimming of existing versions until the pilot review.

    Who
    SharePoint admin
    Produces
    Pilot sites running on automatic limits

Production configuration

  1. Set the organization default

    Set the organization default version history limit to automatic, so every new library starts with it.

    Who
    SharePoint admin
    Produces
    Organization default set

  2. Extend to existing sites in waves

    Update existing libraries site by site, largest storage consumers first. If you trim existing versions, queue trim jobs in waves and only after each site's what-if review.

    Who
    SharePoint admin
    Produces
    Existing libraries aligned to the default, wave by wave

  3. Make it enforceable

    The organization default applies to every new library automatically, so new sites follow the standard without anyone remembering it. Review site and library exceptions in the version settings changes recorded in the audit log.

    Enforced by a mechanism.

Pilot to production

Rollout approachRepresentative cross-section · Pilot size: 5 to 10 sites

Version use differs by kind of site. A sample that includes heavily edited project sites, regulated content and ordinary team sites shows the real effect before you change everything.

Make your pilot representative
  • Every major role, not only IT and enthusiasts
  • More than one location or time zone
  • Heavy users of the workload you are changing
  • People who handle sensitive information
  • At least one team you expect to be sceptical

  1. Choose and brief the pilot sitesChange: Inform

    Pick sites with heavy editing, long drafting cycles and ordinary use. Tell their owners what changes and how to ask for help.

    Move on when: Every pilot site owner has acknowledged the change

  2. Apply and observe for two to four weeksChange: Explain

    Apply automatic limits and watch restore requests and support tickets about missing versions.

    Move on when: No unresolved restore requests caused by the new limits

  3. Review the numbers

    Compare version storage on the pilot sites with the baseline and with the what-if estimate.

    Move on when: Savings are in line with the estimate and owners report no lost work

  4. Set the default and roll out in wavesChange: Explain

    Set the organization default, then update existing sites in waves of similar size, largest first.

    Move on when: Each wave completes with no increase in restore requests

  5. Hand over and publish the standardChange: Sustain

    Publish the version standard and how to request an exception, and hand monitoring to operations.

    Move on when: Service desk and site owners know the standard and the exception route

Common challenges

  • If youTrim existing versions on every site straight away

    What tends to happenVersions people expected to restore are gone for good, because trim jobs bypass the recycle bin.

    A better approach

    Run what-if analysis first, trim in waves, and check whether your backup arrangements cover what you are about to delete.

  • If youExpect limits to shrink content under retention or legal hold

    What tends to happenStorage on those sites stays the same and the project looks like it failed.

    A better approach

    Tell stakeholders up front that retained and held content is exempt, and measure savings on the sites limits can affect.

  • If youSet very low manual limits to save more storage

    What tends to happenPeople lose versions they need, and site owners start requesting exceptions.

    A better approach

    Use automatic limits. Microsoft advises against limits below 100 versions or 30 days.

  • If youChange the default without telling site owners

    What tends to happenThe first missing version becomes a support escalation instead of an expected outcome.

    A better approach

    Explain the change and the exception process before the default changes, not after.

Checkpoints

Pilot

  • Do we have a storage baseline for every pilot site?
  • Did the what-if report run on each pilot site?
  • Are pilot owners seeing no lost work after two weeks?

Production

  • Is the organization default set to automatic?
  • Are existing libraries updated in every planned wave?
  • Is the exception list documented with a reason for each?
  • Do the service desk and site owners know how to request an exception?

Success measures

Capture a baseline before you start, or you won't be able to show the change.

MeasureWhere you see itGood direction
Total SharePoint storage usedSharePoint admin center storage reporting Down
Version storage on the largest sitesVersion storage usage report Down
Restore requests for missing versionsService desk tickets Steady
Extra storage purchasedMicrosoft 365 billing Down

Ready-to-use text

Message to site owners before the change
From [date], SharePoint will keep file versions automatically: recent versions are kept in full, and older versions are thinned out over time. Most people will notice no difference. If your site needs to keep more versions, for example for regulated work, reply to this message before [date] so we can review it with you.

Additional reading

Changelog

Changelog (1 version)
Published versions of this playbook
VersionDateAuthorChange
1Sev DerghazarianFirst published. Placeholder draft for review; facts checked against Microsoft Learn.