How to Connect Jira Cloud to Microsoft 365 Copilot: A Step-by-Step Guide

A beginner-friendly, permission-aware walkthrough for preparing Jira, adding the Microsoft 365 connector, testing one project, and troubleshooting common issues.

By Gowtham Rajamanickam · Updated September 11, 2026

What this article covers: The Microsoft 365 Copilot Jira Cloud connector uses OAuth and indexing for permission-aware search. An optional Copilot Studio agent flow can use the Jira Power Platform connector and an Atlassian API token for live actions. These are two different connection patterns.

Understand the two connection paths

Choose the path that matches the job you want to perform. The Microsoft 365 connector is intended for discovery and Copilot search. The optional flow is useful when an agent must call a Jira operation at run time.

Use case	Connection	Credential	What happens
Microsoft 365 Copilot and Microsoft Search	Jira Cloud connector in the Microsoft 365 admin center	Standard OAuth	Microsoft authorizes the prepared Jira account, crawls selected content and applies source permissions.
Copilot Studio agent action	Jira connector in Power Platform or an Agent Flow	Atlassian API token + email	The flow calls Jira REST-backed actions such as `Get issue by key (V2)` when the agent runs.

Do not mix the credentials. An API token is not entered into the Microsoft 365 connector when you select standard OAuth. It is used only by the separate Power Platform/Jira connection shown later.

Prerequisites checklist

Jira Cloud site URL, for example https://your-site.atlassian.net.
Jira administration help for project permissions, issue security and profile visibility.
Microsoft 365 administrator access to Copilot connectors.
A small pilot project and at least two test users with deliberately different access.
A test issue whose key and expected visibility are written down before indexing.
Agreement on whether results must be restricted to existing Jira permissions.
Network allowlists and REST/API access checked by the Jira administrator.
A secure place for any API token used by the optional agent flow. Never place a token in a blog post, screenshot or prompt.

Microsoft’s current product requirements are described in the Jira Cloud deployment guide and the administrator setup guide.

Prepare Jira Cloud

Step 1 Record the site address

Copy only the Jira site root, such as https://grajamanickam2024.atlassian.net.
Do not append /browse/SCRUM-7, /rest/api or a project path.
Confirm the site opens over HTTPS from the network used by Microsoft services.

Figure 1. Jira space access settings show the current members and their roles. Use the browser address to identify the Jira site root.

Step 2 Prepare the connector account

Use a dedicated, named Jira account rather than a personal administrator account.
Create a separate Jira account to use for the Jira connector.
Ask your Jira administrator to give this account access to the projects and tickets you want to include.
If you want the connector to read all projects, make sure this account can view every required project.
If some tickets have restricted access, ask the administrator to allow this account to view them as well.
Sign in with this account when setting up the Jira connector.

Figure 2. Review the members listed under Access and confirm that the connector account can access the required Jira space or project.

Figure 3. The Atlassian Administration Users page lists account status and app access. Confirm that the dedicated connector account is active.

Permission detail: Grant Browse projects for the content being indexed and issue-security access where needed. Microsoft also lists Browse users and groups and Administer Jira for source-permission search. Ask the Jira administrator to review these requirements and the account’s email visibility. Microsoft: required Jira permissions.

Step 3 Check API and network controls

Ask the Jira administrator to confirm that REST/API access is enabled.
Review outbound allowlists, proxy rules and conditional access policies.
Check whether Atlassian managed accounts restrict profile or email visibility.
Record any restriction before troubleshooting the connector; otherwise a permission issue can look like an indexing failure.

Choose a project and test users

Use a small, repeatable test plan before selecting many projects.

Choose one non-production project. In this walkthrough the project key is SCRUM and the project is “Gowtham’s Agile Team.”
Choose one harmless issue, such as SCRUM-7, and record its title, status and expected audience.
Nominate an authorized user who can browse the project and open the issue.
Nominate a restricted user who cannot browse the project or cannot see the protected issue.
Write down the expected result for each user before running Copilot tests.

Test identity	Jira expectation	Copilot expectation
Authorized user	Can open SCRUM-7 in Jira	Can discover the issue and open the source link
Restricted user	Cannot open the issue or project	Issue should not be disclosed in results

