--- title: Connect AI agents to Microsoft Teams slug: microsoft-teams integration: Microsoft Teams category: comms connectionType: mixed status: published publishedAt: "2026-05-06T20:00:00.000Z" lastUpdated: "2026-05-06T19:18:13.234Z" canonical: "https://fidelic.ai/integrations/microsoft-teams" topSearchQueries: - "microsoft teams ai" - "ai in microsoft teams" - "ai for microsoft teams" - "microsoft teams ai integration" - "microsoft teams ai features" - "ai assistant for microsoft teams" - "ai bot for microsoft teams" --- # Fidelic agents in Microsoft Teams *Fidelic agents work where your team already does. They post in Teams channels, book interviews on Outlook calendars, search SharePoint, and file action items in Planner.* ## The connection Fidelic agents connect to [Microsoft Teams](https://www.microsoft.com/microsoft-teams/) through two Microsoft surfaces working together. The Teams Bot Framework gives the agent a presence in your channels and chats — it appears as a member, gets @-mentioned, posts threaded replies. Microsoft Graph gives the agent OAuth-scoped read and write access to the rest of your Microsoft 365 — [Outlook](https://outlook.live.com/) mail and calendar, [SharePoint](https://www.microsoft.com/sharepoint/) sites, OneDrive folders, Planner buckets, Microsoft To Do lists. The agent uses both. The connection lives inside your sandboxed [Anthropic](https://www.anthropic.com/) project — one project key per Fidelic customer. Microsoft Entra sees an app registration for your tenant; Fidelic infrastructure is not in the path between the agent and your Microsoft data. Your Teams admin authorizes the scopes once, and they remain revocable from the Teams admin center. Two distribution paths are available. The Fidelic app is publishable through your tenant's app catalog (admin-approved) or sideloaded via the Teams admin center for a single team while you evaluate. Both paths produce the same agent capability — the difference is who can install it. Most operators sideload first, then promote to the catalog after the trial. ## Permissions requested - Read and post in Teams channels and chats the agent is added to - Read user calendars; create proposed events that the user accepts or declines - Read mail in shared mailboxes the workspace admin explicitly shares - Read SharePoint sites and OneDrive folders the admin shares - Create tasks in Planner buckets and Microsoft To Do lists the agent is added to - Read user profile fields (display name, timezone, manager) used for scheduling decisions Official docs: ## Before you start - Microsoft Teams admin role for app installation (Teams Service Administrator or Global Administrator) - Microsoft 365 license that includes Teams and Microsoft Graph (E3, E5, Business Standard, or higher) - Anthropic enterprise account or Fidelic-managed Anthropic project — provisioned during onboarding - List of Microsoft surfaces the agent should reach (Outlook mail, Calendar, SharePoint sites, OneDrive folders, Planner buckets) — used to scope OAuth grants ## How to connect ### 1. Install the Fidelic app in Teams From the Teams admin center, go to Teams apps → Manage apps. Search for Fidelic, or upload the manifest if your tenant requires sideloading. Click Install. Choose whether to publish to the org-wide catalog or limit to specific teams. The app appears in the Teams chat list once installed. ### 2. Authorize the Microsoft Graph scopes Open the Fidelic app and click Connect Microsoft 365. You'll see the Microsoft consent screen with the scopes listed in the Permissions block above. A Global Administrator or Cloud Application Administrator must grant tenant-wide consent — individual users cannot self-grant for the agent. Once granted, the app shows Connected. ### 3. Add the agent to the channels and inboxes you want it in @-mention the agent in any Teams channel to add it. Share the [SharePoint](https://www.microsoft.com/sharepoint/) sites, OneDrive folders, and Planner buckets the agent should reach — same flow you'd use to add a colleague. The agent picks up the share within minutes. ### 4. Configure the agent's constitution From the Fidelic console, attach the use cases the team needs — recruiter, meeting notes, support escalation, contract review. Each use case has a written constitution and a published list of capabilities and safeguards. Edit the constitution to reflect your team's playbook before going live. ## How you'll know it worked When the wiring is complete you should see four signals: - The Fidelic app appears in your Teams app catalog with a Connected badge. - An @-mention of the agent in a channel returns a reply within a few seconds. - The Microsoft Entra audit log shows the consent grant under the Fidelic app registration with the scopes you authorized. - The agent posts its first useful output within the same day — usually a recap of a recent meeting or a brief drawn from the SharePoint and [Outlook](https://outlook.live.com/) context it can now read. ## Agents that use this connection - [NYRA-01](https://fidelic.ai/agents/nyra) — AI Recruiter Coordinator Candidate scheduling, screening, follow-up - [PRAX-01](https://fidelic.ai/agents/prax) — AI Contract Review Contract redlining against your firm's playbook - [AERA-01](https://fidelic.ai/agents/aera) — AI Agent-Assist Copilot Real-time assist for human support agents - [OMNA-01](https://fidelic.ai/agents/omna) — AI Operations Orchestrator Multi-agent ops coordinator for teams running 3+ agents - [OREN-01](https://fidelic.ai/agents/oren) — AI Research Analyst Weekly market memo - [TANE-01](https://fidelic.ai/agents/tane) — AI Sales Engagement Coordinator Cadence, sequence ops, hand-off discipline - [DRYN-01](https://fidelic.ai/agents/dryn) — AI Data Analyst Recurring analyses, dashboard maintenance, anomaly watch - [VELA-01](https://fidelic.ai/agents/vela) — AI Compliance Analyst Compliance memos ready for your GC ## How they use it | Trigger | Action | Outcome | Agent | | --- | --- | --- | --- | | Hiring manager posts a req in the #hiring channel | NYRA-01 sources candidates, drafts reach-outs, books interviews on the panel's Outlook calendars | Filled interview slots with Teams join links; the manager confirms or reschedules in one click | [NYRA-01](https://fidelic.ai/agents/nyra) | | Teams meeting ends with a recorded transcript | OMNA-01 summarizes the discussion, extracts action items, files them as Planner tasks | Action-item list posted in the channel; tasks assigned and dated in the team's Planner board | [OMNA-01](https://fidelic.ai/agents/omna) | | Deal stage advances in Dynamics 365 or Salesforce | TANE-01 reads the latest activity, drafts the follow-up email and a one-paragraph update | Posts the deal brief in the revops channel; the AE accepts the draft or edits in place | [TANE-01](https://fidelic.ai/agents/tane) | | A new Zendesk or Intercom ticket comes in flagged urgent | AERA-01 pulls customer history, drafts a reply, escalates the thread to the support channel | Support engineer opens Teams to a thread with the draft, the customer history, and the recommended next step | [AERA-01](https://fidelic.ai/agents/aera) | | A new contract lands in the SharePoint legal-review folder | PRAX-01 reviews against your written playbook, drafts a redline, marks the deviations | Posts a summary in the legal channel with a link to the marked-up file in SharePoint | [PRAX-01](https://fidelic.ai/agents/prax) | | A competitor files an SEC document, ships a product, or makes a senior hire | OREN-01 drafts a one-page brief — what changed, what it implies, what to watch next | Posts in the strategy channel with the original source linked | [OREN-01](https://fidelic.ai/agents/oren) | | Someone @-mentions the agent in a channel asking a policy or product question | DRYN-01 searches the SharePoint and OneDrive content the agent is allowed to read | Posts a sourced answer with the page link; logs unanswered questions for the team to triage | [DRYN-01](https://fidelic.ai/agents/dryn) | ## Connection limits The agent can only see what your Microsoft admin has shared. The OAuth scopes are scoped per-resource — adding a [SharePoint](https://www.microsoft.com/sharepoint/) site, a Planner bucket, or a shared mailbox is a permissions change in the Microsoft 365 admin center, not a contract change. The Fidelic agents in Teams currently do not: - Run inside Microsoft GCC High or DoD tenants. We support commercial and GCC; GCC High is out of scope today. - Replace Microsoft Copilot inside Word, Excel, or PowerPoint. Copilot is good at the in-document task you start from inside the file. Fidelic agents work the stream — channels, calendars, mailboxes, files — and write the result back where the team reads. - Send Teams messages on behalf of a specific human user. The agent posts as itself; impersonation is out. - Modify your tenant's conditional-access or app-deployment policies. Those stay under your Teams admin's control. ## Where the data goes The Microsoft connection runs inside your sandboxed [Anthropic](https://www.anthropic.com/) project. The OAuth credentials are stored on [Anthropic](https://www.anthropic.com/)'s infrastructure under your project key, never on Fidelic systems. When the agent reads a Teams message, an [Outlook](https://outlook.live.com/) email, or a [SharePoint](https://www.microsoft.com/sharepoint/) file, the content passes from Microsoft through your [Anthropic](https://www.anthropic.com/) project to the model, and the model's output goes back to Teams or to the file — never to a Fidelic-operated database. Fidelic operates the agent template; we don't run an intermediate store that holds your Microsoft data. --- Canonical: https://fidelic.ai/integrations/microsoft-teams