Connect Microsoft Teams to Codex
Give Codex governed access to Microsoft Teams’s 60 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft Teams to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 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
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Microsoft Teams’s 60 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 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
Use Microsoft Teams from Codex
Microsoft Teams’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
60 Microsoft Teams tools in Codex
Runlayer policy decides which of these Codex 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.
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Microsoft Teams call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex 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 Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more