Updated August 15, 2025: We have updated content. Thank you for your patience.
Introduction
Connectivity changes between cmdlets and other M365 services like SharePoint and Exchange will need a new flag to be specified. Starting August 31, 2025, customers will need to use at least Exchange Online PowerShell v3.9.0 and later, with - EnableSearchOnlySession parameter when running Connect-IPPSSession to run the following eDiscovery cmdlets.
When this will happen
This change will take effect on August 31, 2025.
How this affects your organization
To maintain functionality and align with modern authentication standards, customers must use Exchange Online PowerShell v3.9.0 and later and include the EnableSearchOnlySession parameter when running Connect-IPPSSession to execute the following cmdlets:
- New-ComplianceSearchAction
- New-CaseHoldPolicy, Set-CaseHoldPolicy, Remove-CaseHoldPolicy
- New-CaseHoldRule, Set-CaseHoldRule, Remove-CaseHoldRule
- New-ComplianceSecurityFilter, Set-ComplianceSecurityFilter, Get-ComplianceSecurityFilter, Remove-ComplianceSecurityFilter
This change does not impact users accessing eDiscovery through the Purview portal. These cmdlets also remain incompatible with Certificate-Based Authentication (CBA).
You are receiving this message because one or more users in your organization are actively using these eDiscovery features.
What you can do to prepare
- Update scripts and workflows to include the
-EnableSearchOnlySessionparameter when connecting to Security & Compliance PowerShell. - Ensure your organization is using Exchange Online PowerShell version 3.9.0 or later.
- For more information, visit: Learn about eDiscovery solutions in Microsoft Purview
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.