Skip to main content

Retention Labels

Retention labels are the item-level retention tool in Microsoft Purview. A label applied to a document or list item declares how long the item must be kept, what happens when the period ends, and whether it becomes a locked record. Unlike a retention policy, which blankets an entire site, a label travels with the individual item, and an item can carry only one label at a time. For organizations with legal, regulatory, or audit obligations, retention labels turn SharePoint libraries into a defensible records system without third-party software.
Related Features
Adaptive Scopes, Audit Log, Preservation Hold Library, Retention Policies

Common Use Cases

  • Contract lifecycles: retain each contract for a set number of years after its expiration date using event-based retention
  • Financial records: keep invoices and statements for the legally required period, then dispose of them automatically
  • HR documentation: retain employee files based on events such as termination, with different rules per document type
  • Official policies: mark approved policies as records so they cannot be quietly altered or deleted
  • Library-wide defaults: set a default label on a library, folder, or document set so everything filed there is labeled on arrival
  • Controlled cleanup: apply delete-only labels to working libraries so stale drafts disappear after a defined period

Benefits

  • Item-level precision: different rules for different documents inside the same library, instead of one blanket rule per site
  • Labels travel: a retention label stays with the file when it moves to another location within the Microsoft 365 tenant
  • Records capability: only labels can declare content a record or regulatory record, the gold standard for tamper resistance
  • Automation options: default labels, auto-apply conditions, and trainable classifiers label content without user effort
  • Defensible disposition: disposition review adds human approval and documented proof of deletion at the end of retention
  • User-visible clarity: the applied label shows on the item, so everyone can see which rule governs a document

How It Works

  • Centrally defined, locally applied: labels are created in Microsoft Purview and published to SharePoint locations, which can take up to seven days
  • One label per item: each document or list item carries at most one retention label, and applying another replaces it
  • Manual or automatic: users can apply published labels themselves, libraries can set a default label, and auto-apply policies match content by sensitive information types, keywords, or trainable classifiers
  • Preservation Hold Library: when retained content is edited or deleted, SharePoint preserves a copy in this hidden library for the rest of the retention period
  • Event-based retention: for rules like seven years after contract expiration, the retention clock starts when the matching event is triggered in Purview
  • Configurable retention settings: a label sets a retention period (days, months, years, or forever), a start trigger (creation, last-modified, label-applied, or a custom event), and an end-of-retention action (auto-delete, disposition review, or simply stop retaining)
  • Record status and file plan: a label can mark items as records or regulatory records with escalating restrictions, with optional file plan descriptors documenting why the rule exists

Limits and Nuances

  • One label, period: there is no stacking; a second label replaces the first, so label design has to anticipate overlaps
  • Explicit beats implicit: an item’s retention label takes precedence over a site-wide retention policy covering the same content
  • Seven-day lag: publishing labels and auto-applying them can each take up to seven days to reach all locations
  • Licensing matters: auto-apply based on sensitive information types or trainable classifiers, and disposition review, require higher-tier Microsoft 365 licensing
  • Records lock hard: a record cannot be deleted, and a regulatory record cannot be unlocked or have its label removed, even by administrators
  • Copies are not labeled: downloading or copying a file produces an unlabeled copy; the label follows the original item, including moves within the tenant

Common Questions About Retention Labels

What is a retention label in SharePoint?

A retention label is a Microsoft Purview tag applied to an individual document or list item that controls how long the item is kept and what happens afterward. A label can retain content, delete it at the end of the period, or both, and it can declare the item a record. Labels are created and published centrally, then applied manually or automatically in SharePoint.

What is the difference between a retention label and a retention policy?

Scope. A retention policy covers an entire location, such as a whole SharePoint site, and applies invisibly to everything in it. A retention label applies to one specific item and travels with it. Policies set the broad baseline; labels handle exceptions, records, and event-based retention. Most organizations use both, with labels taking precedence on the items that carry them.

Can a file have more than one retention label?

No. One retention label per item is a hard rule. Applying a different label replaces the existing one, unless the item is a record, in which case the label is locked down. When multiple retention settings could apply, Purview follows its principles of retention: retention wins over deletion, and an explicit label takes precedence over an implicit site-wide policy.

What happens when someone edits or deletes a labeled file?

If the label is set to retain the content, SharePoint quietly preserves it. When a user deletes a retained file, a copy is kept in the hidden Preservation Hold Library, where it stays for the rest of the retention period. The user experience is unchanged, but the organization can always produce the content if a regulator, auditor, or court requires it.

What does marking an item as a record do?

A record label locks the item. Once content is marked as a record, it cannot be deleted, and editing requires unlocking the record first, with each unlock tracked. A regulatory record goes further: it cannot be unlocked, the label cannot be removed, and even administrators cannot relax the restrictions. Records are how SharePoint provides defensible, tamper-resistant retention.

Do I need third-party software for records management in SharePoint?

Usually not. Retention labels, auto-apply policies, event-based retention, and disposition review are all native Microsoft Purview capabilities that work directly on SharePoint content. Greg Zelfond builds LookBook 365 document centers on exactly this out-of-the-box stack, pairing labeled libraries with sensible metadata. The main consideration is licensing, since the automation features require higher-tier Microsoft 365 plans.