Microsoft Purview DLM: Retirement of SharePoint online information management and in-place records management features [MC1211579]

Message ID: MC1211579 (Updated)

Updated January 7, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re retiring several legacy SharePoint Online features to streamline compliance and data lifecycle management. Starting April 2026, the following features will be retired:

• Information Management Policies
• In-Place Records Management
• Document deletion policies (deletion only)

We recommend using Microsoft Purview Data Lifecycle Management and Purview Records Management, where we continue to invest in modern, flexible compliance solutions.

For details on the retirement plan and migration guidance, refer to: Use Microsoft Purview risk and compliance solutions instead of older SharePoint features.

[When this will happen:]

Retirement will take place in April 2026

[How this affects your organization:]

Who is affected: Organizations using Information Management Policies, In-Place Records Management, or related deletion policies in SharePoint Online.

What will happen:

• These features will no longer be supported by Microsoft.
• These features may disappear from the user interface (UI).
• Configurations will not be available through UI or programmatically (including enable/disable actions).
• Backend services supporting these behaviors may stop functioning.

[What you can do to prepare:]

Microsoft won’t automatically migrate your older information management and SharePoint records management features in SharePoint Online. If you choose not to migrate to supported features, the older features may no longer be supported.

Between now and April 2026, you have the flexibility to migrate your scenarios on your own schedule. To prepare:

• Review current use of legacy features and confirm compliance goals.
• Plan migration to Microsoft Purview Data Lifecycle Management and Purview Records Management.
• Audit retention schedules for duplicates or outdated policies.
• Confirm applicable licenses for Purview features.
• Implement modern features and verify functionality using tools like Policy Lookup.
• Communicate this change to your Data Lifecycle and Records Management teams.

For detailed migration strategies and feature mapping, refer to: Migration strategies for moving to Microsoft Purview solutions.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft

<<< [MC1211579] Archive
Tooltip: View earlier revisions of this post

Latest Posts