OFICIAL Atlassian Blog Gadgets · Aug 27, 2026

Put your conversations to work with the Teamwork Graph connector for Microsoft Teams

What happened

Based on Atlassian Blog · Aug 27, 2026

Microsoft and Atlassian launch a Teamwork Graph connector for Microsoft Teams, integrating conversations and meeting transcripts into Rovo’s search and AI tools alongside Jira and Confluence data.

🚩 Report a correction ↗ Open source

Video

Video available

Key points

The work your team delivers rarely starts and ends in one tool.

Plans may live in Confluence and delivery in Jira, while the day-to-day context that shapes those plans and decisions often lives in Microsoft Teams: the quick decisions in chat, the back-and-forth in threads, and the details captured in meeting transcripts.

That creates a familiar problem: you know the information exists, but you do not always remember where it was said, which channel it happened in, or which meeting captured the decision.

By the time you track it down, the moment to act may already be gone.

Microsoft Teams conversations and meeting transcripts will now be searchable within Atlassian’s Rovo platform, alongside existing Jira and Confluence data. The connector aims to reduce time spent locating information by making Teams content part of a unified knowledge base. Enterprise admins can control indexing scope, starting with public channels or recent content to limit noise and exposure during pilot phases. Access remains tied to existing Microsoft Teams permissions, ensuring users only see content they are already authorized to view.

The integration allows users to query across Teams channels, threads, and meeting transcripts using natural language prompts. For example, a project review preparation could begin with a request like, "Summarize the latest updates, decisions, risks, and announcements for Project Titan." Rovo then compiles relevant context from Teams, Jira, and Confluence to provide a grounded starting point for further analysis. This reduces the manual effort of piecing together scattered updates from multiple sources.

Meeting transcripts, including recurring and ad hoc sessions, become searchable within Rovo, enabling teams to reference exact discussions rather than relying on incomplete notes or memory. The connector also supports drafting updates or follow-up actions by leveraging conversation history and meeting context. For instance, users can request, "Draft a weekly status update for the portal security project using context from Teams, Jira, and Confluence." The generated content can then be shared directly in a designated Teams channel.

Enterprise administrators retain granular control over the connector’s deployment, including which Teams and channels are indexed and how broadly the content is made available. The permission-aware approach ensures that connected Teams content respects existing access restrictions, preventing unauthorized exposure. Admins can pilot the connector with specific groups before expanding coverage, while users continue to interact with familiar Teams permissions to determine visibility within Rovo.

Original source → Deals on Clipraptor.com →