ediscoveryReviewSet: addToReviewSet

Namespace: microsoft.graph.security

Start the process of adding a collection from Microsoft 365 services to a review set. After the operation is created, you can get the status of the operation by retrieving the Location parameter from the response headers. The location provides a URL that will return a Add to review set operation.


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 /security/cases/ediscoveryCases/{eDiscoveryCaseId}/reviewSets/{eDiscoveryReviewSetId}/addToReviewSet

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
search microsoft.graph.security.ediscoverySearch The ID of the eDiscovery search you'd like to add to the review set.
additionalDataOptions additionalDataOptions The options for adding items to reviewSet.

additionalDataOptions values

Name Description
allVersions include all versions of a sharepoint document matching the source collection query. Caution: SharePoint versions can significantly increase the volume of items
linkedFiles include linked files that were shared in outlook, teams, or yammer messages by attaching a link to the file.


If successful, this action returns a 202 Accepted response code.



The following is an example of a request.

POST https://graph.microsoft.com/v1.0/security/cases/ediscoveryCases/58399dff-cebe-478f-b1af-d3227f1fd645/reviewSets/63ef0fd7-0db2-45eb-a9d7-7d75c8239873/addToReviewSet
Content-Type: application/json

    "search": {
        "id": "c17e91d6-6bc0-4ecb-b388-269ea3d4ffb7"
    "additionalDataOptions": "linkedFiles"


The following is an example of the response.

HTTP/1.1 202 Accepted