Skip to main content
Book a demo

Connect Microsoft SharePoint to GitHub Copilot

Give GitHub Copilot governed access to Microsoft SharePoint’s 40 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot setup guide

Set up

Add Microsoft SharePoint to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Approve Microsoft SharePoint in Runlayer

    Add Microsoft SharePoint from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Microsoft SharePoint’s 40 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Microsoft SharePoint

    Sign in the way Microsoft SharePoint requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Microsoft SharePoint from GitHub Copilot

    Microsoft SharePoint’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.

Tools

40 Microsoft SharePoint tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 9 read data only and 1 can change or delete data.

  • Create list item

    Create a new item in a SharePoint list.

  • Delete list item

    Delete an item from a SharePoint list.

  • Get list item

    Fetch a single item from a SharePoint list by its id.

  • Get site

    Fetch a single SharePoint site's metadata.

  • List drives

    List the document libraries (drives) in a SharePoint site.

  • List folder items

    List files and folders inside a SharePoint document library folder.

  • List list items

    List items in a SharePoint list.

  • List lists

    List SharePoint lists in a site.

See all 40 Microsoft SharePoint tools

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 SharePoint 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

Find another combination