check before: 2025-09-26
Product:
eDiscovery, Exchange, Purview, Purview Communication Compliance, SharePoint
Platform:
Online, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message
Links:
Details:
Summary:
Starting September 26, 2025, eDiscovery cmdlets require Exchange Online PowerShell v3.9.0+ with the -EnableSearchOnlySession flag in Connect-IPPSSession. This change affects specific cmdlets but not the Purview portal and remains incompatible with Certificate-Based Authentication. Update scripts accordingly.
Details:
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).
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-08-09
updated:
2025-09-18
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
eDiscovery Cmdlet Functionality
Failure to execute eDiscovery cmdlets due to missing -EnableSearchOnlySession flag, leading to inability to perform compliance searches and case holds.
- roles: Compliance Officer, IT Administrator
- references: https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/connect-ippssession?view=exchange-ps, https://learn.microsoft.com/en-us/purview/edisc
" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/purview/edisc
Script and Workflow Disruption
Existing scripts and workflows will break if not updated to include the new parameter, causing delays in compliance processes.
- roles: Compliance Officer, IT Administrator
- references: https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-compliancesearchaction?view=exchange-ps, https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-caseholdpolicy?view=exchange-ps
User Experience Degradation
Users relying on eDiscovery features may experience delays or inability to access necessary compliance tools, impacting their workflow.
- roles: Compliance Officer, Legal Team Member
- references: https://learn.microsoft.com/en-us/purview/edisc, https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/get-compliancesecurityfilter?view=exchange-ps
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
Script Optimization for eDiscovery
With the requirement to update scripts to include the -EnableSearchOnlySession parameter, there is an opportunity to optimize and streamline eDiscovery scripts. This can lead to improved performance and reduced execution time for compliance searches.
- next-steps: Conduct a review of existing eDiscovery scripts to identify those that need updating. Refactor scripts to ensure they are efficient and incorporate the new parameter. Test the updated scripts in a controlled environment before full deployment.
- roles: Compliance Officer, IT Administrator, Legal Team
- references: https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/connect-ippssession?view=exchange-ps, https://learn.microsoft.com/en-us/purview/edisc
Training and Knowledge Sharing
As the connectivity change affects how cmdlets are executed, there is an opportunity to enhance training for IT staff and compliance officers. Providing updated training materials will ensure that all relevant personnel are aware of the changes and how to implement them effectively.
- next-steps: Develop training sessions and materials that cover the new cmdlet requirements and the importance of the -EnableSearchOnlySession parameter. Schedule training sessions and create a knowledge base article for ongoing reference.
- roles: IT Trainer, Compliance Officer, IT Administrator
- references: https://learn.microsoft.com/en-us/purview/edisc
Monitoring and Reporting Enhancements
The change provides an opportunity to implement better monitoring and reporting tools for eDiscovery cmdlets. By tracking the usage of cmdlets and their performance post-update, organizations can identify any issues early and optimize their compliance processes.
- next-steps: Evaluate existing monitoring tools and determine if they can be enhanced to track the new cmdlet usage. Consider implementing dashboards for real-time reporting on eDiscovery activities and performance metrics.
- roles: IT Administrator, Compliance Officer, Data Analyst
- references: https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/get-compliancesecurityfilter?view=exchange-ps
Potentional Risks**
XXXXXXX ... paid membership only
Data Protection**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
Hypothetical Work Council Statement**
XXXXXXX ... paid membership only
DPIA Draft**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2025-09-18 | MC Messages | Updated September 16, 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 19, 2025 (previously August 31). | 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). |
| 2025-09-18 | MC Last Updated | 09/16/2025 16:56:14 | 2025-09-17T22:35:42Z |
| 2025-09-18 | MC Summary | Starting September 19, 2025, running certain Microsoft Purview eDiscovery cmdlets requires Exchange Online PowerShell v3.9.0+ with the -EnableSearchOnlySession parameter in Connect-IPPSSession. This change does not affect the Purview portal and remains incompatible with Certificate-Based Authentication. Update scripts accordingly. | Starting September 26, 2025, eDiscovery cmdlets require Exchange Online PowerShell v3.9.0+ with the -EnableSearchOnlySession flag in Connect-IPPSSession. This change affects specific cmdlets but not the Purview portal and remains incompatible with Certificate-Based Authentication. Update scripts accordingly. |
| 2025-09-17 | MC Messages | 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). | Updated September 16, 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 19, 2025 (previously August 31). |
| 2025-09-17 | MC Last Updated | 09/04/2025 21:28:15 | 2025-09-16T16:56:14Z |
| 2025-09-17 | MC Summary | Starting September 12, 2025, running certain Microsoft Purview eDiscovery cmdlets requires Exchange Online PowerShell v3.9.0+ with the -EnableSearchOnlySession parameter in Connect-IPPSSession. This change does not affect the Purview portal and remains incompatible with Certificate-Based Authentication. Update scripts accordingly. | Starting September 19, 2025, running certain Microsoft Purview eDiscovery cmdlets requires Exchange Online PowerShell v3.9.0+ with the -EnableSearchOnlySession parameter in Connect-IPPSSession. This change does not affect the Purview portal and remains incompatible with Certificate-Based Authentication. Update scripts accordingly. |
| 2025-09-05 | MC Messages | 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. | 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). |
| 2025-09-05 | MC Last Updated | 08/15/2025 15:44:49 | 2025-09-04T21:28:15Z |
| 2025-09-05 | MC Summary | Starting August 31, 2025, running certain Microsoft Purview eDiscovery cmdlets requires Exchange Online PowerShell v3.9.0+ and the -EnableSearchOnlySession flag with Connect-IPPSSession. This change does not affect portal users and remains incompatible with Certificate-Based Authentication. Update scripts accordingly. | Starting September 12, 2025, running certain Microsoft Purview eDiscovery cmdlets requires Exchange Online PowerShell v3.9.0+ with the -EnableSearchOnlySession parameter in Connect-IPPSSession. This change does not affect the Purview portal and remains incompatible with Certificate-Based Authentication. Update scripts accordingly. |
| 2025-08-16 | MC prepare | https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/connect-ippssession?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/get-compliancesecurityfilter?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-caseholdpolicy?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-caseholdrule?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-compliancesearchaction?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-compliancesecurityfilter?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/remove-caseholdpolicy?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/remove-caseholdrule?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/remove-compliancesecurityfilter?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-caseholdpolicy?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-caseholdrule?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-compliancesecurityfilter?view=exchange-ps https://learn.microsoft.com/en-us/purview/edisc https://www.microsoft.com/en-us/trust-center/security/secure-future-initiative https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.8.0 | https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/connect-ippssession?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/get-compliancesecurityfilter?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-caseholdpolicy?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-caseholdrule?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-compliancesearchaction?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-compliancesecurityfilter?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/remove-caseholdpolicy?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/remove-caseholdrule?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/remove-compliancesecurityfilter?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-caseholdpolicy?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-caseholdrule?view=exchange-ps https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-compliancesecurityfilter?view=exchange-ps https://learn.microsoft.com/en-us/purview/edisc https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.8.0 |
| 2025-08-16 | MC MessageTagNames | Feature update, Admin impact | Updated message, Feature update, Admin impact |
| 2025-08-16 | MC Summary | Starting August 31, 2025, Microsoft Purview requires Exchange Online PowerShell v3.9.0+ and the -EnableSearchOnlySession parameter for specific eDiscovery cmdlets to enhance security. This change doesn't affect the Purview portal and remains incompatible with Certificate-Based Authentication. Update scripts accordingly. | Starting August 31, 2025, running certain Microsoft Purview eDiscovery cmdlets requires Exchange Online PowerShell v3.9.0+ and the -EnableSearchOnlySession flag with Connect-IPPSSession. This change does not affect portal users and remains incompatible with Certificate-Based Authentication. Update scripts accordingly. |
| 2025-08-16 | MC Last Updated | 08/09/2025 01:38:15 | 2025-08-15T15:44:49Z |
| 2025-08-16 | MC Messages | Introduction
As part of Microsoft's ongoing Secure Future Initiative (SFI) (SFI), Microsoft Purview is enhancing protections for cmdlets that connect to other Microsoft 365 services such as SharePoint and Exchange. Starting August 31, 2025, a new connection parameter will be required when using Security & Compliance PowerShell to run specific eDiscovery-related cmdlets. When this will happen This change will take effect on August 31, 2025. | 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. |
| 2025-08-16 | MC Title | Microsoft Purview | eDiscovery cmdlet connectivity change | (Updated) Microsoft Purview | eDiscovery cmdlet connectivity change |
| 2025-08-16 | MC How Affect | 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. | 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. |
Last updated 3 days ago ago
