Jira AI context from Microsoft 365: Why Teams and Outlook matter

A Jira ticket tells you what needs to be done, who’s responsible, and where things stand. But does it tell you why a decision was made? Probably not the whole story. That might be hiding in a Microsoft Teams chat, an Outlook email, or a meeting nobody thought to document.

At Atlassian Team Europe in Amsterdam, Robert Hean sat down with Andy, co-founder and CEO of yasoon, to discuss why this missing context matters, especially for AI. Their conversation also explored Atlassian Rovo, automation, the future of Jira and Confluence, and the evolving relationship between Jira Service Management and Customer Service Management.

Why Jira tickets don’t tell the whole story

Jira is good at managing structured work. But the actual discussions? Those tend to happen elsewhere. Imagine an IT incident: the ticket documents the problem and resolution, while the team debates solutions in Teams. Two weeks later, someone takes over the ticket and wonders why a particular approach was chosen. Good luck finding that decision in a three-week-old chat.

At yasoon, we’ve been connecting Microsoft and Atlassian tools since 2012. Our Atlassian Marketplace app, Microsoft 365 for Jira, makes it possible to link Teams conversations, Outlook emails, and meetings to Jira work items. The idea isn’t to bring every conversation into Jira, but to make relevant communication accessible in the context of the work it relates to. This helps teams understand not only what was done, but also the discussions and decisions behind it.

Why AI needs the right context from Microsoft 365

Here’s where Jira AI context from Microsoft 365 gets interesting. Atlassian Rovo can search for information, summarize work, and help people take action. Connecting relevant Teams chats, emails, and meetings creates a better foundation for summaries, handovers, and AI-assisted workflows.

Of course, more context isn’t automatically better context. Nobody needs an AI agent enthusiastically reading every Teams conversation from the past five years. The challenge is identifying what matters for a particular task while respecting permissions. Andy sees Rovo for Microsoft 365 and specialized integrations as complementary approaches to solving that problem. For organizations already managing projects across both ecosystems, connecting Jira and Microsoft 365 is a practical starting point.

What’s next for Jira, Confluence, AI, and intergations?

Robert and Andy also explored Atlassian’s broader direction. With Rovo and automation becoming more important, Andy expects organizations to combine existing capabilities into tailored workflows rather than build everything themselves. AI might make writing code easier, but maintaining integrations, permissions, and compatibility? That’s still real work.

Then there’s Jira and Confluence. As AI brings structured work and knowledge closer together, Andy wondered whether the two products might eventually become one. Jirafluence, anyone? Of course, that’s speculation. But who knows, maybe we’ll all be using Jirafluence one day.

Why the JSM and CSM split raises questions

Another question was Atlassian’s distinction between Jira Service Management and Customer Service Management. Andy questioned whether internal and external service management can really be separated so neatly. After all, many organizations handle requests from employees, partners, and customers through remarkably similar processes.

For service teams, the practical question is how well requests, communication, and workflows connect across these audiences. That’s also why Jira Service Management with Microsoft 365 focuses on keeping service communication connected, regardless of where the conversation starts.

Connecting Jira, Microsoft 365, and AI

The conversation ultimately returned to a familiar problem: organizations already have plenty of tools. What they often lack is a reliable connection between them. Jira provides structure, Microsoft 365 handles everyday communication, and AI can help make sense of the information.

The real opportunity for Jira AI context from Microsoft 365 isn’t giving AI access to everything. It’s making the right context available for the right work, without losing control along the way. Not quite as catchy as Jirafluence, perhaps, but probably more useful.

A big thank you to Robert Hean for the great conversation and for everything he does for the Atlassian community! From his legendary Team Swag Giveaways to sharing knowledge through courses at Hean.Tech, Robert puts a lot of energy into bringing the community together and helping others learn. Keep up the great work, Robert!