Reference · built on requestConnectorFiles, documents & spreadsheets

OneDrive

Drives and driveItems in OneDrive, with delta queries, upload sessions, and change notifications through Microsoft Graph.

Request accessPricing ↗

About

OneDrive is the personal file store in Microsoft 365 and the consumer service of the same name. Microsoft Graph models both with two resources: a drive, which is the container, and a driveItem, which is a file, folder, or other item inside it. Items are addressed by ID or by path with a colon, such as /me/drive/root:/path/to/file.

Through Fibric, an operator follows a drive's delta feed, reads the items it cares about, and proposes an upload, a move, or a sharing link. You approve the item and the destination. A receipt records what changed, why, and how to reverse it.

This is a reference listing. It documents what Fibric would read from OneDrive and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • A user's drive at /me/drive or /users/{user-id}/drive, and a group's library at /groups/{group-id}/drive
  • Items in a folder through /drives/{drive-id}/root/children, with file, folder, image, and package facets
  • Every change in a drive through the delta method, resumed from the @odata.deltaLink it returns
  • Deleted items, marked with the deleted facet in a delta response
  • Change notifications on the root of a drive at /drives/{id}/root or /users/{id}/drive/root
  • File versions, permissions, thumbnails, and a short-lived @microsoft.graph.downloadUrl for content

Proposed actions

  • Target capability: propose an upload, through createUploadSession for large files, in fragments that are multiples of 320 KiB
  • Target capability: propose a move or rename through the Move item method, or a copy monitored as a long-running action
  • Target capability: propose a sharing link through Create sharing link, or an invitation through Add permissions
  • Target capability: propose restoring an item from the recycle bin

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Collect proof of delivery photos

    Drivers drop photos into a shared folder. The operator reads the delta feed, matches each file name to a stop, and proposes the attachment on the delivery record.

    With Delivery Proof

  • Draft an incident file from what was uploaded

    When a report lands in the incidents folder, the operator reads it, proposes the incident draft in your safety system, and proposes a sharing link for the reviewer.

    With Incident Draft

  • Watch a drive that keeps growing

    The operator sums item sizes from the delta feed, flags the folders growing fastest, and proposes an archive move for the oldest versions.

    With Storage Growth, Backup Proof

Requirements

  • A Microsoft 365 tenant, or personal Microsoft accounts, with an app registration in Microsoft Entra ID
  • Files.Read.All for application-only reads; app-only upload sessions need Sites.ReadWrite.All
  • A public HTTPS endpoint for change notifications, renewed inside the 42,300-minute maximum lifetime
  • Upload fragments sized as multiples of 320 KiB, each under 60 MiB, sent in order
Authentication
A Microsoft Entra application using Microsoft Graph; Files.Read or Files.ReadWrite for a signed-in user, Files.Read.All or Files.ReadWrite.All for application access.

Limits

  • OneDrive for work or school shares SharePoint Online throttling: resource units per app per tenant, with 429 or 503 and Retry-After
  • Change notifications carry only the resource id; the delta method is then called to learn what changed, with latency up to six hours
  • Delta returns the latest state of each item, not each change, and omits path on parentReference; track items by id
  • Timestamp delta tokens and the workbook API work on work or school accounts only, not consumer OneDrive

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request OneDrive ↗

Questions and answers

How does an app track changes in a OneDrive?
Call the delta method on the drive root. Pages arrive with @odata.nextLink; the last page carries @odata.deltaLink, which you store and call later. Deleted items carry the deleted facet. An expired token returns 410 Gone with a fresh link to restart.
How large a file can be uploaded, and how?
Small files go in one PUT. Larger files use createUploadSession, then sequential PUT requests of byte ranges to the uploadUrl. Each range must be a multiple of 320 KiB and under 60 MiB; Microsoft recommends 5 to 10 MiB fragments and resumable transfers above 10 MiB.
Which permission does an app need?
For delegated access, Files.Read reads a user's files and Files.ReadWrite writes them. For application access without a user, Files.Read.All reads and Files.ReadWrite.All or Sites.ReadWrite.All writes. Delta on a drive is available with Files.Read as the least privileged permission.
Ask about OneDrive

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with OneDrive through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy