Skip to content

ediscovery-reviewset-export.md

Latest commit

 

History

History
135 lines (98 loc) · 5.49 KB

ediscovery-reviewset-export.md

File metadata and controls

135 lines (98 loc) · 5.49 KB
title reviewSet: export
description Initiate an export from a reviewSet.
author mahage-msft
ms.localizationpriority medium
ms.subservice ediscovery
doc_type apiPageType
ms.date 06/10/2024

reviewSet: export

Namespace: microsoft.graph.ediscovery

[!INCLUDE beta-disclaimer]

[!INCLUDE ediscovery-deprecation]

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

[!INCLUDE national-cloud-support]

Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.

[!INCLUDE permissions-table]

HTTP request

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

Request headers

Name Description
Authorization Bearer {token}. Required. Learn more about authentication and authorization.
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. The possible values are: originalFiles, text, pdfReplacement, fileInfo, tags.
exportStructure microsoft.graph.ediscovery.exportFileStructure Options that control file structure and packaging of the export. The possible values are: none, directory, pst.

Response

If the export is started successfully, this action returns a 202 Accepted response code. The response contains 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 changes to succeeded.

Examples

Request

HTTP

POST https://graph.microsoft.com/beta/compliance/ediscovery/cases/99e865fc-e29f-479a-ba83-9e58eb017103/reviewsets/e44ac2cb-f8b4-4fd8-aa1c-1391b46ba9cc/export
Content-Type: application/json

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

C#

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

Go

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

Java

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

JavaScript

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

PHP

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

PowerShell

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

Python

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

Response

HTTP/1.1 202 Accepted
cache-control: no-cache,
client-request-id: 3ec98906-7187-927e-5203-2ed4533175c6,
location: https://graph.microsoft.com/beta/compliance/ediscovery/cases('5b840b94-f821-4c4a-8cad-3a90062bf51a')/operations('2ad2da7c7dbb404abfbbb28b7b6babd6'),
request-id: 9e6b9230-113c-49de-8f7d-ecb90d35b0de