Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.4.3. Data Lifecycle Management and Retention

💡 First Principle: Retention exists for two opposite obligations: keeping records long enough to satisfy law and litigation, and deleting data you no longer need so it can't leak. Purview resolves conflicts between those obligations with fixed principles, so you can predict any item's fate.

Retention policies vs retention labels:
Retention policyRetention label
Applies toWhole locations (mailboxes, sites, Teams, Copilot interactions)Individual items
Teams chats and channel messages, Viva Engage, Copilot and AI appsYesNo
Applied by users manuallyNoYes (once published by a retention label policy)
Auto-applied by condition (SITs, keywords, trainable classifiers)NoYes (auto-apply label policy)
Travels with content when moved within the tenantNoYes
Declare as a record, event-based retention, disposition reviewNoYes

A retention label reaches users through a retention label policy (publish to locations) or an auto-apply policy. An item can carry only one retention label at a time.

Principles of retention resolve conflicts, applied in order:

  1. Retention wins over deletion — if any policy or hold says keep, the item isn't permanently deleted (it may vanish from the user's view).
  2. The longest retention period wins.
  3. Explicit wins over implicit for deletion — a label's delete action beats a policy's; among policies, a specifically scoped one beats an org-wide one.
  4. The shortest deletion period wins.

Scopes. An adaptive scope is query-based (for example, all users in the Legal department), updates automatically and has no per-policy item limits. A static scope is a fixed include or exclude list. The scope type can't be changed after a policy is created. Preservation Lock makes a policy impossible to weaken or delete — even for admins — for regulations such as SEC 17a-4, but it isn't supported with adaptive scopes.

Copilot and AI interactions now have their own retention locations, separate from Teams chats: Microsoft Copilot experiences (Microsoft Copilot, Security Copilot, Copilot in Fabric, Copilot Studio), Enterprise AI apps (such as Entra-registered AI apps and ChatGPT Enterprise) and Other AI apps (consumer AI apps such as ChatGPT and Google Gemini). Older combined "Teams chats and Copilot interactions" policies keep working but can't be edited. Third-party AI apps need a collection policy that captures content before retention can apply.

⚠️ Exam Trap: "Use a retention label to keep Copilot interactions for seven years" is wrong — Copilot and AI interactions support retention policies only. And if one policy keeps content for seven years while another deletes it after one, the content is kept for seven years.

Reflection Question: A document is covered by an org-wide policy that deletes after three years, and a user applies a label that retains for seven years and then deletes. What happens at year three, and at year seven? Name the principle behind each answer.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned