Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 22:54 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Purview: Data Lifecycle Management - Retention support Microsoft Teams call logs

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
559261

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, with source markup removed
Updated May 8, 2026: We have updated the content. Thank you for your patience.  Introduction We are introducing Microsoft Purview Data Lifecycle Management (DLM) retention support for Microsoft Teams call logs. Microsoft Teams stores call logs in several persistent locations, such as Call Detail Record (CDR) logs, which are currently retained indefinitely. However, regulatory requirements in various countries specify maximum retention periods for calling-related logs, creating a potential compliance gap. This update enables organizations to manage retention or deletion of Teams call logs to meet regulatory obligations, while still supporting evolving product features and business needs. This message is associated with Microsoft 365 Roadmap ID 559261. When this will happen: General Availability (Worldwide): Rollout will begin in late April 2026 and is expected to complete by late April 2026. How this affects your organization: Who is affected: Microsoft 365 compliance administrators Organizations using Microsoft Teams calling What will happen: Compliance admins can apply Microsoft Purview DLM retention and deletion policies to Teams call logs. Teams call logs stored with Teams compliance data in Exchange Online mailboxes are no longer retained indefinitely if new policies scoping teams call logs are setup. Existing Purview retention capabilities and workflows are respected. There is no direct impact to user calling experiences. What you can do to prepare: Review your regulatory and business requirements for retaining Teams call logs. Create or update Microsoft Purview retention policies to retain or delete Teams call logs as required once the feature is available. Update internal compliance documentation and guidance for your compliance and legal teams. Compliance considerations: Area Impact Retention policies, holds, or deletion workflows This change enables new retention and deletion controls for Microsoft Teams call logs using Microsoft Purview Data Lifecycle Management. How admins can monitor, report on, or demonstrate compliance activities Compliance admins gain additional control and visibility through Purview retention policies applied to Teams call logs. Processing or storage of existing customer data Existing Teams call logs stored in Exchange Online mailboxes can now be governed by configurable retention or deletion policies.

What changed

Between archive captures, newest first
    • Tags Feature update, Admin impact → Updated message, Feature update, Admin impact

    Updated May 8, 2026: We have updated the content. Thank you for your patience.  Introduction We are introducing Microsoft Purview Data Lifecycle Management (DLM) retention support … Teams compliance data in Exchange Online mailboxes are no longer retained indefinitely by default.if new policies scoping teams call logs are setup. Existing Purview retention capabilities and workflows are respected. There is no direct …

  1. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 22:54 UTC · 271 of 272 readable · 269 fully read · documentation 469/469 current