-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Case Requests failing as Forbidden #1987
Comments
I am also getting this error message when trying to retrieve a case by id. The same case is retrievable at the |
Thanks for raising this @henry-filosa As this is an API/service related question, any chance you could post the same at the link below for the API owners to help out with this? |
@andrueastman I posted the question here: Is there any way to escalate this as it is an error on the MS Graph side and not with the individual requests. |
@mslosarek Just to confirm, are you still experiencing this? Are you able to share a fresh error response if this is the case? |
It is now working again on our end. Mysterious. |
Govt cloud still erroring in the exact same way seems like for us it STARTED this am. |
Describe the bug
Get requests to fetch an ediscovery case are failing spuriously w/
Forbidden: Request for case type is not supported
. This is a V1.0 endpoint and should be supported.We have taken the following troubleshooting steps that make us fairly certain that it is an issue w/ the graph itself:
Additionally, this error started suddenly today w/ no changes to our code or infrastructure.
To Reproduce
Java: make a request w/
client.security().cases().ediscoveryCases(caseId).buildRequest().get()
Postman:
https://graph.microsoft.com/v1.0/security/cases/ediscoveryCases/CASE_ID
The app registration used for OAuth must have
eDiscovery.Read.All
oreDiscovery.ReadWrite.All
permissions and be granted admin consent.Expected behavior
Return the specified case.
Screenshots
Here is an example return value we have received:
Desktop (please complete the following information):
Additional context
This doesn't seem to be an issue w/ the SDK, but there was no other location we could find to file an issue. Additionally, none of the following health dashboards we could find indicated an applicable issue:
The text was updated successfully, but these errors were encountered: