How to Set SharePoint Retention Policies
Retention policies tell SharePoint how long to keep content and what to do when that time is up. Set well, they handle compliance automatically.
What it is
Retention policies are rules that govern how long content is kept and what happens when it reaches the end of its life. Set up at the tenant level by an admin, applied to libraries, sites, or specific content types, retention policies enforce keeping content for a defined period — and (depending on configuration) automatically deleting it afterwards, or marking it for review.
Retention is fundamentally a compliance tool. Different industries have different requirements: financial records often need to be kept 7+ years; medical records, much longer; HR records, varying by jurisdiction. Retention policies make this systematic — instead of relying on individual users to remember ‘don’t delete this for 7 years’, the system enforces it.
For end users, retention is mostly invisible. You create and edit content normally; the policies work in the background. Where it does become visible is when retention prevents deletion (‘You can’t delete this — it’s under retention until 2031’), or when retention triggers a review or auto-delete after the retention period ends. Knowing retention exists helps you understand why some content can’t be deleted casually.
When to use this
- When you need to comply with industry regulations on document retention.
- When you want to systematically manage content lifecycle at scale.
- When you’ve inherited a tenant with no retention rules and need to fix it.
- When you’re setting up a new site or library for regulated content.
How to do it
- Identify the content types and retention periods required (often via your compliance team).
- Work with your SharePoint admin to set up retention labels in the Microsoft Purview compliance centre.
- Apply retention labels to libraries, sites, or content types.
- Test with sample content to confirm the policy behaves as expected.
- Document the retention scheme for users and admins.
- Communicate to users when retention prevents normal deletion (so they understand it’s deliberate).
- Review the retention scheme periodically as regulations and business needs change.
Best practices
- Centralise retention decisions. Don’t let individual library owners invent their own retention rules.
- Document the rationale. ‘Why do we keep this for 7 years?’ should have a written answer.
- Use labels consistently. Different content types may have different retention, but the labels should be standard.
- Audit retention coverage. Content without retention labels is content not under management.
Common mistakes
- Setting retention without compliance input. Guessing retention periods can create real legal risk.
- Letting retention conflict with business needs. Aggressive auto-delete on active content disrupts work.
- Applying retention inconsistently. Some libraries have it, some don’t — chaos at audit time.
The Governance Starter Kit gives you the plain-English governance system for real organisations. The 5 governance domains, the Roles & Responsibilities Matrix, the Library Standards Audit, the Monthly Governance Routine — and the 5-day Start This Week plan.
Get the Governance Starter Kit — $29 →FAQ
How do I set retention policies in SharePoint?
Retention is configured in Microsoft Purview compliance portal, not in SharePoint itself. Create a retention label with the rule (e.g. retain for 7 years, then delete). Apply the label automatically based on content type or location, or let users apply it manually. SharePoint enforces the policy across affected libraries.
What’s the difference between SharePoint retention and version limits?
Version limits control how many versions of each file are kept. Retention policies control how long files exist at all (and what happens when retention expires). Version limits affect storage; retention affects compliance. Most regulated organisations need both.
Can SharePoint retention prevent deletion of important files?
Yes — retention labels can be configured to prevent deletion. When applied, users cannot delete the file (or attempts go to a hold area instead of the Recycle Bin) until the retention period expires. Useful for legal hold, compliance records, and audit-critical content.
Should I use SharePoint retention or simple archive libraries?
Use archive libraries for operational organisation (keeping the active library clean). Use retention policies when compliance, legal, or regulatory requirements dictate how long content must be kept. Most mature organisations use both: archive for hygiene, retention for compliance.