Cognition Embeds Devin Into Microsoft Teams for 90% of Fortune 500

Cognition has expanded Devin, its autonomous coding agent, across Microsoft’s collaboration stack. According to Cognition’s release notes, Devin now handles direct messages and group chats in Microsoft Teams and connects to Microsoft 365 through Model Context Protocol servers built and hosted by Cognition.

Microsoft Teams already carries bug reports, product specifications, alerts, and engineering discussions for many companies. Over 90% of Fortune 500 companies use Microsoft Teams, giving Devin a way to start and coordinate coding tasks where those requests originate.

Devin enters the Teams thread

Devin has worked in Teams channels since last year, and the updated app broadens that integration to direct messages and group chats. Sending Devin a message starts a session, with subsequent questions, approvals, and results appearing in the same conversation.

• Channel triggers: Devin can monitor a channel and begin work when a bug report, alert, or request arrives.
• Interactive requests: Devin can send a card when it needs clarification, approval, or authentication for an MCP server.
• Chat controls: The agent can mention people, attach files, and mute itself within a conversation.

Mentions let Devin route a missing specification or unresolved question to the relevant person. Cards keep approvals and sign-ins structured, while muting limits unnecessary notifications after a task ends.

One prompt across six services

Cognition built and hosts six Microsoft 365 MCP servers in Devin’s MCP Marketplace. Model Context Protocol, an open standard introduced by Anthropic, gives AI agents a common interface for retrieving data and invoking external tools.

• Outlook: Email and contacts
• Calendar: Events and scheduling
• OneDrive and SharePoint: Files, documents, and sites
• Microsoft To Do: Tasks and follow-up items
• Teams: Messages and conversations
• Microsoft Entra ID: Directory lookups

A single instruction can ask Devin to read a SharePoint design document and an Outlook thread, modify code, open a pull request, schedule a review, and add follow-up items to Microsoft To Do. The Microsoft connectors supply documents, messages, directory data, and productivity actions; Devin’s existing repository access handles code changes and pull requests.

The Teams app provides the conversational interface, and the MCP connections provide optional access to Microsoft 365 data. Organizations can deploy the chat integration without granting Devin access to email, files, calendars, or other connected services.

Access stays scoped to each user

• Teams permissions: Installing the updated Teams app grants no access to Microsoft 365 email, files, or calendars and requests no additional permissions compared with the previous app.
• User identity: Each MCP connection uses delegated, per-user permissions. Devin operates as the signed-in user and receives no application-level permissions.
• Separate consent: Each of the six connections has its own consent screen. Read-only access is the minimum, and optional write scopes can be cleared during setup.
• Tenant controls: Organizations that restrict user consent can require administrator approval. Some broader directory scopes always require admin consent.
• App ownership: Administrators can register their own Microsoft Entra application instead of using Cognition’s hosted application.

Delegated access limits Devin to resources the signed-in user can already reach and to actions allowed by the approved scopes. Teams can therefore enable write access only for workflows that require actions such as sending messages, changing calendar events, or updating task lists.

From discussion to pull request

A coding agent needs project context to complete multi-step engineering work. Access to the relevant design document, email thread, directory, and meeting schedule reduces the manual copying developers would otherwise perform before asking the agent to change code.

The additional context also expands the operational surface that teams must manage. Organizations need to decide which channels can trigger work, which connectors receive write access, and where human review remains mandatory for code, messages, tasks, and calendar changes.

GitHub Copilot, Cursor, and other coding-tool vendors are also connecting assistants to the documents, conversations, tickets, and repositories that hold project decisions. Cognition’s release targets Microsoft-centric organizations by placing task initiation and supervision inside systems they already administer.

How teams switch it on

Cognition says both integrations are available now to all Devin customers. Teams deployment starts through the Microsoft Marketplace, while the Microsoft 365 connectors are installed separately from Devin’s MCP Marketplace.

1. A Teams administrator installs the Devin app.
2. A Devin administrator enables the integration for the organization.
3. Individual users link their Microsoft and Devin accounts.
4. Users add the required Microsoft 365 connectors and approve their requested scopes.

Cognition’s integration documentation provides the complete setup process and permission breakdown.