SharePoint retention labels and retention policies solve related but different information-governance problems. This guide explains how to choose between them, map records to retention requirements, configure a controlled test, document exceptions, and preserve evidence that your Microsoft 365 compliance process is operating as intended.
Overview
Retention in SharePoint should begin with the organization’s records schedule, not with a particular Purview setting. First identify what information must be retained, why it must be retained, how long the period lasts, and what should happen at the end of that period. The technology configuration should then express those approved business rules.
In broad terms, a retention policy is useful when the same rule should apply across a broad scope, such as selected SharePoint sites or locations. A retention label is more targeted: it can be applied to an individual document or item when retention depends on the content’s classification. A record label adds stricter records-management behavior where the organization needs to control changes or deletion according to its recordkeeping requirements. Exact capabilities, terminology, licensing, and interface locations can change, so the Microsoft Purview documentation and the organization’s licensing terms should be checked before deployment.
| Control | Best fit | Key design question |
|---|---|---|
| Retention policy | Broad coverage for content in a defined location or set of locations | Should this rule apply to most or all content in the selected scope? |
| Retention label | Item-level classification for documents or list items with different retention needs | Can users, automation, or records staff identify the content category reliably? |
| Record label | Content that must be managed as an official record with additional restrictions | What controls are required after declaration, and who can authorize disposition? |
These controls are not a substitute for backup, version recovery, or a complete security program. Retention addresses how long content is preserved and how its lifecycle is managed; it does not by itself replace a SharePoint backup and restore plan. For a broader recovery comparison, see SharePoint Backup and Restore Comparison.
What to track
1. Maintain a records-classification mapping
Create a controlled register before creating labels. A practical mapping template should include:
- Business function: the process that creates or receives the information.
- Content category: for example, a contract, personnel record, project file, financial record, or operational correspondence.
- Authoritative location: the SharePoint site, library, list, or other Microsoft 365 location that owns the record.
- Retention trigger: creation, last activity, contract end, case closure, employee departure, or another approved event.
- Retention period: the approved duration, recorded with its source and effective date.
- Disposition outcome: delete, transfer, review, or retain for a further period.
- Record status: whether the category requires formal record declaration or additional restrictions.
- Owner and approver: the business owner, records manager, privacy contact, and technical administrator responsible for the rule.
Do not create a separate label for every variation unless there is a genuine difference in retention, disposition, or control. A smaller, understandable label set is easier to apply, test, explain, and audit.
2. Track configuration and dependencies
For each policy or label, record its name, purpose, scope, retention trigger, disposition action, event-based requirements, publication status, and date of last review. Also note whether the control depends on user classification, automated labeling, a file plan, a workflow, or a disposition review.
Keep licensing assumptions in the register rather than treating them as permanent facts. Confirm that the organization’s subscription and user coverage support the intended feature set, especially where advanced records management, event-based retention, or disposition review is involved.
3. Track evidence, not just settings
A screenshot of a configuration page shows what an administrator selected; it does not prove that the control behaved correctly. Maintain evidence for representative test items, including the item path, label or policy applied, test date, expected result, observed result, reviewer, and any relevant audit or activity record. Store evidence where access is controlled and where its own retention requirements are understood.
Cadence and checkpoints
Before configuration
- Obtain the approved retention schedule and identify unresolved legal, regulatory, or business-owner questions.
- Inventory SharePoint sites, libraries, lists, and content types that fall within scope.
- Choose the least complex control that meets the requirement: broad policy coverage where appropriate, item-level labels where classification matters, and record controls where formal records treatment is required.
- Confirm licensing, administrative roles, supported locations, and interactions with other retention or legal-hold controls.
- Write a plain-language label description that tells users when to apply it and what happens afterward.
During a controlled test
Use a dedicated test library or another agreed non-production scope. Include ordinary documents, modified documents, files with multiple versions, list items, documents that should remain outside scope, and content with an intentionally incorrect classification. If event-based retention is planned, test the event trigger separately and document who supplies the event date.
For each test case, capture:
- the item name and location;
- the expected retention start and end behavior;
- whether editing, moving, renaming, or deleting is allowed;
- whether a disposition review is expected;
- the observed behavior and time of observation;
- the evidence location and tester’s sign-off.
Allow for processing delays and avoid declaring success immediately after a configuration change. The test plan should define when to check again and what evidence is sufficient. Keep the test set reusable so it can be run after a material configuration change or service update.
After deployment
Use a monthly or quarterly operational check, depending on risk and change volume. Review new labels, policy changes, failed or ambiguous classifications, disposition-review queues, unusual deletion activity, and exceptions that have passed their expiry date. A quarterly SharePoint site health review can complement this work by checking ownership, content locations, and lifecycle conditions; see the SharePoint Site Health Review guide.
How to interpret changes
A change in content volume does not automatically mean that the retention design is wrong. First determine whether the change reflects a new business process, a migration, a label-publishing change, an automation error, or a genuine shift in records creation. Compare the result with the classification register and the approved schedule.
Use an exception log with these fields:
- exception ID and date raised;
- site, library, item category, or process affected;
- expected control and observed issue;
- risk assessment and temporary safeguard;
- assigned owner and target resolution date;
- decision, evidence, and closure approval.
Common warning signs include labels with overlapping descriptions, content that cannot be classified by ordinary users, large numbers of unlabeled records in a label-dependent process, policies scoped more broadly than the approved schedule, and disposition decisions made without documented business-owner review. Treat these as design or operating questions to investigate rather than as proof of noncompliance.
When a policy or label changes, compare the old and new scope, trigger, duration, action, and affected content. Record whether the change is prospective, changes how existing items are handled, or requires a migration and relabeling exercise. If content is being moved between sites or tenants, include retention behavior in the migration test plan rather than assuming it will transfer unchanged. The SharePoint Migration Tool Comparison provides useful context for broader migration planning.
When to revisit
Schedule a formal review at least semiannually, and bring it forward when the retention schedule, business function, regulation, organizational structure, or Microsoft Purview capability changes. Revisit the design after a merger, site restructuring, major SharePoint migration, new records category, legal-hold event, audit request, or deployment of a new label set.
At each review, complete this action list:
- Compare the live configuration with the approved records-classification register.
- Verify that owners, approvers, descriptions, scopes, and licensing assumptions remain current.
- Run the reusable test library and record expected-versus-observed results.
- Review exceptions, disposition activity, unlabeled content, and evidence retention.
- Confirm that user guidance and administrator procedures still match the interface and behavior.
- Approve, revise, retire, or replace labels and policies through the organization’s change process.
The most defensible SharePoint retention program is not the one with the most labels. It is the one that connects an approved records schedule to understandable controls, repeatable testing, accountable decisions, and evidence that can be produced when questions arise. Keep this checklist with the governance register and update it whenever Microsoft 365 compliance features, business rules, or audit expectations change.