As of July 2026 OpenAI does not publish a ChatGPT bot inside the Microsoft Teams client. What it publishes is the Microsoft Teams app for ChatGPT: a plugin that runs inside chatgpt.com and reads your Teams chats, channels and group chats. Unusually, and unlike the equivalent Claude connector, it can also write - creating chats and channels and sending messages and replies - but only when an admin has enabled actions, and only initiated from ChatGPT rather than from Teams. There are two variants: a self-service one for Business, Enterprise and Edu, and an admin-managed read-only sync for Enterprise and Edu. If you want something people can mention in a Teams channel, your real options are Microsoft 365 Copilot, a third-party Teams app, or a bot you build on the Teams SDK.
OpenAI has no bot inside Teams.
It does have a way in.
There is no @ChatGPT you can mention in a Teams channel. There is a plugin that lets ChatGPT read your Teams - and, with actions on, send messages back into it. That distinction decides your whole rollout.
The short answer.
| At a glance | |
|---|---|
| Is there a ChatGPT bot inside Teams? | No. OpenAI publishes no bot or app inside the Microsoft Teams client. There are three help articles for Slack and none for a ChatGPT app in Teams. |
| What does exist | The Microsoft Teams app for ChatGPT: a plugin inside chatgpt.com that searches and reads Teams chats, channels and group chats. |
| Can it write to Teams? | Yes, when actions are enabled: creating chats and channels, and sending messages and replies. This is a real difference from the equivalent Claude connector, which cannot post to Teams at all. |
| Plans it needs | ChatGPT Business, Enterprise or Edu for the self-service plugin. The admin-managed sync variant is Enterprise and Edu only, and is read-only. |
| Who has to approve it | A Microsoft Entra administrator must grant consent for the Graph scopes, separately from ChatGPT's own action controls. Users often have to reconnect after any scope change. |
| The in-Teams alternative | Microsoft 365 Copilot is the assistant that actually lives in Teams. It is no longer OpenAI-only - Anthropic models run across it, and can be set as the default in the EU, EFTA and UK. |
| Build-your-own stack | The Teams SDK for Teams-only apps, or the Microsoft 365 Agents SDK for multi-channel. Do not start from the Bot Framework SDK - it is archived and unsupported since the end of 2025. |
Last reviewed 2026-07-29 View as Markdown
Your options.
Read this table before promising anyone an @mention in a Teams channel, because that specific outcome has no first-party OpenAI answer.
| Approach | What you get | Where it stops |
|---|---|---|
| The Teams plugin for ChatGPT | From chatgpt.com, ChatGPT searches and reads Teams chats, channels and group chats, works with Planner plans and tasks, and - with actions enabled - creates chats and channels and sends messages and replies. Enterprise users can also retrieve meeting transcript text. | You work in ChatGPT, not in Teams. Every action is one you asked for in that moment. Business, Enterprise or Edu plans only, and Entra admin consent is mandatory. |
| The admin-managed sync variant | An administrator connects Teams once and it is indexed for everyone, with no per-user OAuth dance. Much less setup friction across a large org. | Enterprise and Edu only, and strictly read-only. No sending, no channel creation, no Planner writes. |
| Microsoft 365 Copilot | The assistant that genuinely lives in Teams, in the meeting, in the chat and in the Office apps, with the tenant's own data behind it. | It is Microsoft's product, not OpenAI's, and no longer OpenAI-only - Anthropic models run across it and can be set as the default in the EU, EFTA and UK. A per-user licence on top of your Microsoft 365 bill. |
| A Teams agent you build | The only way to get a GPT-powered agent you can @mention in a Teams channel. The Teams SDK covers Teams-only apps; the Microsoft 365 Agents SDK covers multi-channel. | Two admin gates in two consoles, streaming that only works in one-to-one chats, and a framework landscape that has renamed itself twice in two years. You own hosting, auth, state and the token bill. |
| An AI teammate that already runs in Teams | A product built to live in Teams: 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. Judge it on a real job in the first week rather than on the feature list. |
Step by step.
Steps one to four set up the Teams plugin, which is the fast path and answers whether this is useful at all. Steps five to seven cover building the in-channel agent the plugin cannot give you.
01 Be precise about the outcome you promised
"ChatGPT in Teams" is used for two very different things: ChatGPT reading your Teams from chatgpt.com, and an assistant people mention inside a Teams channel. OpenAI ships the first and not the second. Getting this wrong is the single most expensive mistake in this whole area.
02 Line up Entra consent first
Every Microsoft app in ChatGPT needs a Microsoft Entra administrator to grant consent for its Graph scopes, and that is separate from ChatGPT's own action controls. This is the most common support issue OpenAI reports on these integrations, and it is the item with a lead time.
ScopesChat.Read, ChatMessage.Send, ChannelMessage.Send, Tasks.ReadWrite and more, depending on the actions you enable
03 Pick self-service or admin-managed sync
Self-service means each person connects their own Teams and you get search plus actions. Admin-managed sync means an administrator connects once for everyone, with no user setup, but it is read-only and Enterprise or Edu only. Large orgs almost always want the second unless they need writes.
04 Enable actions deliberately, not by default
Read access and write actions are separate switches. Sending a Teams message on someone's behalf is a meaningful step up in blast radius, so turn actions on once you know who is using this and for what, rather than as part of the initial rollout.
05 For an in-channel agent, start on the right SDK
This is where most guidance online is out of date. The Bot Framework SDK is archived and Microsoft stopped servicing support tickets for it after 31 December 2025. Teams AI Library v1 is deprecated. New builds use the Teams SDK for Teams-only apps, or the Microsoft 365 Agents SDK for anything spanning Microsoft 365, with Agents Toolkit v5 for scaffolding.
Do not start fromBot Framework SDK, TeamsFx SDK, or Teams AI Library v1
06 Design around Teams' streaming limits, not Slack's
Teams streaming works only in one-to-one chats, never in channels or group chats, and it wants the full cumulative content resent on each update rather than deltas. It throttles at about one request per second and hard-stops after two minutes. If you copied a streaming design from a Slack bot, it will not survive contact.
Also7 sends per second per thread, 1,800 operations per hour per thread
07 Budget for the app-approval gauntlet
A Teams administrator has to allow custom app upload in the Teams admin center, and Microsoft documents that availability changes take up to 24 hours to reach all users and in rare cases up to six days. Submitting an app to your organisation is also not the same as publishing it - an administrator has to publish it separately.
ConsoleTeams admin center, Teams apps then Setup policies
What trips people up.
Teams is where the distance between the blog posts and the shipping product is widest, in both directions.
"Install ChatGPT in Teams" usually means something else
Guides with that title are almost always describing the ChatGPT-side plugin that reads Teams, or a third-party app that is not built by OpenAI. Check the publisher before you trust a listing. OpenAI does publish into the Microsoft ecosystem, but its own Office add-in is scoped to Excel and PowerPoint, with Teams absent.
Copilot is not ChatGPT any more
The assumption that Microsoft 365 Copilot is simply ChatGPT inside Office is out of date. Copilot has been multi-model since late 2025, with Anthropic models running across it, and since April 2026 administrators in the EU, EFTA and UK can make Anthropic the default. If your rationale for Copilot was "we already pay for the same model", check that first.
Two consoles, two admins, one long wait
Entra consent for Graph scopes and Teams admin center app policy are separate approvals held by different people, and the Teams side can take a day or, rarely, most of a week to propagate. The code is never the schedule here.
Approving is not publishing
An app submitted to your organisation sits in the Teams admin center until an administrator separately publishes it. Teams routinely lose a week assuming the submission was the last step, then blame the vendor.
The framework names changed twice
Bot Framework SDK is archived. Teams AI Library was renamed the Teams SDK and its v1 is deprecated. TeamsFx is deprecated with community-only support. Teams Toolkit became Agents Toolkit. Any tutorial written before 2026 is naming at least one dead thing.
Streaming is backwards compared with Slack
Slack now streams true deltas. Teams wants the whole message resent each time, only in one-to-one chats, at roughly one update per second, with a two-minute ceiling after which it refuses outright. Do not port the design across.
Data residency stops at the connector
OpenAI's residency commitments cover its own storage up to the point a query is sent to a connected app. Past that boundary, the connected app's residency and retention rules apply. Worth knowing before you tell a compliance team that European residency covers the whole flow.
Everyone will tell you ChatGPT works with Teams. Almost nobody will tell you which side of the boundary the work happens on.
Or skip the build.
If the outcome you want is an AI you mention in a Teams channel that then does the work behind the answer, that exists today - it just is not OpenAI shipping it. Beagle runs in Microsoft Teams and Slack alike, on 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 chatgpt.com tab, no pasting the answer back in.
It works across the stack, not one service
Beagle reads the CRM, the tracker, the docs and the inbox under OAuth you control, and drafts the deliverable rather than stopping at a summary.
Nothing for your team to host or patch
No custom agent to stand up, no SDK generation to track, no streaming quirks to work around. It installs as a normal Teams app.
Every outbound send waits for a human
Reports, replies and updates arrive drafted and held for 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 ChatGPT app for Microsoft Teams?
Not inside Teams. OpenAI publishes the Microsoft Teams app for ChatGPT, which is a plugin that runs inside chatgpt.com and reads your Teams. There is no OpenAI-published bot you can mention in a Teams channel - OpenAI has three help articles for Slack integrations and none for a ChatGPT app inside the Teams client.
Can ChatGPT read and send Microsoft Teams messages?
Yes to both, through the Teams plugin, but always initiated from ChatGPT. It can search and read chats, channels and group chats, and when an admin has enabled actions it can create chats and channels and send messages and replies. Enterprise users can also retrieve meeting transcript text. There is a separate admin-managed sync variant that is read-only and available on Enterprise and Edu.
How do I get an AI assistant I can @mention in a Teams channel?
Three options. Microsoft 365 Copilot, which lives in Teams natively. A third-party Teams app built for the purpose. Or build your own on the Teams SDK for a Teams-only app, or the Microsoft 365 Agents SDK for multi-channel - not the Bot Framework SDK, which is archived and has been unsupported since the end of 2025.
Is Microsoft 365 Copilot just ChatGPT in Teams?
Not any more. Copilot has been multi-model since late 2025, with Anthropic models running across Office and Copilot surfaces, and since April 2026 administrators in the EU, EFTA and UK can set Anthropic as the default model. If you chose Copilot on the basis that it was the same model as ChatGPT, that reasoning no longer holds.
What approvals does our IT team need to grant?
A Microsoft Entra administrator must consent to the Graph scopes the plugin uses, which is separate from ChatGPT's own action controls, and users often need to reconnect after any scope change. If you are deploying a custom Teams agent instead, a Teams administrator must also allow custom app upload and then separately publish the app - and Microsoft documents that availability changes take up to 24 hours, and in rare cases up to six days, to reach everyone.
Why does our Teams bot's streaming response keep failing?
Teams streaming only works in one-to-one chats, never in channels or group chats. It expects the full cumulative message resent on each update rather than deltas, throttles at about one request per second, and hard-stops after two minutes with a content-stream error. A streaming design ported from a Slack bot will fail on all four counts.
