Read
Retrieve selected files, pages, and folders without flattening their permissions.
Overview
Use OneDrive as a governed source or destination in a Context runbook. Configure the exact records and actions each agent can access.
- · Vendor-supported OAuth or scoped service credentials
- · Read and write access configured separately
- · Tool calls and outcomes recorded per run
Connector contract
Control what agents can do in OneDrive.
Exact authentication methods and available scopes depend on your OneDrive plan and deployment. Context keeps the connector configuration explicit.
Act
Draft or update content in the destination chosen by the team.
Verify
Carry source links and revisions with the finished artifact.
Set up the connection
- 01
Authenticate
Connect OneDrive with an admin-approved OAuth flow or scoped credential supported by the vendor.
- 02
Choose scope
Select the accounts, workspaces, projects, or resources available to the runbook.
- 03
Map policy
Set read and write permissions, reviewer gates, and the identity used for each action.
- 04
Test a run
Verify one read, one permitted action, and the resulting audit record before rollout.
Build with OneDrive
OneDrive can be added to any Context runbook. Start from a prebuilt agent, then choose the resources and actions it needs. Browse all agents →
More in Documents & knowledge
Connect OneDrive to Context.
Request demo