Connect Microsoft OneDrive to GitHub Copilot
Give GitHub Copilot 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 GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot 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 GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Microsoft OneDrive’s 11 tools through the plugin’s search and execute tools.
GitHub Copilot 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 GitHub Copilot
Microsoft OneDrive’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
11 Microsoft OneDrive tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot 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 GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every Microsoft OneDrive call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more
