Skip to main content
Book a demo

Connect Microsoft Teams to Goose

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

Book a demo Goose setup guide

Set up

Add Microsoft Teams to Goose in four steps

Admins approve the server once. Everyone in Goose 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 Goose to Runlayer

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Microsoft Teams’s 60 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

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

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

Tools

60 Microsoft Teams tools in Goose

Runlayer policy decides which of these Goose 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 Goose

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

  • Gateway policy (available)

    Every Microsoft Teams call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Goose 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 before Goose runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Goose’s model sees it.

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination