Move a DriveItem

To move a DriveItem to a new parent item, your app requests to update the parentReference of the DriveItem to move. This is a special case of the Update method. Your app can combine moving an item to a new container and updating other properties of the item into a single request.

Items cannot be moved between Drives using this request.


One of the following scopes is required to execute this API:

  • Files.ReadWrite
  • Files.ReadWrite.All
  • Sites.ReadWrite.All

HTTP request

PATCH /me/drive/items/{item-id}
PATCH /me/drive/root:/{item-path}
PATCH /drives/{drive-id}/items/{item-id}
PATCH /groups/{group-id}/drive/{item-id}

Request headers

Name Type Description
if-match String If this request header is included and the eTag (or cTag) provided does not match the current eTag on the folder, a 412 Precondition Failed response is returned.

Request body

In the request body, supply the new value for the parentReference property. Existing properties that are not included in the request body will maintain their previous values or be recalculated based on changes to other property values. For best performance you shouldn't include existing values that haven't changed.

Note: When moving items to the root of a OneDrive you cannot use the "id:" "root" syntax. You either need to use the real ID of the root folder, or use {"path": "/drive/root"} for the parent reference.


If successful, this method returns a 200 OK response code and updated DriveItem resource in the response body.


This example moves an item specified by {item-id} into the Documents folder in the user's OneDrive.

Content-type: application/json

    "name": "new-item-name",
    "parentReference" : {"path": "/drive/root:/Documents"}

The following example shows the response.

HTTP/1.1 200 OK
Content-type: application/json

    "id": "0123456789abc",
    "name": "new-item-name",
    "folder": { "childCount": 3 },
  "parentReference": {
    "id": "507DE6D5-0201-496A-AA87-5E2563247982",
    "path": "/drive/root:/Documents"