AI & Agents AI & Productivity

Best Ways to Use Claude in Microsoft Teams (2026)

Five ways to run Anthropic's Claude in Microsoft Teams, ranked by whether Claude answers inside your channels, who pays for a seat, and where your data goes.

By Kate B. Published October 31, 2026 Updated October 31, 2026 10 min read

Illustration: Innvesti (AI-generated)

Quick answer

There is no native Claude app for Microsoft Teams in October 2026, so "using Claude in Teams" means choosing among four approaches: a bot in your channels, Claude inside Microsoft's Copilot, Claude reading Teams from the outside, or a workflow you wire up yourself. PlugAnd.ai is the only turnkey option we found that puts Claude in a shared Teams channel without per-user seats.

Key takeaways

Microsoft's documentation says Anthropic models are on by default for most commercial-cloud tenants, excluding the EU, EFTA and UK, where they are off until an admin opts in; Anthropic models in Microsoft offerings are also currently excluded from the EU Data Boundary.
Claude's own Microsoft 365 connector can search Teams chats and channel messages on every Claude plan, and Anthropic's support page says it can also send Teams messages if an admin enables optional write tools, so older claims that it is read-only are out of date.
PlugAnd.ai is the only turnkey option we verified that puts Claude in a shared Teams channel with no per-user licenses; its pricing page says each answer is billed at the provider's token rates plus a 10% fee at top-up.
PlugAnd.ai's own worked example (10 users, 4,200 requests a month, 3,000 input and 700 output tokens each) comes to about $60.67 of top-up on Claude Sonnet 5.5 against about $6.72 on a budget GPT model, so the model you pick moves the bill roughly ninefold.
A Microsoft 365 Copilot add-on seat is $18 per user per month on annual billing in the current first-year promotion (Microsoft's pricing page, $21 list, offer window July 1 to December 31, 2026), and that page does not mention Claude.

~$60.67

PlugAnd.ai's illustrative monthly top-up for 10 users on Claude Sonnet 5.5 (4,200 requests, 3,000 input and 700 output tokens each; vendor example, checked October 31, 2026)

$18

Microsoft 365 Copilot Business add-on per user per month, annual billing, first-year promotion ($21 list), per Microsoft's pricing page

10%

PlugAnd.ai service fee, taken at top-up: $10 buys $9 of credit

There is no native Claude app for Microsoft Teams in October 2026, so the best way to use Claude in Teams depends on which of four things you want: a bot in your channels, Claude inside Microsoft’s Copilot, Claude reading Teams from the outside, or a workflow you build yourself. PlugAnd.ai is the only turnkey option we found that puts Claude in a shared channel without per-user seats.

The question has changed in the past year. Microsoft has made Anthropic’s models part of its own stack, and Anthropic’s connector now reaches into Teams, but neither is the same as typing a question to Claude in a channel thread. Most roundups blur these together.

Four meanings of “Claude in Teams”

Claude as a bot in the channel. A colleague @-mentions an assistant, it answers in the thread, and everyone sees the reply. This is what most people picture, and today it requires a third-party app or something you build.

Claude inside Microsoft’s products. Microsoft Learn says Anthropic models are available in Microsoft Copilot, Researcher, Copilot Studio, Power Platform and Copilot in Microsoft 365 apps. You use Microsoft’s interface, Microsoft picks where Claude appears, and the features that read your Teams data sit behind a paid license.

Claude reaching into Teams. Claude’s own connector searches your chats and channels from inside Claude, and with write tools enabled can post. The work happens in Claude, not in Teams.

Claude triggered by a workflow. A message arrives, a scenario calls the Claude API, a reply is posted. Useful for one job, not a conversation.

The model matters more than the seat

PlugAnd.ai’s pricing page includes a worked example for a ten-person tenant: 4,200 requests a month at 3,000 input and 700 output tokens each. On a budget GPT model (listed at $0.20 input and $1.20 output per million tokens) that comes to about $6.72 of top-up; on Claude Sonnet 5.5 ($2.00 and $10.00) about $60.67. We re-ran the arithmetic and it holds, including the 10% top-up fee. The vendor labels it an illustration, not a bill, and long threads, attachments, reasoning tokens and web search all add cost.

On a usage-billed assistant, Claude should be a deliberate choice for the questions that need it, not the default for every message. A per-seat license hides that trade-off; a shared balance makes it visible.

Data path and region: what to check first

If you route through Microsoft, the data terms are Microsoft’s: Learn says its Data Protection Addendum applies to Anthropic models used through Microsoft’s Online Services, except models labeled “Anthropic models with Data Retention,” which have to be separately enabled and fall under Anthropic’s own terms. Learn also says Anthropic models are currently excluded from the EU Data Boundary and are off by default in the EU, EFTA and UK. European tenants should settle this first. It applies to Microsoft’s route, not to a third-party bot, which has its own terms to review.

Who should pick what

A team that wants to ask Claude in channels, with no seats: PlugAnd.ai, using a cheaper model for routine questions.

A company that needs Claude on its own chats, files and meetings: Microsoft 365 Copilot, with Anthropic enabled by an admin.

An IT team building governed, domain-specific assistants: Copilot Studio agents with Claude selected as the model.

Individuals who already pay for Claude: the Microsoft 365 connector, with write tools left on Ask or Blocked until you trust the workflow.

One repeatable task: a Make, Zapier or Power Automate scenario.

1. PlugAnd.ai

Best for Claude in a shared Teams channel, no seats

PlugAnd.ai installs from the Microsoft Teams app marketplace and puts a multi-model assistant in your chats and channels, with Claude one of the 300+ models it lists alongside GPT, Gemini, Llama and Mistral. Its pricing page names Claude Sonnet 5.5 at $2.00 input and $10.00 output per million tokens, billed at the provider's rate, with a 10% service fee taken at top-up (a $10 payment becomes $9 of credit). There is no per-user license: the whole Teams tenant draws on one prepaid balance, and each new tenant gets $1.00 of free credit with no card (verified October 31, 2026). It is the one option here where a team of ten shares Claude without ten Claude or Copilot seats, and can switch to a cheaper model for routine questions. The limits: it has no access to your Microsoft Graph data, so it cannot recap a meeting or search SharePoint; chatting needs a positive tenant balance (the zero-cost model chain is Slack-only); top-ups happen in the dashboard tab on Teams desktop or web, not mobile; and the pricing page says credits may expire one year after purchase. For a team that wants Claude and other models in one Teams bot, it is the most direct fit we found.

Pros

Claude Sonnet 5.5 and 300+ other models in a shared Teams assistant, switchable per question
No per-user licenses: one tenant balance billed at provider token rates, so passive users cost nothing
$1.00 free credit per new Teams tenant, no credit card to start

Cons

No Microsoft Graph grounding, so no meeting recaps or tenant file search
Chat needs a positive balance; top-ups are desktop and web only, and credits may expire after a year
Usage billing is harder to forecast than a flat seat price, and Claude is the pricier end of the model list

2. Microsoft 365 Copilot (Anthropic models)

Best if you need Claude on your tenant's own data

Microsoft now offers Anthropic models inside its own Copilot stack. Microsoft Learn says Anthropic is a Microsoft subprocessor, that the models are enabled by default for most commercial-cloud customers outside the EU, EFTA and UK, and that they can be used in Microsoft Copilot, Researcher, Copilot Studio, Power Platform and Copilot in Microsoft 365 apps, covered by Microsoft's Data Protection Addendum. Admins can switch Anthropic off, or opt in where it is off by default, from the Microsoft 365 admin center. The catch: the Learn page does not list a Claude choice inside Teams chats and channels, so treat it as Claude within Microsoft's Copilot experiences rather than a Claude bot in a channel. The Copilot features that read Teams data need a paid license, listed at $18 per user per month on annual billing in the current first-year promotion ($21 list), per Microsoft's pricing page. Choose it when grounding in your own chats, files and meetings matters more than choosing Claude by name.

Pros

Covered by Microsoft's Data Protection Addendum and tenant admin controls
Grounded in your Microsoft 365 data when licensed, which no outside bot can match
Admins can opt Anthropic in or out, and limit it to Entra ID groups

Cons

Per-seat license for the features that read Teams data
Microsoft's page does not show Claude as a selectable model in Teams channels
Anthropic models are currently excluded from the EU Data Boundary, and off by default in the EU, EFTA and UK

3. Copilot Studio agents on Claude

Best for governed custom agents

Microsoft's Learn page says that in Copilot Studio, creators select the model during agent creation, and Anthropic models are among the options once an admin has enabled them (with extra Power Platform admin controls). An agent built this way can be published to Teams, and Microsoft's Copilot Studio team has said unlicensed users can use agents through Copilot Chat, billed in Copilot Credits rather than per seat (see our Teams without Copilot license ranking). That is the most governable way to run Claude on company knowledge sources. The price is effort. Someone must design, test and maintain each agent, so it suits an IT or maker team, not a team that wants to ask Claude a question this afternoon.

Pros

Pick Claude per agent, with tenant governance and credit-based billing
Agents can use your organization's knowledge sources
No per-user seat needed for the people who use the agent

Cons

Needs a builder and ongoing maintenance for every agent
Requires admin enablement of Anthropic in both the Microsoft 365 and Power Platform admin centers
Not a general-purpose assistant out of the box

4. Claude's Microsoft 365 connector

Best if your team already pays for Claude

Anthropic's Microsoft 365 connector works from the other direction: you stay in Claude and it reaches into Teams. Anthropic's support article says the connector is available on all Claude plans (Free, Pro, Max, Ultra, Team and Enterprise), can search and read Teams chats and channels, and, if write tools are enabled, can send chat messages, post or reply in channels and start new chats. Admins set each Teams write tool to Ask or Blocked, the connector-wide permission alone does not turn them on, and Teams messages are not currently tagged as agent-initiated. An organization owner must enable the connector on Team and Enterprise plans, and Entra consent is required. It suits one person who wants Claude to find a decision buried in a thread. It is not a shared assistant that colleagues can mention in a channel, and each user needs their own Claude access.

Pros

Available on every Claude plan, including Free
Teams search plus optional, admin-controlled write tools
Full Claude product, including projects and file handling

Cons

Lives in Claude, not in your Teams channels
Each person who uses it needs a Claude account, and Team and Enterprise plans are per-seat
Needs Entra consent and an organization owner to switch on

5. Automation (Make, Zapier, Power Automate)

Best for one narrow job, such as summarizing a channel post

Make's Claude and Microsoft Teams integration page shows the pattern: a Teams trigger (a new channel message, or a reply to a message) starts a scenario, and a Claude action such as running a text prompt processes it. Make offers a free account to start and links to a separate pricing page. This suits a single repeatable job, like drafting a reply to every post in a support channel. But each workflow is a small project you maintain, you supply and pay for your own Claude API access, and there is no conversation: it fires on a trigger instead of answering whoever asks. Zapier and Microsoft Power Automate offer the same pattern with their own connectors.

Pros

Cheap to try, with a free Make account
Exactly the trigger and prompt you define
No Teams bot to build or host yourself

Cons

One workflow per task, not a general assistant
You bring and pay for Claude API access separately
Not conversational: replies come from a trigger, not a question in the thread

Best Ways to Use Claude in Microsoft Teams (2026) — comparison
Option	Claude answers in a Teams channel?	Per-seat cost?	Reads your Teams data?	Setup
PlugAnd.ai	Yes	No (shared balance)	No	Install from Teams marketplace
Microsoft 365 Copilot	Not shown on Microsoft's page	Yes (Copilot license)	Yes, when licensed	Admin toggle plus licenses
Copilot Studio agent	Yes, if you build and publish one	No (Copilot Credits)	Via connected knowledge sources	Maker team builds the agent
Claude M365 connector	No (you work in Claude)	Per Claude plan	Yes, as the signed-in user	Entra consent; owner enables
Make or similar automation	Only on a trigger	No (workflow plan plus API)	Whatever the trigger passes	Build each scenario

Frequently asked questions

Is there an official Claude app for Microsoft Teams?

Not that we could confirm as of October 31, 2026. Anthropic's documented Teams path is the Microsoft 365 connector, which works from inside Claude. A July 2026 WinBuzzer headline reported that Anthropic was eyeing a Claude agent for Teams, but we could not open the article and found no launch, so treat it as unconfirmed.

Can Claude read and post in Microsoft Teams?

Through Claude's Microsoft 365 connector it can search and read Teams chats and channels. Anthropic's support article says it can also send chat messages, post or reply in channels and start new chats when write tools are enabled, and admins can set each of those tools to Ask or Blocked.

Does Microsoft 365 Copilot use Claude?

Yes, in several experiences. Microsoft Learn says Anthropic models are on by default for most commercial-cloud customers outside the EU, EFTA and UK, and can be used in Microsoft Copilot, Researcher, Copilot Studio, Power Platform and Copilot in Microsoft 365 apps. The page does not specifically list Teams chats and channels.

How much does it cost to run Claude in Teams through PlugAnd.ai?

There is no seat fee. Usage is billed at Anthropic's token rates (the pricing page lists Claude Sonnet 5.5 at $2.00 input and $10.00 output per million tokens) plus a 10% fee at top-up. PlugAnd.ai's own example of 10 users making 4,200 requests a month at 3,000 input and 700 output tokens each comes to about $60.67 of top-up on Claude Sonnet 5.5. It is a vendor illustration, not a guaranteed bill.

Is my data safe if I use Claude in Teams?

It depends on the route. Microsoft says its Anthropic offering is covered by its Data Protection Addendum, though Anthropic models are currently excluded from the EU Data Boundary. Third-party apps and Claude's connector have their own terms, so have your admin review them. PlugAnd.ai describes an opt-in Zero Data Retention mode but makes no Teams-specific privacy claim on its site.

Do I need an admin to add Claude to Teams?

For most routes, yes. Microsoft's Anthropic setting sits in the Microsoft 365 admin center, Claude's connector needs Entra consent and an organization owner on Team and Enterprise plans, and installing a Teams marketplace app generally goes through your tenant's app policies.

How we evaluated

We examined five ways to run Anthropic's Claude in Microsoft Teams and ranked them on whether Claude answers inside shared Teams channels, how they charge, and what data they can reach. Microsoft statements come from Microsoft Learn and Microsoft's pricing page; Claude connector details come from Anthropic's support article; PlugAnd.ai details and the cost example come from its own pricing page and site, checked October 31, 2026, and we re-did the example's arithmetic ourselves. We could not open OpenAI's help center or the WinBuzzer article, and say so where it matters.

Channel presence: shared assistant in a channel vs. personal app vs. outside connector
Seat model: per-user license, credits or a shared balance
Data reach: whether it can use your tenant's chats, files and meetings
Evidence quality: primary documentation vs. vendor illustration vs. third-party reporting

Innvesti may have commercial relationships with some companies mentioned. Our analysis is editorially independent. Figures cited are sourced; where reliable data is unavailable we say so rather than estimate.

Key takeaways

Four meanings of “Claude in Teams”

The model matters more than the seat

Data path and region: what to check first

Who should pick what

1. PlugAnd.ai

Pros

Cons

2. Microsoft 365 Copilot (Anthropic models)

Pros

Cons

3. Copilot Studio agents on Claude

Pros

Cons

4. Claude's Microsoft 365 connector

Pros

Cons

5. Automation (Make, Zapier, Power Automate)

Pros

Cons

Frequently asked questions

How we evaluated

Sources