Skip to main content
Book a demo

Connect Microsoft Teams to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Microsoft Teams to GitHub Copilot CLI in four steps

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

  1. 1

    Approve Microsoft Teams in Runlayer

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

  2. 2

    Connect GitHub Copilot CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Microsoft Teams’s 60 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI setup guide
  3. 3

    Sign in to Microsoft Teams

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

  4. 4

    Use Microsoft Teams from GitHub Copilot CLI

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

Tools

60 Microsoft Teams tools in GitHub Copilot CLI

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

  • Add channel member

    Add a member to a channel.

  • Add chat member

    Add a member to a group chat.

  • Create channel

    Create a channel in a team.

  • Create chat

    Create a new Teams chat (1:1 or group) and return it.

  • Delete chat message

    Soft-delete a chat message (recoverable).

  • Get channel

    Get a single channel by id.

  • Get chat

    Get a single Teams chat by id.

  • Get chat message

    Get a single message from a Teams chat.

See all 60 Microsoft Teams tools

Control

What Runlayer can see and stop in GitHub Copilot CLI

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Microsoft Teams call from GitHub Copilot CLI 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 CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination