Skip to main content

OneDrive

The OneDrive connection lets agents search for files and read their content from the connected user’s OneDrive. Use it when an agent should look up an existing document, read a shared Microsoft file by URL, or summarize stored material without creating or editing files.

When to Use It​

Use it when an agent needs to:

  • find a file by name,
  • browse files inside a folder,
  • read a file by OneDrive-relative path,
  • read a file from a full Microsoft sharing URL,
  • summarize or extract information from an existing document.

Setup​

  1. In Connections, click on Add Integration.
  2. Select OneDrive.
  3. Sign in with a Microsoft account that has access to the intended OneDrive files.
  4. Review whether the connection should stay private or be shared.
  5. Save the connection and attach it only where OneDrive access is actually needed.

What the Tool Can Do​

  • list accessible files from OneDrive root or from a selected folder,
  • search files by file name,
  • read a file by exact or partial file name,
  • read a file by a OneDrive-relative path such as Documents/Finance/Q2-report.docx,
  • read a file by a full Microsoft URL.

Read-Only Behavior​

The released OneDrive tool surface is read-only. It does not create, update, rename, or delete files in this release.

Use this connection when the job is document discovery and reading. Use these related connections when the agent must write files:

If the content lives in a team site rather than in a user drive, consider SharePoint instead.

In practice:

  • use OneDrive to find and read existing files,
  • use Office 365 Word when the agent should create or rewrite Word documents,
  • use Office 365 Excel when the agent should create, append, or replace spreadsheet-style content.

Path and URL Examples​

Typical file-path input:

  • Documents/Onboarding/Welcome-pack.docx
  • Shared/Reports/Customer-summary.pdf

Typical URL input:

  • full onedrive.live.com or Microsoft file URLs,
  • sharepoint.com document URLs shared by a user,
  • file links copied directly from Microsoft 365.

If the agent already has the exact document URL, using the URL form is usually more reliable than searching by a broad file name.

Use file-name search when the user knows roughly what the document is called. Use path input when the folder structure is known. Use URL input when a copied Microsoft 365 link is already available and you want to avoid ambiguity.

Security and Confirmation​

The connection is read-only, but it can still expose sensitive business content. Keep it scoped to the same audience that could already open those files in Microsoft 365.

Recommended rules:

  • avoid attaching OneDrive broadly to public-facing agents,
  • use a dedicated account when the files represent a shared business source,
  • verify the returned file identity before trusting a summary based on a partial file name match.

Example Usage​

Find the latest customer onboarding deck in my OneDrive and summarize the sections that explain implementation timing.

Read this Microsoft document URL and extract only the action items and due dates.

Technical Notes​

  • Implementation: the connection exposes OneDrive search and file-reading operations through Microsoft Graph.
  • Authentication/scopes: uses Microsoft OAuth/Graph access. The connected account must already have permission to the target file.
  • Functions: list files, read file by name or path, and read file by full Microsoft URL.
  • Write behavior: none in this release. If the use case requires file creation or editing, use an appropriate Microsoft 365 writing connection instead.
Last updated on