How to Access Word OneDrive Version History Beyond the Default 90 Days

When you edit a Word document saved to OneDrive, Word automatically saves versions of your work. By default, OneDrive keeps version history for 90 days. After that period, older versions are deleted and become unrecoverable through the standard File > Info > Version History interface. This article explains how to extend the version retention period for your OneDrive for Business or SharePoint document libraries so you can access Word versions older than 90 days. You will learn the steps to change the retention policy and what limitations apply to personal OneDrive accounts.

How OneDrive Version History Works for Word Documents

Word documents saved to OneDrive or SharePoint Online automatically generate a new version each time you save. Word for Microsoft 365 saves automatically every few seconds by default, which means a single editing session can produce dozens of versions. OneDrive retains these versions for 90 days from the date each version was created. After 90 days, the version is permanently removed from the server and cannot be recovered.

The 90-day default applies to all OneDrive personal accounts and all OneDrive for Business and SharePoint document libraries unless an administrator changes the retention policy. The setting that controls version retention is located in the tenant-level or site-level versioning settings, not inside Word itself. This means accessing older versions requires changing a server-side policy rather than a Word option.

Who Can Change the Version Retention Policy

Only a SharePoint Online administrator or a site collection administrator can modify version retention for a document library. For OneDrive for Business, the user who owns the OneDrive can change the retention setting for their own library if they have the appropriate permissions. For personal OneDrive accounts (onedrive.live.com), there is no option to extend version retention beyond 90 days. The steps below apply to OneDrive for Business and SharePoint Online only.

Steps to Change Version Retention for a OneDrive for Business Document Library

These steps assume you have owner or administrator access to the OneDrive for Business site or SharePoint site where the Word document is stored.

1. Open the document library settings
   Navigate to the OneDrive for Business or SharePoint site in your browser. Click the gear icon in the upper right corner and select “Library settings.” If you do not see “Library settings,” click “Site contents” first, find the document library, hover over it, click the three dots (ellipsis), and choose “Settings.”
2. Locate the Versioning settings page
   In the Settings page, under the “General settings” section, click “Versioning settings.”
3. Change the version retention value
   On the Versioning Settings page, find the section labeled “Require content approval for submitted items?” — leave this as “No” unless you need approval workflows. Scroll down to “Document Version History.” Under “Keep the following number of major versions,” enter a number that reflects how many versions you want to keep. Under “Keep drafts for the following number of major versions,” enter a value for minor versions if you use them. Below these, you will see “Keep versions for the following number of days:” Change the default 90 to a higher value such as 365 for one year or 730 for two years. The maximum allowed value is 99,999 days. Alternatively, select “Never delete versions” to retain all versions indefinitely. Click “OK” to save.
4. Verify the change
   Return to the document library and open a Word document. Go to File > Info > Version History. Versions older than the previous 90-day limit will not appear retroactively unless they were created after the new policy was applied. Only versions created from the moment the policy change takes effect onward will be retained for the new duration.

Using PowerShell to Set Version Retention on SharePoint Document Libraries

For administrators managing multiple sites, the SharePoint Online Management Shell with the PnP PowerShell module allows you to set version retention programmatically. This method is useful when the web interface does not expose the exact retention duration you need or when you need to apply the setting to hundreds of libraries.

1. Install the PnP PowerShell module
   Open PowerShell as an administrator and run: Install-Module PnP.PowerShell -Scope CurrentUser. If prompted, confirm the installation.
2. Connect to your SharePoint tenant
   Run: Connect-PnPOnline -Url https://yourtenant.sharepoint.com/sites/yoursite -Interactive. Replace the URL with your actual site address. Sign in with an administrator account.
3. Set the version retention policy
   Run: Set-PnPListVersionPolicy -List "Documents" -EnableVersionExpiration $true -ExpireVersionsAfterDays 730. This example sets the retention to 730 days. Replace “Documents” with the name of your document library. Set $false to disable expiration and keep all versions forever.
4. Confirm the policy
   Run: Get-PnPListVersionPolicy -List "Documents" to verify the retention value is applied.

If Word Version History Still Does Not Show Old Versions

Versions Created Before the Policy Change Are Still Deleted

Changing the retention policy does not restore versions that were already deleted. If a version was created 100 days ago and the default 90-day policy was in place at that time, that version was deleted on day 91 regardless of when you change the policy. The new retention duration applies only to versions created after the policy change. To preserve versions from the past, you must change the policy before the 90-day window expires.

Personal OneDrive Accounts Cannot Extend Version History

If you use a personal OneDrive account (onedrive.live.com) with a free or Microsoft 365 Personal subscription, you cannot change the version retention period. The 90-day limit is enforced by Microsoft and cannot be adjusted through any user-facing settings. The only way to keep a specific version beyond 90 days is to manually download a copy or use File > Save As to create a separate file before the version expires.

Version History Shows Fewer Versions Than Expected

Even with an extended retention period, OneDrive limits the total number of versions stored per file. The maximum is 500 major versions. If your document generates more than 500 versions within the retention period, the oldest versions are deleted to stay under the 500-version cap. To reduce version count, increase the auto-save interval in Word Options > Save > Save AutoRecover information every N minutes, or manually save less frequently during heavy editing sessions.

OneDrive for Business vs SharePoint: Version Retention Capabilities

Item	OneDrive for Business	SharePoint Online
Default retention period	90 days	90 days
Maximum retention via web UI	99,999 days or never delete	99,999 days or never delete
Retroactive application	No — only new versions after change	No — only new versions after change
Maximum versions per file	500 major versions	500 major versions
User can change retention	Yes, if owner of the site	Only site collection admin
Personal OneDrive option	Not available	Not applicable

The table shows that both OneDrive for Business and SharePoint Online offer identical version retention capabilities. The key difference is who can change the setting: the OneDrive owner for OneDrive for Business versus a site collection administrator for SharePoint. Personal OneDrive accounts cannot extend retention at all.

You can now access Word version history beyond the default 90 days by changing the retention policy in your OneDrive for Business or SharePoint document library settings. If you manage an organization, use the PowerShell method to apply the policy across multiple sites at once. For personal OneDrive users, the only workaround is to manually save critical versions as separate files before the 90-day window closes. As an advanced tip, combine the extended retention policy with the 500-version limit by setting a reasonable retention duration such as 365 days and increasing the auto-save interval to 10 minutes to avoid hitting the version cap during heavy editing.