ChangeIntelIT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 270/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 09:12 UTC Customize Public modeDiscuss ChangeIntel on Discord
MC1131771 Plan for changeUpdated messageFeature updateAdmin impact

Microsoft Purview | eDiscovery cmdlet connectivity change

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.
Microsoft Purview
Microsoft 365 admin center

Rollout

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, safely structured
Updated September 17, 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 26, 2025 (previously September 19). 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 -EnableSearchOnlySession parameter 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.

What changed

Between archive captures, newest first

  1. Updated September 16,17, 2025: We have updated the timeline. Thank you for your patience. Introduction … cmdlets.   When this will happen This change will take effect on September 19,26, 2025 (previously August 31).September 19). How this affects your organization To maintain functionality and align with modern …

  2. Updated September 4,16, 2025: We have updated the timeline. Thank you for your patience. Introduction … cmdlets.   When this will happen This change will take effect on September 12,19, 2025 (previously August 31). How this affects your organization To maintain functionality …

  3. Updated August 15,September 4, 2025: We have updated content.the timeline. Thank you for your patience. Introduction Connectivity changes between cmdlets and other … eDiscovery cmdlets.   When this will happen This change will take effect on September 12, 2025 (previously August 31, 2025.31). How this affects your organization To maintain functionality and align with modern …

    • Tags Feature update, Admin impact → Updated message, Feature update, Admin impact

    Introduction As part of Microsoft’s ongoing Secure Future Initiative (SFI) (SFI), Microsoft Purview is enhancing protections forUpdated August 15, 2025: We have updated content. Thank you for your patience. Introduction Connectivity changes between cmdlets that connect to other Microsoft 365 services such as SharePoint and Exchange.and other M365 services like SharePoint and Exchange will need a new flag to be specified. Starting August 31, 2025, a new connection parameter will be required when using Security & Compliance PowerShellcustomers will need to use at least Exchange Online PowerShell v3.9.0 and later, with - EnableSearchOnlySession parameter when running Connect-IPPSSession to run specific eDiscovery-relatedthe following eDiscovery cmdlets.    When this will happen This change will take effect on August 31, … customers must use Exchange Online PowerShell v3.9.0 and later and include the -EnableSearchOnlySessionEnableSearchOnlySession parameter when running Connect-IPPSSession to execute the following cmdlets: New-ComplianceSearchAction New-CaseHoldPolicy, Set-CaseHoldPolicy, …

  5. · first version seen

Learn more

Links from the notice and their documentation checks

Both explicitly reference the same documentation; this does not confirm the same change, rollout or applicability

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.
  • 12 linked pages have not been read yet.
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 27 Oct 09:12 UTC · 270 of 272 readable · 269 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.