Microsoft Purview | Data lifecycle Management cmdlet connectivity change
Starting January 31, 2026, admins must use Exchange Online PowerShell v3.9.0+ and include the -EnableSearchOnlySession parameter with Connect-IPPSession to run Data Lifecycle Management cmdlets. This change enhances security and affects specific retention compliance cmdlets, with no impact on Purview portal users. Introduction Connectivity changes between cmdlets and Microsoft 365 services like SharePoint and Exchange now require a new parameter for improved security and modern authentication. Starting Jan 31, 2026, Admins must use Exchange Online PowerShell v3.9.0 or later and include the -EnableSearchOnlySession parameter when running Connect-IPPSession to execute Data Lifecycle Management cmdlets. When this will happen: Enforcement begins January 31, 2026. How this affects your organization: Who is affected: Admins using Data Lifecycle Management cmdlets in Security & Compliance PowerShell. What will happen: You must use Exchange Online PowerShell v3.9.0 or later. You must include the -EnableSearchOnlySession parameter when running Connect-IPPSession. This applies to the following cmdlets: New-RetentionCompliancePolicy Set-RetentionCompliancePolicy New-RetentionComplianceRule Set-RetentionComplianceRule No impact for users accessing Data Lifecycle Management through the Purview portal. Cmdlets remain incompatible with Certificate-Based Authentication (CBA). What you can do to prepare: Compliance considerations: No compliance considerations identified, review as appropriate for your organization. Update scripts and workflows to include the -EnableSearchOnlySession parameter. Ensure your organization is using Exchange Online PowerShell version 3.9.0 or later. For more information, visit: Learn about Data Lifecycle Management solutions in Microsoft Purview. Message ID: MC1213770
The post Microsoft Purview | Data lifecycle Management cmdlet connectivity change appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Microsoft Purview | Data lifecycle Management cmdlet connectivity change
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
External messaging limits for onmicrosoft.com-only organizations in Microsoft Teams
Microsoft Teams will impose outbound external messaging limits starting mid-September 2026 for organizations using only the default onmicrosof...
Microsoft Teams: Enable agents for existing applications in your organization
For third-party applications already being used in your organization, admins can now discover and enable the corresponding Teams agents from w...
Microsoft Viva: Campaigns Hub in Engage and Engage in Teams mobile
The Campaigns Hub in Viva Engage provides a centralized mobile destination where employees can discover and participate in organizational camp...
Planner: Conditional Coloring
Conditional Coloring highlight tasks based on selected criteria, making priorities, status, and important task details easier to spot. Product...
Outlook: Offline settings “Days of email to save” admin policy
Tenant admins will be able to define the default value for “Days of email to save” in Offline settings and designate whether end u...
Microsoft Copilot Studio: Agent Sharing amongst makers
Enables sharing of agents with other makers in the new GHCP harness. Makers can grant other makers Agent Viewer (view analytics/evaluations on...
OneDrive Photos on Windows: admin controls and policy support
OneDrive Photos, integrated into the OneDrive sync app for Windows 10/11, is currently available only for personal Microsoft accounts, with wo...
Admin app retiring in Teams, Outlook and Microsoft365.com
The Admin app for very small businesses in Teams, Outlook, and Microsoft365.com will retire by October 2026, with rollout starting August 2026...
Calls popout into a new window on the browser to support multi-tasking and collaboration during a meeting
Microsoft Teams for Web will introduce a Picture-in-Picture Call Monitor in October 2026, allowing users to manage meeting controls in a separ...
Microsoft Windows Autopatch: September 2026 Windows security update requires a restart for hotpatch-enabled devices
The September 2026 Windows security update requires a restart for hotpatch-enabled devices because it is a standard update. Devices will remai...