SharePoint version history vs. retention: what survives an edit or deletion?

If you need yesterday’s wording back, start with Version history. If you need to know whether a deleted contract remains available for an authorized retrieval, check the retention policy or label that applies to that file. If the question is whether people can change it at all, check its record state. A successful restore answers the first question; it does not establish the answers to the other two.

Restore an earlier draft

In the document library, open the item’s menu, choose Version history, open the menu for the version you want, then select Restore and confirm with OK. SharePoint makes a copy of that earlier version the new latest version. It does not remove the earlier entry from history. If Version history is missing, check More in the item menu and ask the library owner to confirm the configuration. Microsoft’s restore instructions

Suppose a contract draft says $50 on Monday. Someone accidentally changes it to $60 on Tuesday. On Wednesday, the team restores Monday’s version. The working document can say $50 again, but Wednesday’s restore is a new current version. The version sequence and the document’s original creation date have not been rewound. This is an illustration of the documented restore behavior, not a tenant test.

The library owner can review Settings > Library Settings > Versioning settings to see whether the library uses major versions only or major and minor versions, who can see drafts, and what version limits apply. Versioning provides a route to earlier working content while the needed version exists; its settings alone are not a retention guarantee. Microsoft’s versioning instructions

What an edit or deletion can leave behind

For controls configured to retain content during an applicable retention period, Microsoft describes the following edit and delete behavior. Check the file’s actual policy scope, label, record settings and holds. A delete-only configuration does not promise a retained compliance copy. SharePoint retention policies · Records management

Applicable state	Edit	Delete
Policy configured to retain the file	Original content is preserved when required; see the first-edit exception below.	Original content is preserved.
Standard retention label	The label alone does not create a preserved copy just because the file is edited.	Content is normally preserved, subject to records management settings.
Locked record	Content editing is blocked.	Deletion is blocked.
Unlocked record	Content editing is allowed and creates a preserved copy.	Deletion is blocked.
Regulatory record	Content editing is blocked.	Deletion is blocked.

Microsoft notes that newly created content is not copied to the Preservation Hold library on its first edit. Retaining all versions requires versioning. This hidden library is an automatic preservation location, not an interactive archive; editing, deleting, or moving its retained files yourself is unsupported. Authorized retrieval uses compliance tools such as eDiscovery. Microsoft’s SharePoint retention guidance

A record lock concerns content editing. A locked record can still allow property changes, including renaming, unless the tenant blocks them. For a regulatory record, property editing is also blocked, and even a global administrator cannot remove the regulatory label. Check the label’s actual classification before asking someone to unlock it. Microsoft’s record restrictions

When Contract-A.pdf disappears

Imagine a coworker cannot find Contract-A.pdf in the usual library. That observation does not yet tell you whether the file was deleted, moved, viewed in the wrong library, or preserved under a retention control. Nor would an unsuccessful search of the ordinary folder establish that a hidden compliance copy is gone.

First, identify the actual site and library and the file’s URL or other precise identifier. Check whether the item is elsewhere in the working library and whether an eligible item appears in the visible Recycle Bin. If the question concerns an older version, make that explicit: Microsoft says a manually deleted version goes to the Recycle Bin, while versions removed through automatic or age-based trimming are not recoverable there after purge. Microsoft’s version FAQs

Then ask the owner or administrator which policy and label actually applied to Contract-A.pdf, whether it was a record, and who is authorized to search for retained content. A label available for users to apply does not prove this particular item has it. Record the applied label separately from any site policy confirmed to cover the file. Do not delete a real record to find out which rule wins.

Version limits deserve a separate check. A limit based on count answers a different question from one involving age: 100 edits and 100 days are different histories. Automatic version storage keeps more detail from recent activity and less from older activity; an inactive document can also lose old history through expiration. Changing an expiration limit applies to newly created versions, while a count change can progressively affect existing versions as the item is updated. An applicable retention policy or hold can extend a version’s expiry. Ask for the configured settings and the version you need, rather than assuming a universal number of recoverable drafts. Version storage planning · Version limit FAQs

Ask when retention starts

“Keep it for three years” is incomplete without a start event and an approved schedule. Event-driven retention can start from an event such as a contract’s expiration, rather than its creation date; the event information matters. Microsoft’s event-driven retention guidance

For arithmetic only, imagine a fictional approved rule saying retain for three years after the contract ends. A document created on February 15, 2024, for a contract ending September 30, 2026, reaches that three-year calendar anniversary on September 30, 2029. Counting from creation gives a different date. Neither calculation proves that a file will be deleted on that day: the applicable rule, other holds, and disposition still need to be established.

For a support request, state the problem in terms the owner can investigate: “The file at this site and library URL is missing from the working folder,” or “Version history opens, but the Monday draft is absent,” or “The Version history menu is absent.” Include when you observed it, the versioning settings if known, the current label and record lock state, the policy confirmed to cover the location, the approved schedule and start trigger, and the role authorized to retrieve retained content. Retention labels can classify records or regulatory records and carry disposition behavior, so the exact state matters. Microsoft’s records management overview

Record the unresolved recovery question

Download the blank recovery and retention notes CSV. It has space for the document URL, required version, actual version settings, applicable retention control, record state, start trigger, approved schedule, covered location, evidence date, retrieval role, and unresolved question. Keep the filled file privately. It is a set of questions for your own document, not a Microsoft export or proof of a configured policy.

For the hypothetical missing Contract-A.pdf, version_recovery_need could say “Monday wording needed,” while unresolved_question could ask “Was this file covered by a retention policy on the date it disappeared?” Leave retention_control blank until someone verifies the applicable control.

The recovery and retention behavior above follows the linked Microsoft documentation. The amounts, dates, contract and worksheet examples are illustrative. No live tenant recovery was performed, and the article does not determine your organization’s legal retention obligation.