OneDrive: what this connector can do

Member·5 minutes to read

What this page is for

docs/connectors/microsoft-365.md is the setup guide for whoever runs your organisation's Botseon deployment — creating the vendor application and entering its credentials. This page is the other half: what OneDrive actually lets a bot do once it is connected to your account, what it asks you for along the way, its limits, and how to take the connection away again, in Botseon and at Microsoft.

Files across your Microsoft 365 account: search, list, read, create, upload and share files.

What a bot can do with it

Read — OneDrive tells a bot things, nothing changes

Tool	What it does
`onedrive.search_files`	Search files in the drive.
`onedrive.read_file`	Read a file as text.
`onedrive.list_folder`	List what is in the drive’s root or in a folder, with each entry’s name, kind and size.

Write — OneDrive lets a bot change things

Tool	What it does
`onedrive.create_file`	Create a file in a folder.
`onedrive.update_file`	Replace a file’s contents.
`onedrive.upload_file`	Upload a file, such as a spreadsheet or a PDF, into a folder, byte for byte from base64.
`onedrive.share_file`	Share a file with a named person.

Saving a file your bot made

When your bot makes a spreadsheet, a PDF or another file in its computer, ask it to put the file in a OneDrive folder, for example "save the budget to Reports/2026 in my OneDrive". The bot shows you a card naming the file first, and uploads it only after you approve. The file arrives exactly as the bot made it, and opens in OneDrive and its apps like any file you uploaded yourself.

A file is at most 16 MiB. Leave the folder out and the file goes to the top of your OneDrive.
If the folder already has a file with that name, your file is kept and the new one gets OneDrive's renamed copy, such as budget 1.xlsx. The bot tells you the name it got.

The permissions it asks for, in plain words

Every call a bot makes through this connector is tagged with what kind of thing it is. Only the tags below ever apply here — a tag this connector's tools never carry is not listed, because it can never ask you for it.

read — Looks something up. Nothing changes, and nothing is sent anywhere. A bot never has to ask first for this.
write — Changes something inside the connected account — creates, edits or files something. Asks you first, unless you have told Botseon to always allow that exact action.
external_send — Sends something to someone outside Botseon — a message, a reply, an email, a post. Asks you first, unless always-allowed.

Limits

Files across your Microsoft 365 account: search, list, read, create, upload and share files. Nothing outside that list is possible through this connector, however a bot is asked to use it.

OneDrive is also only ever as wide as the scopes your organisation's connected app actually requests — the exact scopes are on the operator's own setup page, docs/connectors/microsoft-365.md, because narrowing or widening them is a decision for whoever runs your deployment, not for this page.

Disconnecting

In Botseon

Open Plugins from the sidebar, press this connector's card to open its detail page, and under Accounts press the ✕ next to the account (its label is "Remove account" and the name of the account), then Revoke and remove to confirm — or Uninstall to remove the plugin and every account connected to it at once. Either one revokes the stored connection immediately: nothing more is read or changed through it from that moment on. Install a plugin walks through the same screen step by step.

At Microsoft

Removing the account in Botseon also asks Microsoft to revoke the token, when this deployment's connector is configured with a revoke URL. Confirm the grant is actually gone by opening Microsoft's own account settings — the connected-apps, security or authorised-apps page covers it — and removing Botseon there too if it still shows up. That is also where you can revoke access without going through Botseon at all, which is worth knowing if you ever lose access to your Botseon account.

What Botseon keeps, and how your data is used

Whatever a bot reads or writes through this connector becomes part of your conversations and the record of that run — the same records, and the same retention schedule, as everything else a bot works on. Botseon is the processor for that content; your organisation decides what it may read and remember, and can delete it sooner than the schedule would on its own.

Your data is sent to a model provider only to produce the bot's answer, and for nothing else — it is not used to train any model. The Privacy Policy's Models and How long we keep it sections have the full detail, including exactly how long each kind of record is kept for.