Fix Microsoft Graph eDiscovery Estimate Statistics 404 Error
Question details
The user needs to resolve a 404 object-not-found error encountered while attempting to retrieve eDiscovery case search estimate statistics via Microsoft Graph.
- Product
- Microsoft Graph
- Device & OS
- not provided
- Scenario
- Running a PowerShell command to get the last estimate statistics operation for an existing eDiscovery case search.
- Observed behavior
- The command Get-MgSecurityCaseEdiscoveryCaseSearchLastEstimateStatisticsOperation returns a 404 error, even though the target collection exists and can be listed normally.
Verify that your account has the correct eDiscovery Administrator roles assigned and that the Microsoft Graph PowerShell SDK is updated to the latest version.
Escalate to Microsoft Support via Microsoft Q&A
Because this is a specialized Microsoft Graph issue likely involving a service-side bug or endpoint change, escalating to Microsoft Support engineers is recommended.
A 404 error on a known existing eDiscovery collection typically points to a backend synchronization issue or a temporary API routing failure within the Microsoft Graph infrastructure rather than a user syntax error.
Collect the complete PowerShell command you executed, the exact error response (including the request ID and timestamp), and your tenant details.
Go to the official Microsoft Q&A website (learn.microsoft.com/en-us/answers) and navigate to the Microsoft Graph section.
Post a new question tagging 'ms-graph'. Include all gathered tenant details, permissions, the complete command, and the exact date the problem began to allow Microsoft engineers to investigate the service-side logs.
Switch to WPS Office for a Lightweight Document Workflow
While enterprise compliance and eDiscovery rely on tools like Microsoft Graph, for your daily document creation and team collaboration needs, WPS Office offers a free, lightweight, and highly compatible alternative. Enjoy a seamless transition without heavy administrative overhead.

Frequently Asked Questions
Why does the base eDiscovery search command work but the estimate statistics command fails?
This can happen due to a service-side data synchronization delay or an API routing issue within Microsoft Graph where the statistics endpoint fails to locate the referenced search object immediately after creation.
What permissions are required to run eDiscovery estimate statistics?
Executing eDiscovery operations in Microsoft Graph requires specific permissions, such as the eDiscoveryManager or eDiscoveryAdministrator roles, along with appropriate consented API scopes like eDiscovery.ReadWrite.All.
How can I view the raw error code returned by Microsoft Graph PowerShell?
You can append the '-Debug' parameter to your PowerShell command to view the raw HTTP request and response headers. This exposes the detailed HTTP status code, Request ID, and inner error messages.




