Case creation and Case listing gives "An unexpected error occurred."

Question

Case creation and Case listing gives "An unexpected error occurred."

Shubham Jethava 0

Microsoft.Graph.Beta.Models.ODataErrors.ODataError
  HResult=0x80131500
  Message=An unexpected error occurred.
  Source=Microsoft.Kiota.Http.HttpClientLibrary
  StackTrace:
   at Microsoft.Kiota.Http.HttpClientLibrary.HttpClientRequestAdapter.<ThrowIfFailedResponseAsync>d__28.MoveNext()
   at Microsoft.Kiota.Http.HttpClientLibrary.HttpClientRequestAdapter.<SendAsync>d__20`1.MoveNext()
   at Microsoft.Kiota.Http.HttpClientLibrary.HttpClientRequestAdapter.<SendAsync>d__20`1.MoveNext()
   at Microsoft.Graph.Beta.Security.Cases.EdiscoveryCases.EdiscoveryCasesRequestBuilder.<PostAsync>d__7.MoveNext()
   at EdiscoveryAPI.GraphAPI.src.Services.edcaseoperation.EdCaseOperation.<CreateCase>d__6.MoveNext() in D:\Git\Analytics_UtilityProjects\EdiscoveryAPI\EdiscoveryAPI\GraphAPI\src\services\edcaseoperation\EdCaseOperation.cs:line 115
  This exception was originally thrown at this call stack:

Microsoft.Kiota.Http.HttpClientLibrary.HttpClientRequestAdapter.ThrowIfFailedResponseAsync(System.Net.Http.HttpResponseMessage, System.Collections.Generic.Dictionary<string, Microsoft.Kiota.Abstractions.Serialization.ParsableFactory<Microsoft.Kiota.Abstractions.Serialization.IParsable>>, System.Diagnostics.Activity, System.Threading.CancellationToken)

Microsoft.Kiota.Http.HttpClientLibrary.HttpClientRequestAdapter.SendAsync<ModelType>(Microsoft.Kiota.Abstractions.RequestInformation, Microsoft.Kiota.Abstractions.Serialization.ParsableFactory<ModelType>, System.Collections.Generic.Dictionary<string, Microsoft.Kiota.Abstractions.Serialization.ParsableFactory<Microsoft.Kiota.Abstractions.Serialization.IParsable>>, System.Threading.CancellationToken)

Microsoft.Kiota.Http.HttpClientLibrary.HttpClientRequestAdapter.SendAsync<ModelType>(Microsoft.Kiota.Abstractions.RequestInformation, Microsoft.Kiota.Abstractions.Serialization.ParsableFactory<ModelType>, System.Collections.Generic.Dictionary<string, Microsoft.Kiota.Abstractions.Serialization.ParsableFactory<Microsoft.Kiota.Abstractions.Serialization.IParsable>>, System.Threading.CancellationToken)

Microsoft.Graph.Beta.Security.Cases.EdiscoveryCases.EdiscoveryCasesRequestBuilder.PostAsync(Microsoft.Graph.Beta.Models.Security.EdiscoveryCase, System.Action<Microsoft.Kiota.Abstractions.RequestConfiguration<Microsoft.Kiota.Abstractions.DefaultQueryParameters>>, System.Threading.CancellationToken)

EdiscoveryAPI.GraphAPI.src.Services.edcaseoperation.EdCaseOperation.CreateCase(EdiscoveryAPI.GraphAPI.src.GraphAPI.Entity.edcase.EdCase) in EdCaseOperation.cs

Above exception is thrown by GraphAPI when calling function in the image.

User's image

Below permissions are given. User's image

SrideviM 2,290 Reputation points Microsoft External Staff

2025-04-22T09:18:33.99+00:00

Hello Shubham Jethava,

Could you let me know what type of authentication flow you're using? Are you using delegated authentication where user interaction is involved, or app-only authentication with client credentials? This will help us understand how permissions are being applied and guide you accordingly.
Shubham Jethava 0 Reputation points

2025-04-24T05:21:38.08+00:00
Hello @SrideviM

There are both methods implemented and I have tried both the ways, issue persist in both the cases.
For the reference,

delegated authentication includes parameters like,Using UsernamePasswordCredential class

Scope: {"User.Read"}

Tenant ID:

Client ID:

User name:

Password:

application authentication includes parameter like,

Using ClientSecretCredential class

Scope: {"https://graph.microsoft.com/.default"}

ClientID:

Tenant ID:

Client secret:

Using ~~DeviceCodeCredential~~ class

Scope: {"User.Read"}

Tenant ID:

Client ID:

1 answer

Your answer

SrideviM 2,290 Reputation points Microsoft External Staff

2025-04-22T09:18:33.99+00:00

Hello Shubham Jethava,

Could you let me know what type of authentication flow you're using? Are you using delegated authentication where user interaction is involved, or app-only authentication with client credentials? This will help us understand how permissions are being applied and guide you accordingly.
Shubham Jethava 0 Reputation points

2025-04-24T05:21:38.08+00:00

Hello @SrideviM

There are both methods implemented and I have tried both the ways, issue persist in both the cases.
For the reference,

delegated authentication includes parameters like,Using UsernamePasswordCredential class

Scope: {"User.Read"}

Tenant ID:

Client ID:

User name:

Password:

application authentication includes parameter like,

Using ClientSecretCredential class

Scope: {"https://graph.microsoft.com/.default"}

ClientID:

Tenant ID:

Client secret:

Using ~~DeviceCodeCredential~~ class

Scope: {"User.Read"}

Tenant ID:

Client ID:

Answer 1

Hello Shubham Jethava,

I understand this issue can be frustrating. I’ve tested the same scenario using both delegated and app-only authentication, and I encountered the exact same behavior.

HTTP requests made through Postman are resulting in timeouts, while SDK calls return an unknown error.

Here is the timeout message from Postman:

Timeout Error

And the error returned by the SDK:

Unknown Error

Based on this and similar reports from other users, it appears to be a known issue with the Graph API for eDiscovery. You can find a related discussion here: Graph eDiscovery API or compliance (Beta) API broken

As a workaround, Security & Compliance PowerShell is currently working well and can be used to manage eDiscovery cases. To begin, you can follow the official documentation here:

Connect-IPPSSession - PowerShell | Microsoft Learn

After connecting, you can create a case using the following command:

Connect-IPPSSession

New-ComplianceCase -Name "Sample Case" -CaseType AdvancedEdiscovery -Description "Created via PowerShell" -ExternalId "REF-12345"

Response:

Case Creation

To list all available eDiscovery (Premium) cases, you can run this command:


Get-ComplianceCase -CaseType AdvancedEdiscovery

Response:

Case List

Hope this helps!

If this answer was helpful, please click "Accept the answer" and mark Yes, as this can help other community members.

User's image

If you have any other questions or are still facing issues, feel free to post in the comments and I’ll be happy to assist further.

Share via

Case creation and Case listing gives "An unexpected error occurred."

1 answer

Your answer