Connect Jira to Microsoft 365 Copilot
What Jira and Microsoft 365 Copilot document about their connection: what it does, what it takes to turn it on, what it costs and the data that passes from one to the other. Each fact with its source at the vendor and its date.
What the connection does
- What it does. The Jira Cloud integration indexes Jira Cloud issues so they can be searched in Microsoft 365 experiences, including Microsoft 365 Copilot and Microsoft Search (according to Microsoft's documentation, read on 10/16/2026).
- The direction. From Jira to Microsoft 365 Copilot.
- The mode. Through an integration offered by the vendor.
What it takes to turn it on
- The editions or licenses required. The tenant must have Microsoft 365 licenses; the surfaces offered to users (Microsoft Search, Microsoft 365 Copilot grounding, Copilot Chat agents) depend on the organization's licensing (according to Microsoft's documentation, read on 10/16/2026).
- What it costs on top, or how it is billed. Indexing the data of a synced integration incurs no extra cost for tenants with Microsoft 365 licenses (according to Microsoft's documentation, read on 10/16/2026).
- Who turns it on. An administrator adds the Jira Cloud integration from the gallery, in the Copilot menu of the Microsoft 365 admin center (according to Microsoft's documentation, read on 10/16/2026).
- The prerequisites. Two statements from the vendor, below.
The data that flows
- What passes. Jira Cloud issues and their metadata are indexed, including: title, description, status, project name, created and updated dates, assignee name, priority (according to Microsoft's documentation, read on 10/16/2026).
- Whether the source tool's permissions are respected. Two search permission modes: all users, or only the people who have access in Jira (according to Microsoft's documentation, read on 10/16/2026).
- Where the data is processed. Data that enters the Microsoft cloud through the Copilot integrations platform is stored in the region where the Microsoft 365 tenant is located (according to Microsoft's documentation, read on 10/16/2026).
- Training. Prompts, responses and data accessed through Microsoft Graph are not used to train foundation large language models, including those used by Microsoft Copilot (according to Microsoft's documentation, read on 10/16/2026).
- Retention. Content is retained according to the general Microsoft 365 data retention period (according to Microsoft's documentation, read on 10/16/2026).
Two statements from the vendor
- The prerequisites. According to Microsoft's documentation, read on 10/16/2026: “You must be the search admin for your organization's Microsoft 365 tenant.”
- The prerequisites. According to Microsoft's documentation, read on 10/16/2026: “you must be an AI administrator in the Microsoft 365 admin center.”
With Ojja
Ojja tells you whether you already pay for both tools, whether the connection is turned on in your company, who uses it, and the usage before and after: it is the “Connect” lever of what your tools can already do.
What Ojja never does
- Ojja does not advise you to choose a vendor: it records what each one documents.
- Ojja does not say whether a use is permitted: it gives the facts, and the points to review with your counsel.
Ojja does not provide legal advice: it records and documents; how the law applies to your situation is for your counsel to determine.
Checked on 10/16/2026. When a vendor says nothing, the page says “not documented by the vendor”.