Qutzl LLC LogoQutzl Insights

Tutorial

Purview retention without boiling the ocean

A practical starter for Microsoft Purview retention labels in a small Microsoft 365 tenant — keep what you must, delete what you should, and avoid a year-long taxonomy project.

Updated 3 min readBy Michael NarehoodMicrosoft 365

Email retention vs “archive” confusion is already common in SMB tenants. Microsoft Purview can help — or it can become an endless labeling religion. This tutorial is the minimum useful start: a few labels, clear owners, and policies you can explain to leadership.

1. Decide the business rules first

Write three sentences with the owner of the company (or counsel if you have it). Microsoft’s retention model can retain content, delete it, or retain it and then delete it; it cannot decide which legal or business obligation applies to you.

  • How long do we keep ordinary business email / files by default?
  • What must we keep longer (finance, HR, contracts)?
  • What should we delete on purpose so old junk is not discovery fuel forever?

If nobody will answer those, stop. Technology will not invent policy.

2. Create a tiny label set

Start with something like:

  • General business — 3 years (or whatever your default is)
  • Finance / tax — 7 years (match your accountant’s reality)
  • HR confidential — defined period
  • Do not retain / transient (optional, for clearly disposable spaces)

You can grow later. Do not invent twenty labels on day one.

First decide whether each rule belongs in a policy or a label. Microsoft distinguishes a retention policy for applying the same settings across a whole mailbox or site from a retention label for individual emails or documents that need different settings. The sample periods above are placeholders, not legal advice.

3. Apply with auto-policies where it is safe

Use automation only where you understand false positives. Many SMBs do well by:

  • Publishing labels so users can apply them on purpose for contracts and HR
  • Using a broad retention policy for a mailbox or SharePoint site that truly has one rule
  • Applying a default label to a known-purpose SharePoint library, folder, or document set
  • Leaving noisy personal OneDrive alone until defaults are proven

Microsoft documents those exact policy-versus-label scopes in its retention overview. For condition-based auto-apply labels, use simulation mode to review matches and refine the policy before turning it on. Train a pilot group before you auto-label the whole company.

4. Prove a keep and a delete

  1. Use a dedicated test site or mailbox with content you can safely delete
  2. Confirm the policy distribution status, then confirm content is retained as expected
  3. Confirm disposable content actually expires when policy says it should
  4. Document where admins view disposition and audit activity

Purview is not immediate: Microsoft says retention policies and auto-applied labels can take up to seven days to apply. Build that delay into the test rather than declaring failure after an hour. If you cannot eventually show both keep and delete behavior, you do not have retention — you have hope.

5. Assign owners and a review date

Retention without an owner drifts. Put a calendar reminder: annual policy review with leadership, and a tech check that labels still publish.

Bottom line

Purview retention works for SMBs when policy is short, labels are few, and you test keep-and-delete behavior before wide auto-apply. Skip the enterprise taxonomy until the basics are boring.