Question About Using Jira Cloud as a Knowledge Source for a Microsoft Copilot Agent

[Jaey Kee]

I have Jira Cloud in microsoft 365 copilot, and the Jira Cloud plugin/integration has been enabled by my Microsoft 365 admin.

I have also created a custom Microsoft Copilot Agent and would like to know whether it is possible to use Jira Cloud or Jira directly as the agent's knowledge base.

 Specifically, I would like to understand:

• Does the Jira Cloud plugin/integration support exposing Jira issues as a knowledge source for a custom Microsoft Copilot Agent?

The reason I ask this is because I do see an option to add other data sources (Jira) as knowledge base.

• If this is supported, is there any official documentation or recommended configuration? As I cannot search a jira ticket using this jira data sources.
• If it is not supported, what is the recommended approach for allowing a Microsoft Copilot Agent to retrieve and answer questions based on Jira Cloud data?

[Alexandre Pezzini]

Microsoft provides an official Jira Cloud connector specifically for this purpose.

1. Using Jira Cloud as a Knowledge Base

Microsoft allows developers to use the Jira Cloud connector as a knowledge source in agents built with Copilot Studio, Microsoft 365 Copilot, or the Microsoft 365 Agents Toolkit.

When configured, your custom agent can:

• Index Jira Cloud issues: The connector crawls your Jira instance and indexes issue titles, descriptions, statuses, and metadata.

• Perform Semantic Search: The agent can answer questions based on the indexed Jira data using natural language (e.g., "What are the blockers for the API migration task?").

• Summarize Data: You can ask the agent to summarize specific issues or project statuses based on the Jira data it has indexed.

2. Key Configuration Steps

To use Jira as a knowledge source, your Microsoft 365 admin must first set up the Jira Cloud Graph Connector in the Microsoft 365 Admin Center.

• Authentication: Microsoft recommends using OAuth 2.0. This ensures a secure connection without sharing passwords.

• Permissions: You will need a service account in Jira with "Browse projects" permissions for all projects you wish to index. If you want the agent to respect Jira's security settings (security trimming), the service account also needs "Administer Jira" and "Browse users and groups" permissions.

• Data Freshness: The connector supports both full and incremental crawls to keep the agent's knowledge up to date.

3. Important Limitations

• Cloud Only: This integration only supports Jira Cloud. Jira Server and Jira Data Center are not supported.

• Attachments: Currently, the connector does not index attachments (like PDFs or images) attached to Jira issues. It only indexes the text-based metadata and descriptions.

• Access Control: The agent will only show results to users who have the appropriate permissions in both Microsoft 365 and Jira, provided "security trimming" is enabled during setup.

Verified Documentation

• Jira Cloud connector overview - Microsoft 365 Copilot

• Set up the Jira Cloud connector for Microsoft 365 Copilot

I hope this helps you successfully integrate Jira Cloud into your custom Copilot Agent!