Summary
Details
Updated February 25, 2026: We are removing this message and will be providing an updated message shortly. You can safely disregard this message. We apologize for any confusion this may have caused.
----Disregard---
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
[How this will affect your organization:]
You are receiving this message because our reporting indicates your organization may be using eDiscovery tool.
Note: Administrators can identify usage by reviewing PowerShell audit logs or automation scripts that create or manage eDiscovery cases and searches.
eDiscovery users will no longer see cases or searches created, modified or deleted using cmdlets reflected in the eDiscovery UX when this change is implemented.
[What you need to do to prepare:]
When this change takes effect, no action is required if you manage cases and searches exclusively through the eDiscovery UX.
If your organization currently uses PowerShell cmdlets to create or manage eDiscovery cases or searches and expects them to appear in the UX, you will need to:
- Use Microsoft Graph APIs to create and manage eDiscovery cases and searches.
- Continue using PowerShell cmdlets for backend or automation scenarios without expecting visibility or synchronization in the UX.
Learn more about eDiscovery: Learn about eDiscovery solutions | Microsoft Learn
Learn more about Graph API for eDiscovery: Use Microsoft Purview APIs for eDiscovery | Microsoft Learn
Compliance considerations:
| Compliance area | Explanation |
|---|---|
| Does the change modify, interrupt, or disable any Purview capabilities (eDiscovery or Content Search)? | This change disables on‑demand synchronization between PowerShell‑managed eDiscovery cases and searches and the eDiscovery user experience (UX). While eDiscovery functionality remains available through PowerShell and Microsoft Graph APIs, cases and searches created, modified, or deleted via cmdlets will no longer appear or stay in sync within the eDiscovery UX. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Administrators who rely on the eDiscovery UX to review or manage cases and searches created through automation will no longer see those objects reflected in the UI. Monitoring, reporting, and compliance workflows may need to shift to Microsoft Graph APIs, PowerShell audit logs, or automation tooling to maintain visibility. |
Change History
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
[How this will affect your organization:]
You are receiving this message because our reporting indicates your organization may be using eDiscovery tool.
Note: Administrators can identify usage by reviewing PowerShell audit logs or automation scripts that create or manage eDiscovery cases and searches.
eDiscovery users will no longer see cases or searches created, modified or deleted using cmdlets reflected in the eDiscovery UX when this change is implemented.
[What you need to do to prepare:]
When this change takes effect, no action is required if you manage cases and searches exclusively through the eDiscovery UX.
If your organization currently uses PowerShell cmdlets to create or manage eDiscovery cases or searches and expects them to appear in the UX, you will need to:
- Use Microsoft Graph APIs to create and manage eDiscovery cases and searches.
- Continue using PowerShell cmdlets for backend or automation scenarios without expecting visibility or synchronization in the UX.
Learn more about eDiscovery: Learn about eDiscovery solutions | Microsoft Learn
Learn more about Graph API for eDiscovery: Use Microsoft Purview APIs for eDiscovery | Microsoft Learn
Compliance considerations:
| Compliance area | Explanation |
|---|---|
| Does the change modify, interrupt, or disable any Purview capabilities (eDiscovery or Content Search)? | This change disables on‑demand synchronization between PowerShell‑managed eDiscovery cases and searches and the eDiscovery user experience (UX). While eDiscovery functionality remains available through PowerShell and Microsoft Graph APIs, cases and searches created, modified, or deleted via cmdlets will no longer appear or stay in sync within the eDiscovery UX. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Administrators who rely on the eDiscovery UX to review or manage cases and searches created through automation will no longer see those objects reflected in the UI. Monitoring, reporting, and compliance workflows may need to shift to Microsoft Graph APIs, PowerShell audit logs, or automation tooling to maintain visibility. |
Updated February 25, 2026: We are removing this message and will be providing an updated message shortly. You can safely disregard this message. We apologize for any confusion this may have caused.
----Disregard---
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
[How this will affect your organization:]
You are receiving this message because our reporting indicates your organization may be using eDiscovery tool.
Note: Administrators can identify usage by reviewing PowerShell audit logs or automation scripts that create or manage eDiscovery cases and searches.
eDiscovery users will no longer see cases or searches created, modified or deleted using cmdlets reflected in the eDiscovery UX when this change is implemented.
[What you need to do to prepare:]
When this change takes effect, no action is required if you manage cases and searches exclusively through the eDiscovery UX.
If your organization currently uses PowerShell cmdlets to create or manage eDiscovery cases or searches and expects them to appear in the UX, you will need to:
- Use Microsoft Graph APIs to create and manage eDiscovery cases and searches.
- Continue using PowerShell cmdlets for backend or automation scenarios without expecting visibility or synchronization in the UX.
Learn more about eDiscovery: Learn about eDiscovery solutions | Microsoft Learn
Learn more about Graph API for eDiscovery: Use Microsoft Purview APIs for eDiscovery | Microsoft Learn
Compliance considerations:
| Compliance area | Explanation |
|---|---|
| Does the change modify, interrupt, or disable any Purview capabilities (eDiscovery or Content Search)? | This change disables on‑demand synchronization between PowerShell‑managed eDiscovery cases and searches and the eDiscovery user experience (UX). While eDiscovery functionality remains available through PowerShell and Microsoft Graph APIs, cases and searches created, modified, or deleted via cmdlets will no longer appear or stay in sync within the eDiscovery UX. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Administrators who rely on the eDiscovery UX to review or manage cases and searches created through automation will no longer see those objects reflected in the UI. Monitoring, reporting, and compliance workflows may need to shift to Microsoft Graph APIs, PowerShell audit logs, or automation tooling to maintain visibility. |
Never Miss a Microsoft 365 Update
Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.