Skip to content

user-exportpersonaldata.md

Latest commit

 

History

History
129 lines (100 loc) · 4.76 KB

user-exportpersonaldata.md

File metadata and controls

129 lines (100 loc) · 4.76 KB
title user: exportPersonalData
description Submits a data policy operation request, made by a Company Administrator to export an organizational user's data.
ms.localizationpriority medium
author yyuank
ms.reviewer iamut
ms.subservice entra-users
doc_type apiPageType
ms.date 04/17/2024

user: exportPersonalData

Namespace: microsoft.graph

Submit a data policy operation request from a company administrator or an application to export an organizational user's data. This data includes the user's data stored in OneDrive and their activity reports. For more information about exporting data while complying with regulations, see Data Subject Requests and the GDPR and CCPA.

[!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]

Note: The export can only be performed by a company administrator when delegated permissions are used.

HTTP request

POST /users/{id}/exportPersonalData

Request headers

Name Description
Authorization Bearer {token}. Required. Learn more about authentication and authorization.

Request body

In the request body, provide a JSON object with the following parameters.

Parameter Type Description
storageLocation String A shared access signature (SAS) URL to an Azure Storage account, to where data should be exported.

Response

If successful, this method returns a 202 Accepted response code. It doesn't return anything in the response body. The response contains the following response headers.

Name Description
Location URL to check on the status of the request.
Retry-After Time period in seconds. Request maker should wait this long after submitting a request to check for the status.

Example

Request

HTTP

POST https://graph.microsoft.com/v1.0/users/{id}/exportPersonalData
Content-type: application/json

{
  "storageLocation": "storageLocation-value"
}

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
{
  Location: https://graph.microsoft.com/v1.0/dataPolicyOperations/d007e3da-cd9b-4b02-8d66-422403c53e3f
  Retry-After: 60
}
HTTP/1.1 202 Accepted