Figure 4. Invite a user to the Atlassian organization and select the required app access and groups for the connector account.

Configure the Microsoft 365 connector

Step 4 Open the Jira Cloud connector

Sign in to the Microsoft 365 admin center.
Open Copilot, then Connectors and Gallery.
Search for Jira and select the Jira Cloud connector.
Enter a clear display name, such as SCRUM pilot – Jira Cloud.
Enter the Jira site root, not an issue URL.

Accept only after confirming that the site and account are correct.

Figure 5. Open the Microsoft 365 admin center to begin configuring a Copilot connector.

Select Connectors

Figure 6. The Connectors page lists existing connections and provides access to the connector gallery.

Go to Jira Cloud Connector

Figure 7. Open the Gallery tab to browse the available Microsoft 365 Copilot connectors.

Select Jira Cloud

Figure 8. Search for Jira and select the Jira Cloud connector that matches the cloud-hosted source.

Enter the details

Figure 9. The Jira connector setup panel contains the display name, Jira instance URL, authentication type and rollout settings.

Authorize

Step 5 Choose an authentication method

Which authentication applies? The Microsoft 365 Jira Cloud connector supports standard OAuth or customized Atlassian OAuth 2.0. The API-token instructions are retained under Step 9 for the separate Power Platform Jira connection. Microsoft authentication guidance.

Select one of the following methods to connect to Jira.

Option 1: Authorize using OAuth 2.0

Choose OAuth 2.0 (Recommended) when available.
Select Authorize.
Sign in to Atlassian using the dedicated Jira connector account.
Review the requested permissions and confirm that the correct Jira site is selected.
Select Accept to grant access and return to the connector setup.

Figure 10. Enter the Jira site URL and select Authorize to start the OAuth sign-in process.

Accept the handshake

Figure 11. Atlassian displays the Microsoft 365 connector consent request. Check the Jira site and permissions before selecting Accept.

Successfully Authorized

Figure 12. The connector setup panel confirms successful authorization. Review the remaining settings before creating the connection.

Create

Understand the OAuth handshake

Microsoft displays the Jira authorization page.
You authenticate to Atlassian as the connector account.
Atlassian asks you to approve the requested access.
Atlassian returns an authorization result to Microsoft.
Microsoft stores the connection securely and uses it for crawling.
The connector account is the Jira identity used to read source content; it is not automatically the identity of every Copilot user.
When source permissions are enabled, Microsoft uses identity matching to avoid showing content a user cannot access in Jira.

Use the Atlassian OAuth documentation for OAuth concepts and Microsoft’s Jira administrator guide for connector-specific settings.

Step 6 Choose content, permissions and pilot users

Open Custom setup and select the Jira projects to index for the pilot.
Choose Only people with access to this data source when results must respect Jira permissions.
Check that Jira email identities match Microsoft Entra identities, or configure the appropriate mapping.
Use Rollout to limited audience to select the pilot users or groups.

Reference: Microsoft: Jira Cloud deployment and custom setup.

Step 7 Create the connection and check indexing

Review the settings and select Create.
Open the connection details and check the crawl status before testing search.
Allow the initial crawl to finish. Group permission changes are processed during full crawls, so allow for this when testing access changes.

Figure 13. Connection creation is in progress. The setup screen reports the connection and crawl stages.

Figure 14. Open the connector details panel to review its status, indexed item counts and available configuration information.

Step 8 Test from Microsoft 365 Copilot

Start with a precise prompt that names the issue key and asks for a source link:

Find Jira issue SCRUM-7 in the SCRUM project. Summarize its title, description, status and source link. If you cannot access it, say so.

Open the cited Jira link and compare the response with the source.
Ask the same question as the authorized user and restricted user.
Change a harmless test description, wait for synchronization and repeat the query.
Record the time, user, prompt and observed result.

Check	Pass condition	If it fails
Connection	Connector status is healthy	Review OAuth account and Jira permissions
Content	Authorized user finds SCRUM-7	Check project selection, crawl status and issue security
ACL	Restricted user cannot discover the issue	Review identity mapping and source permission settings
Freshness	Harmless edit appears after synchronization	Wait for the next crawl and inspect connector activity

Optional: build a Copilot Studio agent flow

This section is separate from the Microsoft 365 connector. Use it when an agent must call Jira directly.

