Connect Microsoft OneDrive to Claude Cowork
Give Claude Cowork governed access to Microsoft OneDrive’s 11 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft OneDrive to Claude Cowork in four steps
Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.
- 1
Approve Microsoft OneDrive in Runlayer
Add Microsoft OneDrive from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude Cowork to Runlayer
Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Microsoft OneDrive’s 11 tools show up in Claude Cowork’s own tool list.
Claude Cowork setup guide - 3
Sign in to Microsoft OneDrive
Sign in the way Microsoft OneDrive requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Microsoft OneDrive from Claude Cowork
Microsoft OneDrive’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
11 Microsoft OneDrive tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork users can call. 5 read data only and 1 can change or delete data.
Create folder
Create a new folder in OneDrive.
Create share link
Create a shareable link for a OneDrive item.
Delete item
Delete a OneDrive item (file or folder) by id.
Get item
Fetch metadata for a single OneDrive item (file or folder) by id.
List items
List the immediate children of a OneDrive folder.
List shared with me
List items that other users have shared with the caller via OneDrive, including files in SharePoint document libraries.
Move item
Move a file or folder to a different folder within the user's OneDrive.
Read file
Download a OneDrive file by id and return its text.
Control
What Runlayer can see and stop in Claude Cowork
Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.
Gateway policy (available)
Every Microsoft OneDrive call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.
OTLP telemetry (available)
Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Stop a call before it runs (available)
Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.
In Claude Cowork
- Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.
Frequently asked questions
Connect more
