As of July 2026 there is no first-party Claude bot or app for Microsoft Teams - Anthropic ships Claude for Excel, Word, PowerPoint and Outlook, and a Microsoft 365 connector, but nothing you can @mention in a Teams channel. The connector is genuinely useful and often mistaken for a bot: from claude.ai, Claude can search your Teams chats and read your calendar, alongside SharePoint, OneDrive and Outlook. What it cannot do is write - Anthropic's own documentation states plainly that Claude cannot send Teams messages. Anthropic has said it wants to bring Claude Tag to Teams and is running a waitlist, but has given no date. So the paths are: use the connector and accept read-only, build your own Teams agent on the Microsoft 365 Agents SDK, or adopt a product that already lives in Teams.
There is no @Claude bot for Teams.
Here is what there is instead.
Claude can read your Teams chats and calendar today. It cannot post a message back. That gap is the whole story, and it decides which of the three real options is yours.
The short answer.
| At a glance | |
|---|---|
| Is there an official Claude app for Teams? | No. There is no Anthropic-built bot you can @mention in a Teams channel. Claude Tag, the Slack-native agent, has a Teams waitlist but no announced date. |
| What Claude can do with Teams today | Through the Microsoft 365 connector it can search Teams chats and read Teams calendar data, from inside claude.ai. |
| What it cannot do | Send or post Teams messages. Anthropic's documentation states this explicitly. There is no first-party workaround. |
| Plans it needs | The Microsoft 365 connector is available on all Claude plans, including Free. Team and Enterprise additionally need an organisation Owner to enable it. |
| Who has to approve it | A Microsoft Entra Global Administrator must grant one-time tenant consent. Write permissions need Global Administrator or Application Administrator approval on top. |
| Build-your-own stack | The Microsoft 365 Agents SDK plus the Anthropic Messages API. Do not start from the Bot Framework SDK - it was archived and support ended on 31 December 2025. |
| Time to set up | Minutes for the connector, once tenant consent lands. Days to weeks for a custom Teams agent, mostly spent on approvals. |
Last reviewed 2026-07-29 View as Markdown
Your options.
Three real paths, and one non-path that a lot of articles still describe as if it existed. We have left the non-path out.
| Approach | What you get | Where it stops |
|---|---|---|
| The Microsoft 365 connector | From claude.ai, Claude searches Teams chats and reads your Teams calendar, plus SharePoint, OneDrive and Outlook. It mirrors your own Microsoft 365 permissions, so it cannot see anything you could not already see. | Read-only for Teams. Claude cannot send Teams messages or create Teams content. You still work in claude.ai, not in Teams - it is Teams-as-a-source, not Claude-in-Teams. |
| A Teams agent you build | The real way to get an @mentionable Claude into a Teams channel today. The Microsoft 365 Agents SDK handles hosting and the Teams surface; the Anthropic Messages API supplies the model. | Two separate admin gates, in two different consoles, usually held by two different people. You own the hosting, the auth, the conversation state and the token bill, and the SDK underneath you changed generations recently. |
| Claude Tag's Teams waitlist | Anthropic has said it intends to widen Claude Tag beyond Slack and is collecting names for Microsoft Teams. | Announced intent, not a shipped product. There is no date, no beta and nothing to install. Do not plan a rollout around it. |
| An AI teammate that already runs in Teams | A product built to live in Teams from the start: @mention it in a channel, it reads the thread, connects the rest of your stack and drafts the work. Beagle is one of these. | The model choice is the vendor's, not yours. Judge it on a real job in the first week rather than on the feature list. |
Step by step.
Most teams start with the connector, because it takes minutes and answers the question of whether Claude reading your Microsoft data is useful at all. Steps one to four cover that; steps five to seven cover building the bot the connector cannot give you.
01 Line up your Entra admin before anything else
A Microsoft Entra Global Administrator has to grant one-time tenant consent for the Microsoft 365 connector, and write permissions need Global Administrator or Application Administrator approval in the Entra admin center on top. This approval is the schedule, so book it first.
ConsoleEntra admin center, Enterprise applications
02 Enable the connector at the organisation level
On Claude Team and Enterprise plans an organisation Owner has to enable the Microsoft 365 connector before anyone can connect it. On Free, Pro and Max there is no organisation-level step and you go straight to your own settings.
03 Connect it to your own account
Each person connects the Microsoft 365 connector individually from Claude's connector settings. Permissions are delegated: Claude sees exactly what your Microsoft 365 account can see, and nothing beyond it.
04 Set expectations about Teams being read-only
Tell people up front that Claude can find and summarise Teams conversations but cannot reply in them. Half of the disappointment with this setup comes from someone assuming a summary in claude.ai means a reply in Teams is one step away. It is not.
05 For a real Teams bot, start on the Microsoft 365 Agents SDK
This is the step where most guidance online is out of date. The Bot Framework SDK is archived and Microsoft stopped servicing support tickets for it at the end of 2025; TeamsFx is deprecated too. New Teams agents start on the Microsoft 365 Agents SDK, with the Microsoft 365 Agents Toolkit for scaffolding.
Packages@microsoft/agents-hosting and @microsoft/agents-hosting-extensions-teams, Node 20+
06 Wire the model in behind your own handler
Your agent receives the Teams activity, you assemble the context you want the model to have, and you call Anthropic's Messages API. Keep the model call behind your own service so you can swap models, add tools and cap spend without touching the Teams plumbing.
APIPOST api.anthropic.com/v1/messages, with the @anthropic-ai/sdk client
07 Clear the second admin gate: app upload
Publishing a custom agent into Teams needs a Teams administrator to allow custom app upload in the Teams admin center setup policies. Microsoft documents that these changes take up to 24 hours to reach all users, and in rare cases up to six days. This is a different admin, in a different console, from the Entra consent in step one.
ConsoleTeams admin center, Teams apps then Setup policies
What trips people up.
Microsoft Teams is where the gap between what the internet says and what actually ships is widest right now.
Half the tutorials online are for a dead SDK
The Bot Framework SDK and its emulator are archived on GitHub and Microsoft stopped servicing support tickets for them after 31 December 2025. Any tutorial that opens with the Bot Framework SDK, or with TeamsFx, is writing you a maintenance problem. Start on the Microsoft 365 Agents SDK.
Two admins, two consoles, two waits
Entra tenant consent and Teams custom app upload are separate approvals, usually held by different people. Microsoft's own documentation says app availability changes take up to 24 hours to reach all users and, in rare cases, up to six days. Plan the calendar around the approvals, not around the code.
Approving an app and publishing it are different buttons
Submitting an app to your organisation does not put it in front of anyone. It sits in the Teams admin center until an administrator separately publishes it, and teams routinely lose a week believing the submission was the last step.
Reading Teams is not being in Teams
The Microsoft 365 connector genuinely helps - meeting summaries, finding the thread where something was decided - but everything happens in claude.ai. If the outcome you promised your team was "Claude answers in the channel", the connector will not deliver it.
The write matrix is uneven, and Teams is the gap
Through the same connector Claude can create and update SharePoint and OneDrive files and can send Outlook mail and create calendar events. Teams gets nothing writable. It is easy to read one capability announcement and assume it covers all four services.
Waitlists are not roadmaps
Claude Tag for Teams has a waitlist and Anthropic has said it wants to expand availability, but there is no date and nothing to install. If a rollout plan depends on it landing this quarter, the plan has no floor under it.
Reading Teams and working in Teams are different products. Most of the disappointment here comes from a guide that never drew the line.
Or skip the build.
If the outcome you want is an AI that answers in the Teams channel and does the work behind it, that exists today - it just is not Anthropic shipping it. Beagle runs in Microsoft Teams and Slack alike, under the same read-draft-approve loop.
It answers in the channel
Mention Beagle in a Teams channel and it replies in the thread, with the records it pulled from linked. No claude.ai tab, no copy and paste back into Teams.
It reads the same Microsoft stack, and acts on it
Beagle connects to the tools your work already runs on with OAuth you control, and can draft and act across them rather than stopping at a summary.
One tenant approval, not two consoles
Beagle installs into Teams as a normal app. There is no custom-agent hosting to stand up, no SDK generation to track and nothing for you to keep patched.
Everything outbound waits for a human
Reports, replies and updates arrive drafted and held for your approval. Nothing leaves the tenant on the AI's own authority.
Plugged into your stack.
OAuth in, every read scoped to the teammate who asked.
Common questions.
Is there an official Claude app for Microsoft Teams?
No. As of July 2026 Anthropic does not ship a Claude bot or app you can @mention in Microsoft Teams. It ships Claude for Excel, Word and PowerPoint, Claude for Outlook in beta, and a Microsoft 365 connector that reads Teams. Claude Tag, the Slack-native agent, has a Microsoft Teams waitlist but no announced release date.
Can Claude read my Microsoft Teams messages?
Yes, through the Microsoft 365 connector. From claude.ai, Claude can search and read Teams chats and read Teams calendar data, alongside SharePoint, OneDrive and Outlook. Permissions are delegated, so Claude sees only what your own Microsoft 365 account can see.
Can Claude send or post messages in Microsoft Teams?
No. Anthropic's documentation states that Claude cannot send Teams messages. Through the same connector it can write to SharePoint and OneDrive and can send Outlook mail and create calendar events, but Teams is read-only and there is no first-party workaround.
How do I build a Claude bot for Microsoft Teams?
Build a Teams agent on the Microsoft 365 Agents SDK and call Anthropic's Messages API from your own handler. Do not start from the Bot Framework SDK: it is archived and Microsoft stopped servicing support tickets for it after 31 December 2025. Expect two admin approvals - Entra tenant consent for any Graph permissions, and a Teams admin allowing custom app upload, which can take up to 24 hours to take effect.
What does the Microsoft 365 connector need from our IT team?
A Microsoft Entra Global Administrator must grant one-time tenant consent, and write permissions require Global Administrator or Application Administrator approval via Enterprise applications in the Entra admin center. On Claude Team and Enterprise, an organisation Owner must also enable the connector before individuals can connect it.
Is Claude Tag coming to Microsoft Teams?
Anthropic has said it wants to widen Claude Tag beyond Slack and is running a Microsoft Teams waitlist, but it has not announced a date, a beta or anything installable. Treat it as stated intent rather than a roadmap item you can plan a rollout around.
