Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 417/444 docs · checked 17:18 UTC Customize Public modeDiscuss ChangeIntel on Discord

(Updated) Microsoft Purview | Data Lifecycle Management - Power Automate integration with records management

Rollout

Ends
1 Mar 2027
Roadmap
558859
Platforms
Web

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 its sections, lists and tables; source markup removed

Updated July 14, 2026: We have updated the timeline. Thank you for your patience.

What and Why

Microsoft Purview Records Management will integrate with Power Automate to allow administrators to run custom workflows when retention-labeled items reach the end of their retention period. This enables automated post-retention handling using Power Automate across Microsoft 365 workloads.

This message is associated with Roadmap ID 558859.

Rollout Schedule

General Availability (GCC, GCCH, and DoD): Rollout begins in January 2027 (previously mid-July 2026) and is expected to complete by end of January 2027 (previously late September 2026).

Impact on Your Organization

Who is affected: Records Management and Compliance administrators

Platforms/Services

  • Microsoft Purview
  • Power Automate
  • SharePoint Online
  • OneDrive for Business
  • Exchange Online

What will happen

  • New actions are available in the Microsoft 365 Compliance connector:
  • Admins can select a pre‑existing Power Automate flow to run when a retention label expires.
  • Existing retention labels and retention settings are not changed.
  • The feature is not enabled by default; flows must be explicitly selected during retention label configuration.
  • There is no user impact unless administrators configure and apply flows.
  • Apply a retention label on the item
  • Relabel an item at the end of retention
  • Delete an item at the end of retention
  • Trigger a new instance of the flow if an item can’t be located

Action Required / Recommendations

No action is required. Review internal documentation and evaluate whether to use end-of-retention workflows.

Learn more: Customize what happens at the end of the retention period | Microsoft Learn

Compliance considerations

AreaExplanation
Alteration of how existing customer data is processedRetention‑labeled content can now trigger Power Automate workflows at the end of the retention period, extending how post‑retention actions are executed.
Retention policies, holds, or deletion workflowsRetention labels can invoke Power Automate flows at expiration in addition to built‑in disposition actions.
Admin monitoring and compliance demonstrationAdministrators may use Power Automate workflows to add logging, approvals, or notifications related to retention expiration.
Third‑party or cross‑service integrationMicrosoft Purview Records Management integrates with Power Automate through the Microsoft 365 Compliance connector.
Admin controlsConfiguration is admin‑controlled through retention label settings and selection of pre‑existing Power Automate flows.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

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

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.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
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 19 Oct 17:18 UTC · 258 of 260 readable · 256 fully read · documentation 417/444 current