An API that connects multiple Microsoft services, enabling data access and automation across platforms
We have already identified the issue and fix is getting deployed
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I previously had setup a demonstration for my organization using the 'getdownloadurl' on export operations as documented here: https://learn.microsoft.com/en-us/graph/api/ediscovery-caseexportoperation-getdownloadurl?view=graph-rest-beta&tabs=http#examples This previously worked without issue, however after a few weeks I revisited this and now this endpoint is throwing the following error: { "error": { "code": "InternalServerError", "message": "An unexpected error occurred.", "innerError": { "date": "2022-02-09T18:12:06", "request-id": "7aee13bf-b6ed-442d-a4c2-873df9a54df3", "client-request-id": "7aee13bf-b6ed-442d-a4c2-873df9a54df3" } } } my curl example is: curl --location --request GET 'https://graph.microsoft.com/beta/compliance/ediscovery/cases/c3c587e0-314e-4704-9bcb-254fa227e6b4/operations/0cb2165ee85748839a1dbf10c21f0d61/microsoft.graph.ediscovery.caseExportOperation/getDownloadUrl' \ --header 'Authorization: Bearer omitted' \ --header 'Content-Type: application/json' Where am I in error here?
An API that connects multiple Microsoft services, enabling data access and automation across platforms
We have already identified the issue and fix is getting deployed
Hi @Baker, Darin C ,
Please note this API is under the /beta version in Microsoft Graph are subject to change.
Use of these APIs in production applications is not supported.
Also, error "InternalServerError" suggests returned by server, the response status code should be 500.
Refer to this graph errors status codes documentation for more inputs.
Hope this helps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".