Configure an outgoing link

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

When you configure an outgoing link to an external application, Jira requests data from this application, which means that it acts as the OAuth client. This type of link is primarily used in Jira to create the OAuth 2.0 integration for popular mail servers. To learn more about the type of links and additional details, see Link to other applications.

OAuth 2.0 for SMTP outgoing mail servers is supported in Jira 9.2 and above.

We keep the support for Google and Microsoft as providers, as well as the IMAP, POP3, and SMTP protocols for connection for Jira versions 8.22 to 9.1.

We’ve created an outgoing OAuth 2.0 integration primarily because Google and Microsoft announced deprecating basic authentication. This means you wouldn’t be able to use these providers (Gmail, Microsoft Exchange Online) to let users create issues and comments from emails if you were authenticating using basic auth. To fix this, you need to configure the OAuth 2.0 integration with these providers, and then update the configuration of your mail servers.

You don’t need to take any actions if you’re using IMAP or POP3, these will continue to work.

You need to ensure the following:

To create an outgoing link:

  1. In the upper-right corner of the screen, select Administration  > Applications.

  2. Under the Integrations (the left-side panel), select Application links.
  3. Select Create link.

  4. In a new dialog that opens, select External application, and then choose Outgoing as the direction.

  5. Fill in the details as described in the following sections.

Follow these steps to configure your link:

Choose one of the following providers that you want to configure. Choosing Google or Microsoft lets you create an OAuth 2.0 integration for mail servers – in this case, some of the fields will be pre-filled:

  • Google

  • Microsoft

  • Custom (for internal tools or other providers)

Copy the Redirect URL and register it in your external application to obtain the client ID and client secret required to complete the configuration.

If you’re using Google or Microsoft as service providers, you’ll be able to copy the Redirect URL right away. For custom providers, you need to first provide the Authorization endpoint and Token endpoint. For more information on registering the URL with Google or Microsoft, check out the following guides:

Different providers might have different requirements related to the redirect URL. For example, Google doesn't allow it to be a private IP address. Make sure you provide an external URL (for example, of a load balancer for Jira Data Center).

Provide the remaining details. Here you can find descriptions for all the fields.


Client ID

The client ID that's generated by the external application after registering Jira’s Redirect URL. This is the public identifier of the application.

Client secret

The client secret that's generated by the external application after registering Jira’s Redirect URL. This is the shared secret between Jira and the application, which ensures the authorization is secure.


The required OAuth 2.0 scopes (permissions) that control what Jira can do in the external application. You need to specify different scopes for email servers. 

For Google, we recommend this scope: (for IMAP and POP3)

For Microsoft, the scopes will vary depending on your Microsoft account type:

  • If you're using non-GCC (Government Community Cloud) accounts, we recommend the following scopes:
    • (for IMAP)

    • (for POP3)

    • offline_access

  • For GCC accounts, use: 
    • (for IMAP)
    • (for POP3)
    • offline_access

For more information about scopes available in Google and Microsoft, see the detailed information at the Microsoft & Google sites.

Authorization endpoint

The HTTPS URL where authorization to use OAuth 2.0 is started.

Token endpoint

The HTTPS URL where refresh token requests are sent. As OAuth 2.0 tokens have an expiry, Jira will periodically update the token.

Redirect URL

The Redirect URL that must be registered in the external application to obtain its client ID and client secret. This redirects the authentication flow back to Jira.

After you save the link, it will appear on the list together with other application links. You will now be able to select this link when configuring mail servers, DVCS accounts, or Jira Service Management email channels.

You can use your link in the following built-in functionalities in Jira:

If you're facing some issues while configuring outgoing links for applications, check out the following articles:

Last modified on Oct 27, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.