eDiscovery review set export: export type

Gabrielle Lee 20 Reputation points
2026-08-05T15:20:43.99+00:00

I am using the Export API and see that I am missing the option to specify the options "Select items to include in your export" and "Export type". Is there any way to specify these in the API?

Microsoft Security | Microsoft Purview
0 comments
Answer accepted by question author
Peram Venkateswara Reddy 260 Reputation points Microsoft External Staff Moderator
2026-08-07T06:56:17.5266667+00:00

Hi @Gabrielle Lee , Hope you are doing well.

Hi Gabrielle,

Partly yes — two of those UI settings do have API equivalents, they're just not request-body parameters. Here's the mapping.

"Select items to include in your export"

UI option API equivalent
All documents in the review set POST /security/cases/ediscoveryCases/{caseId}/reviewSets/{reviewSetId}/export — this is the default scope of the call you're already making
-------- --------
All documents in the review set POST /security/cases/ediscoveryCases/{caseId}/reviewSets/{reviewSetId}/export — this is the default scope of the call you're already making
All filtered documents Create a review set query, then POST .../reviewSets/{reviewSetId}/queries/{queryId}/export
Selected documents only No equivalent — it depends on an interactive grid selection with no API analogue. Express the same subset as a review set query instead.

The scope isn't a parameter; it's determined by which endpoint you POST to. The ediscoveryExportOperation resource confirms this with its reviewSetQuery relationship: "The review set query that is used to filter the documents for export."

"Export item report only" vs "Export items with item report"

This one is controllable, via exportOptions. From the request body reference:

"The summary and load files are always included. If originalFiles isn't selected, only the tags member is considered."

So:

  • Report only → omit originalFiles, e.g. "exportOptions": "tags"
  • Items with report → include it, e.g. "exportOptions": "originalFiles,tags"

The summary and item report come along either way. The service tracks these as distinct operations internally too — caseAction includes both exportReport and exportResult.

"Export type" — browser download vs your own Azure Storage

Bring-your-own-storage was previously available as azureBlobContainer + azureBlobToken. In the current microsoft.graph.security beta API both are marked deprecated and have "stopped returning data," and they aren't in the v1.0 request body at all. They only still function in the legacy microsoft.graph.ediscovery beta namespace, which carries its own deprecation warning — so don't build on it.

The supported path now is Microsoft-managed storage plus a download URL:

  1. POST .../export → 202 Accepted with a Location header pointing at the export operation
  2. GET that location until status is succeeded
  3. Read exportFileMetadata, which gives you downloadUrl, fileName, and size

Two gotchas while you're building this

  • exportStructure: "directory" is deprecated — retained in v1.0 for backward compatibility only. Use pst or msg. Same for fileInfo in exportOptions, which has stopped returning data.
  • splitSource, includeFolderAndPath, friendlyName, and condensePaths are evolvable-enum members. Send Prefer: include-unknown-enum-members or the service won't return them to you.

One operational deadline: export processes are retained for the life of the case, but you must download the content within 30 days of the export completing. Worth building into your automation. Also note an export that runs more than seven days without completing is cancelled automatically — batch large review sets.

References

If you tell me which subset you're trying to reach, I can help shape the review set query.

Kind Regards,
Microsoft Support Team.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-08-05T15:20:59.7+00:00

    No. The Microsoft Graph eDiscovery review set export API only supports these request body parameters:

    • outputName
    • description
    • exportOptions
    • exportStructure

    The UI options Select items to include in your export and Export type are documented in the Purview portal export experience, but they are not exposed as parameters in the ediscoveryReviewSet: export API request body.

    Supported API behavior:

    • exportOptions controls export content format options such as originalFiles, text, pdfReplacement, tags, splitSource, includeFolderAndPath, friendlyName, and condensePaths.
    • exportStructure controls packaging/file structure options such as pst and msg.
    • outputName is required.
    • A successful request returns 202 Accepted and a Location header for the export operation.

    For item scope, the available API shown here is the review set export action and the review set query export action, but the documented request bodies still only expose the same four parameters. There is no documented API parameter here for:

    • selected documents only
    • all filtered documents
    • all documents in the review set
    • export item report only
    • export items with item report
    • direct browser download vs Azure Storage selection
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.