Microsoft Teams

What it is

Microsoft Teams is Microsoft’s chat, meetings and calling client, and in 2026 it is also the place where Copilot and third-party agents meet the people who work in a Microsoft tenant. This page scopes Teams as an agent and integration surface for ops teams — which agents, notetakers and front doors actually work inside it — not as a collaboration-suite review.

The correction to make first: Teams is not where agents are built or governed. Copilot Studio and Microsoft Foundry build them, Microsoft Agent 365 governs them, and Teams is the window they show up in. Most “will this work in Teams?” questions are really questions about the licence or the admin policy one layer down.

What actually works natively in Teams

• Microsoft’s own agents. Facilitator takes notes and tracks agenda items in scheduled meetings. Its September 2026 update lets it answer an unanswered factual question unprompted by running a Copilot web search and posting the result to the meeting chat. That behaviour needs a paid Microsoft 365 Copilot licence, is switched on per meeting, and works in scheduled meetings only — not calls, webinars or town halls.
• Third-party agents, now admin-discoverable. Admins can find and enable third-party agents from the Teams admin center, with recommended configuration shown per agent; general availability was scheduled for October 2026. The launch examples are the ones ops teams ask about: GitHub Copilot takes a task handed to it mid-standup and works it in the background while the meeting runs, and Atlassian Rovo pulls Jira and Confluence context into a Teams chat.
• Your own agents. The Teams SDK (renamed from the Teams AI Library in November 2025) is the build path for custom Teams apps. Microsoft has since deprecated the SDK’s built-in AI and MCP plugins in favour of bringing your own framework and wiring MCP or A2A directly. For the other direction — agents reading Teams — Microsoft’s Teams MCP server ships through Agent 365’s tooling gateway, in preview, and requires a Microsoft 365 Copilot licence.
• Notetakers, on Microsoft’s terms. A meeting policy called Manage external bots and their access to meetings (ExternalBotAccessMode, message center MC1459141) reached general availability by the end of September 2026. Its default holds detected bots in the lobby for approval. Vendors in the Teams Bot Identification Program — Otter.ai, Read AI, Recall.ai and Maestro Labs among them — are identified as registered bots; everything else lands under “suspected threats.”

What does not work any more: Teams Live Chat (Customer Connect), the website widget that relayed customer messages into Teams, stopped relaying on 5 October 2026, and Microsoft points those customers to Copilot Studio. A Copilot Studio feature that would have let custom agents join meetings directly was shelved in August 2026 after more than a year on the roadmap. Google Calendar sync through the Teams Admin app is also being retired in October 2026.

Pricing reality

• Teams Essentials — $4/user/month, standalone, for small businesses up to 300 users; no Exchange, SharePoint or Office apps.
• Microsoft Teams Enterprise — $5.25/user/month, the add-on new enterprise customers buy on top of a “no Teams” E3 or E5 suite since Microsoft unbundled Teams worldwide in April 2024.
• Bundled in Business Basic ($7) and Business Standard ($14) after the 1 July 2026 price rise; Business Premium stayed at $22.
• Teams Premium — $10/user/month for intelligent recap, advanced webinars and meeting protection.
• Microsoft 365 Copilot — $30/user/month (Copilot Business for organizations under 300 seats lists at $21, promotionally $18 through 31 December 2026).

The real band for a 200-seat E3 shop: Teams Enterprise alone is 200 × $5.25 × 12 = $12,600/year. Add Teams Premium for everyone and it is $36,600. Add Copilot for the 50 people who actually run meetings and agents and you land at $54,600 — and Copilot, not Teams, is the line that decides which agents work.

Best for

An ops leader in a Microsoft-first company already on E3, E5 or Business Standard, who needs agents, notetakers and approvals to reach people where they already work, and who wants admin control over which meeting bots get in. The scoped case where it wins: a legal ops or RevOps team that must prove which AI tools recorded which client or customer meetings, using a tenant policy instead of a spreadsheet of vendor contracts.

Not for

A tech company already running on Slack with its agents, support channels and alerts wired in. Moving chat to Teams to save a per-seat line rebuilds every integration and buys little that Copilot cannot already reach. It is also the wrong front door for customer-facing chat now that Live Chat is retired — use a helpdesk such as Zendesk or a Slack-based support tool like Pylon.

Versus the alternatives

• Slack — pick Slack when your agents, approvals and partner channels are built for it and Salesforce is your system of record; its third-party agent ecosystem is broader and older. Pick Teams when identity, files and compliance already live in Microsoft 365 and Purview has to see the agent traffic.
• Zoom Workplace — pick Zoom when meetings with external customers or candidates are the core workload and you want the conferencing layer independent of your productivity suite. Zoom Revenue Accelerator is the revenue-intelligence layer on top.
• Google Workspace (Chat and Meet with Gemini) — the entrant to watch for teams standardizing on Google; pick it when documents live in Drive and you do not want a Microsoft licence chain at all.

Watch-outs

• Facilitator answers are visible to everyone in the meeting, including external and cross-tenant attendees who hold no Copilot licence. Guard: keep the proactive web-search setting off in meeting policies used for client, candidate or deal calls, and enable it only in internal meeting templates. Admins can also block it tenant-wide.
• The bot policy will silently drop your notetaker. If your revenue-intelligence or interview tool is not in the Bot Identification Program, it waits in the lobby or gets denied, and the meeting simply goes unrecorded. Guard: before rollout, ask every recording vendor whether it is registered, test one external and one internal meeting, and restrict admit rights to organizers and co-organizers so attendees cannot wave unverified bots in.
• “Works in Teams” usually means “works with a Copilot licence.” The Teams MCP server and Facilitator’s proactive features both sit behind Microsoft 365 Copilot. Guard: price the agent plan on the Copilot seat count, not the Teams seat count, and get the feature-to-SKU mapping in writing before committing to a timeline.
• Retirements land on Microsoft’s calendar, not yours. Live Chat, Live Events scheduling and Google Calendar sync all ended in 2026. Guard: assign one owner to read the Microsoft 365 message center weekly and log any retirement that touches an ops workflow, with a replacement date.

Related: the enterprise AI rollout stack and the AI agent ops stack cover the governance layers that sit behind Teams.