# Your Teams chats. In your agent.

Source: https://corespeed.io/integrations/microsoft-teams

Connect Microsoft Teams to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent reads your own 1:1 and group chats, finds your teams and their channels, and posts a message to a chat or a channel, using your own Microsoft account. It does not read channel history, and approvals can hold any post.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Microsoft Teams after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Know what was asked. Answer in one place

Let your agent read the chat, pull out what is asked of you, and prepare the update before anything is posted.

You ask your agent: "Read my Teams chat with Stewart from today. List what Stewart needs from me and by when, and draft a short update for the Releases channel. Do not post it."

It calls CoreSpeed:

- `teams-chat__list_chats`: ok, 361 ms
- `teams-chat__list_chat_messages`: ok, 474 ms

It reads from: Microsoft Teams.

### Chat brief: Two asks, one update.

Stewart needs the release notes by 3:00 and wants to know if the export fix shipped.

**What Stewart needs**

- The release notes, by 3:00.
- A yes or no on the export fix.

**Draft for Releases**

- Release 4.2 is out. The export fix is included; notes are in the thread.

_Illustrative chat and draft · Fictional data · Nothing posted_

All connectors: https://corespeed.io/docs/connectors

## Catch up on the chat. Post the update

Requests you can make once Microsoft Teams is connected. The data is fictional.

### Catch up on a chat

Chat with Stewart · Teams chat

- Asks for: The release notes by 3:00
- Still open: Is the export fix in?
- Your own chats

### Find the channel

Product team · Your teams and channels

- Team: Product
- Channel: Releases
- Teams you belong to

### Post under your rules

A post that waits · Approval request

- Tool: Post to a channel
- Policy: Ask before posting to a channel
- Waits for a person

Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Microsoft Teams**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Is Microsoft Teams one connection or two?

Two. Teams covers your teams and posting to their channels; Teams Chat covers your 1:1 and group chats. Connect the ones you need.

### Can my agent read channel messages?

No. It lists your teams and channels and can post to a channel, but it reads only your own chats, not channel history.

### Does it work with a personal Microsoft account?

No. Microsoft supports these Teams features for work or school accounts only.

### Will it post without asking?

Only if you let it. Posting is a separate tool call, and approvals can hold it for a person. How approvals work: https://corespeed.io/solutions/agent-approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/teams

Every tool and price: https://corespeed.io/catalog/teams-chat

## Related pages

- [Outlook Calendar for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/outlook-calendar): Read your Outlook Calendar, find a time that works for everyone, and plan the meeting inside the agent you already use.
- [Outlook for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/outlook): Search your Outlook mail, read the message that matters, and get a brief inside the agent you already use.
- [Slack for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/slack): Bring the Slack conversation into your agent. Find the decisions, the open questions, and what happens next.
- [Shared agent tools and controls for teams](https://corespeed.io/solutions/teams): Manage shared connections, approval policies, and tool usage for teams working across Claude Code, Codex, and other MCP clients.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Microsoft Graph: Teams: https://learn.microsoft.com/en-us/graph/teams-concept-overview
- Microsoft Graph: chats: https://learn.microsoft.com/en-us/graph/api/resources/chat

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)
