| title | ediscoveryReviewSet: addToReviewSet |
|---|---|
| description | Start the process of adding a collection from Microsoft 365 services to a review set. |
| author | SeunginLyu |
| ms.localizationpriority | medium |
| ms.subservice | ediscovery |
| doc_type | apiPageType |
| ms.date | 06/10/2024 |
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.
[!INCLUDE national-cloud-support]
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]
POST /security/cases/ediscoveryCases/{eDiscoveryCaseId}/reviewSets/{eDiscoveryReviewSetId}/addToReviewSet| Name | Description |
|---|---|
| Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
| Content-Type | application/json. Required. |
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. |
| 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 example shows 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"
}[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response.
HTTP/1.1 202 Accepted