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.
The Teamwork Graph connector for Microsoft Teams helps close that gap. Once connected, Teams conversations and meeting context become part of the broader knowledge available to Rovo Search, Chat, and Agents, right alongside your Atlassian work in Jira and Confluence. Find what matters, understand it faster, and use it to move work forward. Results respect each user’s channel, chat, and meeting permissions. For example, transcripts are restricted to users who were invited to the meeting and the meeting chat.
Try asking Rovo:
- “Summarize the latest decisions and action items from the Project Titan Teams channel.”
- “Who raised the concern about the migration timeline in Teams last month?”
- “Find the discussion about API deprecation in our engineering standup recording.”
Start with the outcome, not the channel
People should not need to remember which channel, thread, or meeting contains the answer before they can ask the question.
Imagine you are preparing for a project review. Instead of opening Teams, scanning chat history, and piecing together scattered updates manually, you can start with the outcome you need.
“I’m preparing for a Project Titan review. Summarize the latest updates, decisions, risks, and announcements. Link me to the supporting threads.”
Rovo can use connected Teams context together with Jira and Confluence to give you a grounded starting point. You still apply judgment, but you get to that judgment much faster.
Three examples where Teamwork Graph helps you find, understand, and use Teams knowledge
1. Find the right conversation faster
Sometimes the hardest part is not understanding the answer. It is finding the right discussion in the first place.
With the Microsoft Teams connector, you can search across channels, threads, and message history by topic, contributor, time range, and context. That means you can ask naturally instead of relying on memory.
“Who raised the risk about the Inconsistent MFA behavior / login failures?”
“Recent Teams announcements about the Customer Portal Data Security Pilot.”
That is especially helpful when a team moves quickly and important information gets buried under new messages.
2. Catch up without reading every thread
Messaging is great for moving quickly, but catching up can be painful. A busy channel can easily turn into hundreds of messages and nested replies.
Rovo helps by summarizing what actually matters: updates, decisions, unresolved questions, and action items.
“Summarize the latest updates, decisions, and action items from the Titan Working Group Teams channel.”
This is not just useful for people returning from time away. It also helps leaders, partners, and cross-functional teammates stay aligned without living in every channel every day.
3. Search meeting transcripts, not just chat
Some of the most valuable context lives in meetings, where decisions are made and details captured in transcripts.
The Microsoft Teams connector makes meeting transcripts searchable too, including recurring meetings and ad hoc conversations. That means teams can go back to what was actually said instead of relying on memory or incomplete notes in various individuals’ private folders.
“Summarize the customer escalation points from the most recent Sales Strategy Review Weekly meeting.”
4. Turn conversation context into action
Once Teams context is connected, it can help power the next step in your workflow. You can use conversation history and meeting context to draft updates, prepare reviews, or help an agent take follow-up action with better grounding.
Spend less time collecting context and more time making progress.
“Draft a weekly status update for the portal security project using context from Teams, Jira, and Confluence. Send it to the #proj-portal-security Teams channel.”
Why connected context matters
| Approach | Status | Good at | Where teams still get stuck |
|---|---|---|---|
| Microsoft Teams alone | Works well on its own | Fast communication, meetings, and collaboration | Important decisions can stay buried in thread history or recordings |
| Atlassian apps alone | Works well on its own | System of record, documentation, and delivery tracking | Alignment may happen in informal contexts elsewhere |
| Manual copy-and-paste | Works sometimes | Works for urgent one-off needs | Slow, hard to scale, and easy to lose context |
| Connected experience powered by Teamwork Graph with Microsoft Teams context | Ideal State | Brings conversations, meetings, plans, and teamwork context together in one experience | Teams need the Teams Connector enabled and Teams licenses active for seamless access |
What the connector makes available
The Microsoft Teams connector expands the context available to Rovo with the conversations and collaboration history your teams already rely on every day.
| Atlassian experience | How connected Teams context helps |
|---|---|
| Rovo Search | Discover Teams messages, announcements, channels, and meeting discussions alongside Atlassian knowledge |
| Rovo Chat | Ask questions and get grounded answers based on Teams conversations and transcripts you already have access to |
| Rovo Agents | Use Teams context as input for repeatable workflows, summaries, and follow-up actions |
Admin controls that help teams connect with confidence
Connecting more knowledge should not mean giving up control. Enterprise admins can decide what gets indexed, where they want to start, and how broadly they want the connector to reach.
Admins can tailor the rollout to their organization: start with indexing public channels only, focus on recent content to focus on active work, and choose the Teams and channels that matter most. These controls help reduce noise, limit exposure, pilot with selected groups, and expand coverage as teams build confidence.
| Control | What it does |
|---|---|
| Block ingestion of all DMs | Excludes direct messages from being indexed, so organizations can start with shared collaboration spaces while keeping more sensitive one-to-one communication out of scope. |
| Block ingestion of all private channels | Excludes private channels from being indexed, helping admins reduce risk and evaluate value first using lower-sensitivity shared content. |
| Time-based ingestion | Only indexes content created or modified after an admin-selected date, helping teams focus on current knowledge and avoid years of historical noise. |
| Allowlist or blocklist channels | Includes or excludes specific Teams channels in indexing, giving teams precise control over which conversations are available to Rovo. |
| Allowlist or blocklist Teams | Includes or excludes entire Teams workspaces in indexing, making it easier to pilot with selected departments or keep sensitive areas out of scope. |
Permissions stay aligned with Microsoft Teams
Connected content still respects source-system permissions. People only see Teams messages, channels, and meeting content they already have permission to access in Microsoft Teams.
This permission-aware approach helps organizations connect valuable context without creating a new access model. Admins can control what is ingested, while each user’s existing Teams access continues to determine what Rovo can show them.
Useful in your everyday work
- Project leads can catch up on channel activity before a review.
- Engineering teams can find the thread where a technical decision was made.
- Customer-facing teams can revisit meeting discussions before the next conversation.
- New team members can understand the context behind active work faster.
Get started
Connect Teams to Teamwork Graph from Atlassian Administration (make sure to enable Transcripts!), then try one high-value workflow:
- Connect Teams and confirm the objects and fields you want indexed.
- Ask Rovo to prepare you for your next weekly sync, based on last week.
- Review the result, and share it with your team.
