Devin ships native Microsoft Teams mentions and Microsoft 365 connectors
Cognition has broadened Devin with native Microsoft Teams @ mentions and first-party Microsoft 365 connectors that the company ties to MCP servers. Engineers can @ mention Devin inside Teams, and a separate integration is meant to connect the agent to mail, calendar, files, tasks, chats, and directory data across a typical M365 tenant. Cognition says both capabilities are available now to all Devin customers, which positions the coding agent inside everyday collaboration surfaces rather than only standalone developer environments. For enterprises that standardize on Teams and Microsoft 365, first-party hooks can matter as much as model quality when procurement and security teams evaluate agent tools. The public record here is Cognition’s announcement on the Windsurf blog; the packet does not spell out tenant admin steps, licensing changes, data-handling guarantees, or third-party verification of the rollout.
Devin ships native Microsoft Teams mentions and Microsoft 365 connectors
Cognition says engineers can @ mention Devin in Microsoft Teams and connect Devin to mail, calendar, files, tasks, chats, and directory via first-party Microsoft 365 MCP servers. The company states both integrations are available now to all Devin customers.
Key takeaway
Devin now targets Microsoft-centric workflows with native Teams mentions and M365 connectors rather than requiring bespoke integration work.
What happened
Cognition announced that Devin supports native @ mentions in Microsoft Teams, allowing engineers to invoke the agent directly within Teams conversations according to the company’s Windsurf blog post.
The same announcement describes first-party Microsoft 365 integration via MCP servers linking Devin to mail, calendar, files, tasks, chats, and directory, and Cognition states both integrations are available now to all Devin customers.
Evidence
Engineers can @ mention Devin in Microsoft Teams.
Windsurf Blog · attributed
Native support to @ mention Devin in Microsoft Teams
Microsoft 365 connectivity uses first-party MCP servers across mail, calendar, files, tasks, chats, and directory.
Windsurf Blog · attributed
connect Devin to mail, calendar, files, tasks, chats, and directory via first-party Microsoft 365 MCP servers
Both Teams mentions and M365 connectors are live for all Devin customers.
Windsurf Blog · attributed
The company states both integrations are available now to all Devin customers.
Why it matters
Embedding Devin in Teams and M365 may shift evaluation criteria toward suite-native access, permissions, and IT approval paths inside Microsoft tenants.
Limits and uncertainties
The packet relies on Cognition’s self-reported availability claim and does not document admin consent steps, security reviews, or non-customer validation.
Practical implications
Teams- and M365-based engineering orgs can pilot Devin where work already lives, but should confirm tenant policy, connector scope, and MCP server permissions before production use.
What to watch
Whether Cognition publishes admin setup guides, entitlement requirements, or customer case studies beyond the initial Windsurf blog announcement.
