Connection settings
All apps deeply integrate with Microsoft 365, which is a cloud only solution.
That’s why our Microsoft 365 for Jira app behaves differently than “classic” Data Center apps.
Your Jira instance needs to meet the following requirements to be able to use our app.
To learn more about why this is necessary, check out the technical references.
Prerequisites
ℹ️ Public Jira instance
Your Jira instance needs to be publicly accessible from the internet.
Microsoft Teams is a cloud software that needs to connect to your instance.
If you are running Jira behind a firewall, it will not work out of the box. A local version that runs within the internal network is currently not available.
If your Jira is using an additional firewall with IP whitelisting, please see our static ip page.
ℹ️ Jira accessibility via SSL/TLS (https://…)
This is highly recommended.
While not strictly necessary, we recommend to only connect instances that support access via SSL/TLS.
Initial configuration
We highly recommend making your Jira instance publicly available to ensure optimal functionality of our app. This way, you won’t need to manually adjust any additional settings.
Upon installing our Microsoft 365 for Jira app, we attempt to register your Jira instance with our cloud infrastructure and set-up the outgoing webhook.
You can check the current status of the registration in the settings screen Connection Settings (see below).
In case your public Jira URL is not the same as the configured Jira base URL, you might need to adjust this here. The screen also supports you in troubleshooting any network errors.
Connection settings helper page
We provide a concise helper page designed to verify whether your connection is set up correctly and to identify any potential errors. Typically, any relevant errors will be displayed here, assisting you in troubleshooting the issue effectively.
Connection status
The first table indicates whether the connection status is operational, along with details about your system's registration in our database and the corresponding Jira URL.
Webhooks
The Webhook will be automatically added during the app installation process. If this does not occur, an error message will be displayed.
Connectivity check
The second table displays the connectivity details. You can verify whether it functions correctly by clicking on “check connectivity” to test it against our server.
Secret rotation
It is important to note that the "Secret rotation" feature should be used with caution. Please apply it only in the specific scenarios described.
In case your public Jira URL is not the same as the configured Jira base URL, you might need to adjust this here. The screen also supports you in troubleshooting any network errors.
Email feature
To use the Email feature, you need to install our Outlook add-in (for free), which enables you to access Jira functionalities directly from your inbox. Deploying the add-in does not require a connection to our backend infrastructure, as it can be downloaded locally.
However, please take the time to understand what this means for the operation of our app on your server: Data Storage and processing | Exceptions