Skip to main content

Integration with Microsoft Teams

Microsoft Teams integrations overview

Currently, the following Atlassian products can be integrated with Microsoft Teams:
  • Jira Cloud, Jira Data Center, and Jira Server
  • Bitbucket Cloud
  • Confluence Cloud
  • Trello

Microsoft Teams versions

There are 4 versions of the Microsoft Teams application:

As of now, integrations are supported for online, freemium, and desktop.

Marketplace apps

Marketplace application
Developer
Atlassian product supported
Microsoft Teams for Jira
Atlassian
Jira Cloud, Data Center, Server
Advanced Microsoft Teams Jira Connector
Move Work Forward
Jira Cloud, Data Center, Server
Advanced Microsoft Teams Confluence Connector
Move Work Forward
Confluence Cloud, Data Center, Server

To see what functionality each of the apps provide, click on the links above to access their descriptions.

Microsoft Teams for Jira is the app officially supported by Atlassian.

Prerequisites for using the integration

The following information and/or configuration instructions are provided as-is. Please consult your Microsoft 365 admin team for further advice.

Prerequisites to start using Microsoft Teams integrations are:
  • Microsoft 365 with a Business or Enterprise plan (an IT admin needs to have already enabled Microsoft Teams in Microsoft 365)
  • Allow third-party apps in the Microsoft Teams admin center 
    • This is accessed via Teams Apps -> Permission Policies -> Allow All Apps
    • Please bear in mind that third-party apps need to be enabled in the org-wide app settings
    • See below for detailed instructions
Org-wide app settings govern the behavior of all users and override any other app permission policies assigned to users. Please perform the following steps if you need to enable third-party apps:
  1. In the left navigation of the Microsoft Teams admin center, go to Teams apps -> Permission policies.
  2. Select Org-wide settings. You can then configure the settings you want in the panel.
    Integration with Microsoft Teams 1
  3. Under Third-party apps, turn on these settings to control access to third-party apps:
    1. Allow third party or custom apps
    2. Allow any new third party apps published to the store by default
  4. Under Custom apps, turn on Allow interaction with custom apps. This setting controls whether users can interact with custom (side-loaded) apps. Keep in mind that this is different from allowing users to upload custom apps.
  5. Click Save for org-wide app settings to take effect.
In order to manage or create a custom app permission policy, proceed with the steps below:

It's important to know that after you create a custom policy, you can't change it if third-party apps are disabled in org-wide settings.

  1. In the left navigation of the Microsoft Teams admin center, go to Teams apps -> Permission policies.
  2. Click Add. 
    Integration with Microsoft Teams 2
  3. Enter a name and description for the policy.
  4. Under Microsoft apps, Third-party apps, and Tenant apps, select one of the following:
    1. Allow all apps
    2. Allow specific apps and block all others
  5. If you selected Allow specific apps and block others, add the apps that you want to allow:
    1. Select Allow apps
    2. Search for the apps that you want to allow, and then click Add. The search results are filtered by the app publisher.
    3. When you've chosen all the apps, click Allow.
  6. Click Save.
In order to get acquainted with other processes (e.g. how to edit or assign a custom app permission policy), follow this link: Manage app permission policies in Microsoft Teams.

Integration with Microsoft Teams for Jira

The following information and/or configuration instructions are provided as-is. Please consult your Microsoft 365 admin team for further advice.

There may be a need to enable Jira Server in the list of apps, but it may also be enabled automatically or by default.
In order to enable it in the admin center, your IT admin has to go to Settings -> Services & add-ins -> Microsoft Teams -> Apps. Then find Jira Server in the list of apps and add a checkbox to enable the app.
Integration with Microsoft Teams 3

How to configure Jira Server integration (compatible with Data Center)

  1. Install the Jira Server application to Microsoft Teams (from the app store).
  2. From Atlassian Marketplace install the Microsoft Teams for Jira add-on in your Jira Server/Data Center instance. 

To successfully authenticate, the user is required to have direct network access to Jira Server/Data Center. This may mean connecting to VPN or doing this inside a work subnet where Jira Server/Data Center is hosted. Please note that it is valid only for the authentication process and is not needed further for other workflows.

Integration overview

The integration mechanism uses Azure SignalR, which relies on WebSockets.

  • Microsoft Teams communicates with the Jira Server integration application using the Azure Bot app service.
  • The Jira Server integration application communicates with the Jira Server for Microsoft Teams add-on (plugin) via the Azure SignalR service.
  • The Jira Server for Microsoft Teams add-on calls the Jira REST API directly from the Jira Server on-premises instance. API responses are sent back to the application via the SignalR connection.
  • The Jira Server integration application is based on the Microsoft Teams Bot application. You can find more information about bots here: Build bots for Teams.
  • The Jira Server for Microsoft Teams add-on calls the application directly in the next cases:
    • Add-on is installed
    • Add-on is uninstalled
    • Health check calls
  • All the rest of the communication is made via SignalR.
Integration with Microsoft Teams 4
Jira Server <> Microsoft Teams data flow

Microsoft Teams Jira Connector integration

The integration mechanism is webhook based. The Jira Server application has to be enabled in Microsoft Teams and the webhook URL provided is the one to be configured in the Jira Server/Data Center instance.

The Microsoft Teams Jira Connector sends notifications about your team's Jira activities directly into your Microsoft Teams channels. Notifications contain the necessary information to act on them. These are channel-specific configurations, so specific channels receive specific events.

The Jira Server Connector works only with "issue created" and "issue updated" events. The Connector cannot interpret any other types of events. If you enable the "issue updated" event, you will start receiving all the updates on the issue, including comment updates. You may apply a specific JQL filter in Jira webhook configuration to get notifications only on the data you need.

General information on Connector functionality

Once Jira Server Connector is set up, users will be notified in a chosen channel about Jira issues updates. The cards sent by the Connector display pre-defined fields that cannot be customized: priority, issue type, status, assigned to, reporter. Once a comment is added to the Jira issue, the card sent to the Teams channel will display an additional comment field.
Integration with Microsoft Teams 5

Integration overview

Jira Server sends a POST request to the HTTPS endpoint of the connector backend that is hosted on Microsoft Azure. The backend transforms the data to a format that can be consumed by Microsoft Teams. Then it issues a POST request to the Microsoft 365 infrastructure (also HTTPS) that propagates this transformed message to Microsoft Teams chat.
Integration with Microsoft Teams 6

Additional information

Link
Description
Jira Server platform REST API (8.13.0)
This Jira Server platform REST API reference will help you understand how Jira is queried. The data and relevant attributes are received from the Jira REST API and not maintained somewhere within the app.
The Jira Cloud platform REST API
This Jira Cloud platform REST API reference will help you understand how Jira is queried. The data and relevant attributes are received from the Jira REST API and not maintained somewhere within the app.
Microsoft Teams Integration for Jira - Privacy and Data Processing
This Knowledge Base article details what data is collected and how it is stored.

Was this content helpful?

Connect, share, or get additional help

Atlassian Community

Purpose-fit guidance and support to ensure your team's success

Each deployment of Atlassian products is unique, so we offer a breadth of services to design, implement, and optimize solutions for scale.

Learn More