# Microsoft Teams for AI agents. Managed auth, ready-made tools.

> Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.

- Page: https://www.agent200.com/tools/microsoft-teams/
- Category: Communication
- Authentication: Managed OAuth
- Identifier in code: `microsoft_teams`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

Connector: Microsoft Teams, through Agent200. In code: "microsoft_teams".
What it does: Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.
Page: https://www.agent200.com/tools/microsoft-teams/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Microsoft Teams's own page, through the authorization link Agent200 returns. Never ask a user for a Microsoft Teams password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: microsoft_teams_list_teams, microsoft_teams_list_channels, microsoft_teams_get_channel_messages, microsoft_teams_list_chats, microsoft_teams_get_chat_messages. Write tools: microsoft_teams_send_channel_message, microsoft_teams_reply_message, microsoft_teams_send_chat_message, microsoft_teams_create_meeting. Name "microsoft_teams" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/microsoft-teams/framework/claude/
   https://www.agent200.com/tools/microsoft-teams/framework/chatgpt/
   https://www.agent200.com/tools/microsoft-teams/framework/claude-code/
   https://www.agent200.com/tools/microsoft-teams/framework/muse/
   https://www.agent200.com/tools/microsoft-teams/framework/grok-bot/
   https://www.agent200.com/tools/microsoft-teams/framework/openai-dots/
   https://www.agent200.com/tools/microsoft-teams/framework/claude-duet/
   https://www.agent200.com/tools/microsoft-teams/framework/hermes-agent/
   https://www.agent200.com/tools/microsoft-teams/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the Microsoft Teams connector, your agent works in the teams, channels and chats of each user who connects their own Microsoft account. It can catch a user up on a channel, reply in a thread, message a colleague or set up an online meeting, using only the tools your project allows.

Microsoft Teams is Microsoft's workspace for chat, channels and meetings, part of Microsoft 365.

## Microsoft Teams tools

- **List teams** (`microsoft_teams_list_teams`, read): List the teams the user is a member of.
- **List channels** (`microsoft_teams_list_channels`, read): List the channels in a team.
- **Read a channel** (`microsoft_teams_get_channel_messages`, read): Read recent messages in a channel.
- **Post in a channel** (`microsoft_teams_send_channel_message`, write): Post a new message in a channel.
- **Reply to a message** (`microsoft_teams_reply_message`, write): Reply in the thread of a channel message.
- **List chats** (`microsoft_teams_list_chats`, read): List the user's one-on-one and group chats.
- **Read a chat** (`microsoft_teams_get_chat_messages`, read): Read recent messages in a chat.
- **Send a chat message** (`microsoft_teams_send_chat_message`, write): Send a message in a one-on-one or group chat.
- **Create a meeting** (`microsoft_teams_create_meeting`, write): Create an online meeting and get its join link.

## Limits you can set

**Turn single tools on or off.** Keep the reading tools and switch off `microsoft_teams_send_channel_message` if your agent should never post in a channel.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example chats but not channels. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Microsoft Teams

Each end user authorizes their own Microsoft Teams account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Microsoft Teams account, once.
const connection = await agent200
  .user("user_123")
  .connect("microsoft_teams");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Microsoft Teams tools

Name the user, the model and the tools. The model decides which Microsoft Teams tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "What did the design channel discuss today?",
    tools: ["microsoft_teams"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, with their Microsoft work or school account on Microsoft's own sign-in page. You never see or store their password.

**What access is requested.** The Microsoft Graph permissions the connection needs, such as reading chats or sending channel messages, listed on Microsoft's consent screen. Some organizations require an admin to approve these permissions first.

## Example requests

- "What did the design channel discuss today?"
- "Reply to Priya's question in the Launch channel with the new date"
- "Send Tom a chat message asking for the Q3 numbers"
- "Set up a Teams meeting for tomorrow at 10 and give me the link"

## Guides: Microsoft Teams with your AI framework

- [Microsoft Teams + Claude](https://www.agent200.com/tools/microsoft-teams/framework/claude.md): Connect Microsoft Teams to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Microsoft Teams + ChatGPT](https://www.agent200.com/tools/microsoft-teams/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Microsoft Teams into your own agent with OpenAI's models and the Agent200 SDK.
- [Microsoft Teams + Claude Code](https://www.agent200.com/tools/microsoft-teams/framework/claude-code.md): Have Claude Code build a Microsoft Teams agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Microsoft Teams + Muse](https://www.agent200.com/tools/microsoft-teams/framework/muse.md): Connect Microsoft Teams to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Microsoft Teams + Grok Bot](https://www.agent200.com/tools/microsoft-teams/framework/grok-bot.md): Connect Microsoft Teams to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Microsoft Teams + OpenAI Dots](https://www.agent200.com/tools/microsoft-teams/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Microsoft Teams agent with OpenAI's models and the Agent200 SDK.
- [Microsoft Teams + Claude Duet](https://www.agent200.com/tools/microsoft-teams/framework/claude-duet.md): Connect Microsoft Teams to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Microsoft Teams + Hermes Agent](https://www.agent200.com/tools/microsoft-teams/framework/hermes-agent.md): Connect Microsoft Teams to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Microsoft Teams + OpenClaw](https://www.agent200.com/tools/microsoft-teams/framework/openclaw.md): Connect Microsoft Teams to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Microsoft Teams OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Microsoft Teams.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Microsoft Teams connection, never another user's. It cannot reach anything the user or Microsoft Teams has not authorized.

### Can I limit what my agent can do in Microsoft Teams?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [Slack](https://www.agent200.com/tools/slack.md): Search conversations and post messages in the workspaces your users connect.
- [Discord](https://www.agent200.com/tools/discord.md): Read channels, post messages and start threads in the Discord servers your users connect.
- [Zoom](https://www.agent200.com/tools/zoom.md): Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.
- [Telegram](https://www.agent200.com/tools/telegram.md): Send and receive messages, post in groups and channels, and share files through the Telegram bots your users connect.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
