check before: 2026-03-23
Product:
eDiscovery, Microsoft Graph, Purview, Purview Communication Compliance
Platform:
Developer, Online, World tenant
Status:
Change type:
Admin impact, Retirement
Links:
Details:
Summary:
Starting March 23, 2026, on-demand synchronization for eDiscovery cases and searches created or managed via PowerShell cmdlets will be disabled, causing them not to appear or sync in the eDiscovery UX. Organizations must use Microsoft Graph APIs for UX visibility or continue cmdlet use without synchronization.
Details:
Starting March 23, 2026, we're disabling on‑demand synchronization for eDiscovery cases and searches created, modified, or deleted using PowerShell cmdlets. As a result, cases and searches created through cmdlets will no longer automatically appear or stay in sync with the eDiscovery UX.
[When this will happen:]
March 23, 2026
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2026-02-25
updated:
2026-02-25
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**
Starting March 23, 2026, eDiscovery cases and searches created or managed using PowerShell cmdlets will no longer automatically synchronize with the eDiscovery UI, requiring organizations to use Microsoft Graph APIs for visibility, while cmdlets can still be used for backend tasks without UI visibility.
Direct effects for Operations**
Loss of Synchronization
eDiscovery cases and searches created via PowerShell cmdlets will not appear or sync in the eDiscovery UX, leading to potential confusion and inefficiencies in case management.
- roles: eDiscovery Administrators, Compliance Officers
- references: https://learn.microsoft.com/en-us/purview/edisc?view=o365-worldwide
Increased Complexity in Management
Administrators will need to shift to using Microsoft Graph APIs for managing eDiscovery cases, increasing the complexity of workflows and requiring additional training.
- roles: eDiscovery Administrators, IT Support Staff
- references: https://learn.microsoft.com/en-us/purview/edisc-ref-api-guide
Monitoring and Reporting Challenges
The inability to see cmdlet-created cases in the UX will hinder monitoring and reporting capabilities, necessitating a reliance on PowerShell audit logs and Graph APIs.
- roles: Compliance Officers, IT Auditors
- references: https://techcommunity.microsoft.com/blog/microsoft-security-blog/general-availability-of-microsoft-purview-ediscovery-graph-api-for-e3-customers/4489678
User Experience Degradation
Users relying on the eDiscovery UX for visibility will experience a degradation in user experience as they will not see all relevant cases and searches.
- roles: End Users, Legal Teams
- references: https://learn.microsoft.com/en-us/purview/edisc?view=o365-worldwide
Training and Adaptation Needs
Organizations will need to invest in training for staff to adapt to the new requirements of using Microsoft Graph APIs, which may lead to temporary productivity loss.
- roles: eDiscovery Administrators, Training Coordinators
- references: https://learn.microsoft.com/en-us/purview/edisc-ref-api-guide
Configutation Options**
XXXXXXX ... paid membership only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
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.
