reviewSet: export

Namespace: microsoft.graph.ediscovery


APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.

Initiate an export from a reviewSet. For details, see Export documents from a review set in Advanced eDiscovery.

This API is supported in the following national cloud deployments.

Global service US Government L4 US Government L5 (DOD) China operated by 21Vianet


One of the following permissions is required to call this API. To learn more, including how to choose permissions, see Permissions.

Permission type Permissions (from least to most privileged)
Delegated (work or school account) eDiscovery.Read.All, eDiscovery.ReadWrite.All
Delegated (personal Microsoft account) Not supported.
Application Not supported.

HTTP request

POST /compliance/ediscovery/cases/{caseId}/reviewsets/{reviewsetId}/export

Request headers

Name Description
Authorization Bearer {token}. Required.
Content-Type application/json. Required.

Request body

In the request body, supply a JSON representation of the parameters.

The following table shows the parameters that can be used with this action.

Parameter Type Description
outputName String Name of the export. Required.
description String Description of the export
azureBlobContainer String When exporting to your own Azure storage account, this is the container URL.
azureBlobToken String When exporting to your own Azure storage account, SAS token for the container URL.
exportOptions microsoft.graph.ediscovery.exportOptions Specifies options that control the format of the export. Possible values are: originalFiles, text, pdfReplacement, fileInfo, tags.
exportStructure microsoft.graph.ediscovery.exportFileStructure Options that control file structure and packaging of the export. Possible values are: none, directory, pst.


If the export is started successfully, this action returns a 202 Accepted response code. The response will also contain a Location header, which contains the location of the caseExportOperation that was created to handle the export. Check the status of the export operation by making a GET request to the location, when successfully completed, the status will change to succeeded.



Content-Type: application/json

  "outputName": "2020-12-06 Contoso investigation export",
  "description": "Export for the Contoso investigation",
  "exportOptions": "originalFiles,fileInfo,tags",
  "exportStructure": "directory"


HTTP/1.1 202 Accepted
cache-control: no-cache,
client-request-id: 3ec98906-7187-927e-5203-2ed4533175c6,
request-id: 9e6b9230-113c-49de-8f7d-ecb90d35b0de