Updated September 4, 2025: We have updated the timeline. 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 September 12, 2025 (previously August 31).
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.
Source: Microsoft
<<< [MC1131771] Archive
Tooltip: View earlier revisions of this post
![(Updated) Microsoft Purview | eDiscovery cmdlet connectivity change [MC1131771] 1 (Updated) Microsoft Purview | eDiscovery cmdlet connectivity change [MC1131771]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-cottonbro-6153354-1024x683.webp)

![Microsoft Teams: Join by code requires owner approval for private teams [MC1183610] 3 pexels pixabay 461169](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-461169-150x150.webp)
![Rate my call feedback experience update in Microsoft Teams [MC1183608] 4 pexels rostislav 5011647](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-rostislav-5011647-150x150.webp)
![Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF) [MC1183611] 5 pexels ben neale 123878 380337](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-ben-neale-123878-380337-150x150.webp)
![Microsoft Purview: Sender email address update for Microsoft Teams Data Loss Prevention Generate Incident Report emails [MC1064354] 7 Microsoft Purview: Sender email address update for Microsoft Teams Data Loss Prevention Generate Incident Report emails [MC1064354]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-leah-newhouse-50725-325521-150x150.webp)