Working pattern: When an agent calls the flow → Get issue by key (V2) → Respond to the agent.

Before using the optional flow: Microsoft lists the Jira connector as Premium for Power Apps, Power Automate and Copilot Studio. Confirm the applicable entitlement for your environment. Microsoft: Jira connector reference.

Step 9 Create the API-token connection

Option 2: Connect using an API token

Choose API Token when available.
Sign in to Atlassian using the dedicated Jira connector account.
Open the account’s Security → API tokens settings and create an API token.
Copy the generated token and return to the connector setup.
Enter the connector account’s email address and paste the API token into the corresponding fields.
Confirm that the Jira site URL is correct, then use the available connection button to continue.

Note: API token authentication uses the account’s email address and token. It does not use the OAuth permission approval screen.guide for connector-specific settings.

Figure 15. Open Atlassian Account → Security → API tokens to create a token for the separate Power Platform Jira connection.

Figure 16. The API tokens page offers token creation options. Use the token type supported by the connector you are configuring.

Figure 17. Enter a descriptive token name and expiration date in the Create an API token dialog.

Figure 18. Copy the newly generated API token and store it securely. The token value is masked in this screenshot.

Figure 19. The Power Apps Jira connection dialog requests a connection name, API-token authentication, account email, token and Jira instance.

Open Power Apps or Copilot Studio and add the Jira connector.
Choose API Token as the authentication type.
Enter the Atlassian account email used to create the token.
Paste the token once, then store it in the connection; do not paste it into an instruction.
Enter the Jira site root, for example https://grajamanickam2024.atlassian.net.
Create the connection and select the newer action version when the designer offers it.

Field	Value for this example	Safety note
Connection name	`Jira-Connectors`	Use a descriptive name
Authentication type	`API Token`	This is for the Power Platform action, not standard OAuth
Username or Email	Your Atlassian account email	Do not publish it in screenshots
API token	Token generated in Atlassian security settings	Secret; rotate if exposed
Jira instance	`https://grajamanickam2024.atlassian.net`	Use HTTPS and the site root

configure this

Figure 20. The agent flow designer shows a Jira action with a new-connection form. Complete the connection before configuring the action.

Get issue by Steps

Figure 21. The Get issue by key action displays API Token as the authentication type for its Jira connection.

Step 10 Optional: build a Copilot Studio agent flow

Figure 22. Complete the Jira connection fields in the agent flow designer using the dedicated account and its token.

Figure 23. Enter a known Jira issue key in the action input to retrieve a specific ticket.

Flow order: Some screenshots show the response step above the Jira action while the flow is being edited. Before publishing, place the Jira lookup before Respond to the agent, then return the required fields from the lookup. Use the supported action version offered in your environment.

Step 11 Test the flow

Use a known key such as SCRUM-7 in the action input.
Run the flow and confirm a successful status.
Inspect the returned key, summary, status and link.
Map only the fields needed by the agent’s response.
If the action says “Please use the new version,” replace the old action with Get issue by key (V2) and recreate the connection if necessary.

Get Issue By Key

Figure 24. The completed Jira connection form is ready for Create new. Keep credentials in the connection settings.

Step 12 Results

Figure 25. The run details show a successful Get issue by key (V2) action and its returned JSON. Compare the response with the source Jira issue.

Troubleshooting

“Sorry, I can’t respond” in Prompt Builder: Verify that the flow is published, the agent has access to it and the response step is connected.
“Please use new version of Action”: Remove the legacy action and add the V2 Jira action with a current connection.
“Invalid parameters”: Check the issue key format, use a real key such as SCRUM-7, and select the correct Jira instance.
Projects returned but an issue is missing: Inspect issue security, project permissions, selected content and crawl completion.
Authorized user sees nothing: Compare the Jira email with the Microsoft Entra sign-in identity and review custom mapping.
Restricted user sees too much: Stop the rollout and review source-permission settings before adding more data.
OAuth authorization fails: Confirm the site URL, connector account, network allowlist and required Jira permissions.
API-token call fails: Verify the token has not expired or been revoked, and create a new connection instead of exposing the token again.

For connector-specific diagnostics, see Microsoft’s Jira Cloud troubleshooting guide.