If you manage Microsoft 365, particularly SharePoint Online and OneDrive, you’ll probably be familiar with the storage challenges that come with document version history.
Versioning is incredibly useful. It allows users to recover previous versions of documents, investigate changes and restore content when something goes wrong.
But there’s another side to it.
In organisations with large SharePoint environments, heavily edited documents can accumulate significant numbers of versions. Multiply that across thousands of sites, libraries and users, and the storage footprint can become substantial.
Now add Microsoft Purview retention policies into the equation.
Historically, content subject to a retention policy or eDiscovery hold has been protected from normal SharePoint version history limits. This is important from a compliance perspective, but it can also mean that version storage grows beyond the limits administrators would normally expect.
Microsoft roadmap item 575284 is looking to address this.
👉 What is Microsoft Purview Roadmap 575284?
The roadmap item is titled:
Microsoft Purview: Data Lifecycle Management – Enable version trimming for data covered by retention policies in OneDrive and SharePoint.
The planned capability will allow administrators with the appropriate Purview permissions to enable version cleanup for SharePoint and OneDrive content, even when retention policies are in effect.
The intention is to allow SharePoint version management to trim file versions according to configured limits, while maintaining the necessary protections for specific content that must be preserved.
In other words, Microsoft is looking to give organisations more control over the storage impact of version history without simply removing their retention controls.
Roadmap details:
- Roadmap ID: 575284
- Product: Microsoft Purview – Data Lifecycle Management
- Status: In development
- Planned preview: November 2026
- Planned rollout: January 2027
- Platform: Web
These are planned dates, not guaranteed delivery dates. Check the roadmap for the latest status before making deployment plans.
👉 Why does this matter?
Let’s consider a practical example.
Imagine an organisation with 20,000 SharePoint sites and several million documents.
A particular Finance document might be updated dozens of times each month. Each update creates another version.
Under normal circumstances, SharePoint version history settings help control how many versions are retained.
However, if that document is subject to a retention policy, the normal version history limits may not apply in the same way.
This is intentional. Microsoft needs to ensure that retention and eDiscovery obligations are honoured.
But consider the consequences:
- More versions are retained than administrators anticipated.
- Storage consumption increases.
- Administrators have less flexibility when managing version history.
- Storage planning becomes more complicated.
- Organisations may struggle to balance recovery requirements, compliance and storage costs.
Roadmap 575284 is intended to give administrators another option.
👉 What could administrators do with this?
The most interesting aspect is the potential to bring version management and retention management closer together.
Here are three areas where I think this could make a difference.
1. Better SharePoint storage management
Organisations could potentially apply more controlled version history limits to content covered by retention policies.
This could help reduce unnecessary version accumulation and improve storage management across large SharePoint and OneDrive estates.
However, don’t assume this means every historical version can be deleted. Specific protected cases will continue to require preservation.
2. More flexibility for retention policies
Retention policies exist to meet business, regulatory and legal requirements.
They aren’t necessarily designed to retain every intermediate version of every document indefinitely.
There is an important distinction between retaining the information an organisation is obligated to preserve and retaining every historical version generated during normal document collaboration.
This roadmap item is interesting because it recognises that distinction.
3. Better alignment between compliance and operational requirements
Historically, administrators have often had to consider retention and version management as separate concerns.
This capability could provide more flexibility to manage both together.
For example, an organisation might want to preserve information for seven years while applying sensible version history limits to reduce unnecessary storage consumption.
The important thing will be understanding exactly which versions remain protected and how the new behaviour interacts with retention policies, eDiscovery holds and records.
👉 What should you be doing now?
Although the feature is still in development, there are several things I’d recommend reviewing before it arrives.
1. Understand your current version storage
Look at your SharePoint and OneDrive storage consumption.
Identify sites and libraries where version history is contributing significantly to storage usage.
Don’t assume the largest sites are necessarily the biggest contributors. A smaller library containing frequently updated documents can accumulate substantial version history.
2. Review your version history settings
Understand the version limits currently applied at tenant, site and library level.
Remember that SharePoint supports different configuration levels, and individual sites or libraries can have settings that differ from the organisation defaults.
3. Review retention policies and eDiscovery holds
Identify which SharePoint sites and OneDrive accounts are covered by retention policies or eDiscovery holds.
Understand why the content is being retained and whether the organisation has documented requirements around historical versions.
4. Identify records and regulated content
Pay particular attention to records management requirements.
A document declared as a record has additional protection considerations. Do not assume that version trimming will treat records in the same way as ordinary documents.
5. Establish a governance position
Before enabling any version trimming capability, agree:
- Which workloads and sites are in scope?
- What version history limits are appropriate?
- Which content must retain historical versions?
- What recovery requirements apply?
- Who is authorised to configure and approve changes?
- How will the impact be assessed and monitored?
I would strongly recommend testing with a representative set of sites before applying any new configuration more broadly.
👉 One important distinction: retention versus version history
This is the part I think administrators need to understand.
Retention and version history solve different problems.
Retention is about ensuring information is preserved for a defined period or according to a particular business or regulatory requirement.
Version history is about maintaining previous iterations of a document so that changes can be reviewed or content can be restored.
They overlap, but they aren’t the same thing.
A retention policy doesn’t automatically mean that every version must be retained forever. Equally, reducing version history doesn’t mean that an organisation can ignore its retention obligations.
Microsoft’s existing documentation explains how SharePoint version trimming interacts with retention policies and eDiscovery holds. It is worth reading before planning any changes.
💡 The Jim Talks takeaway:
I think roadmap 575284 is a welcome development for organisations managing large SharePoint and OneDrive environments.
For years, administrators have had to balance three competing considerations:
- Protecting information to meet compliance obligations.
- Maintaining useful document recovery capabilities.
- Controlling the storage footprint of Microsoft 365.
This update has the potential to give organisations more flexibility in managing that balance.
But the real opportunity isn’t simply deleting old versions to save storage.
It’s being able to make more informed decisions about what needs to be retained, what needs to remain recoverable and what version history can be managed more efficiently.
Good information governance isn’t about keeping everything forever. It’s about retaining the right information, for the right reasons, for the right amount of time.
That’s the conversation I’d be having before enabling this capability.
Further reading
- Microsoft 365 Roadmap – ID 575284
- Microsoft Learn – Trim existing versions in SharePoint
- Microsoft Learn – Version history limits for SharePoint and OneDrive
- Microsoft Purview – What’s new
Roadmap information checked: 6 November 2026. Feature availability and timelines are subject to change.
Leave a Reply