Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6998

Office 365 using OAuth 2.0 doesn't support GCC customers

XMLWordPrintable

    • 16
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Atlassian Update – 07 March 2022

      Hi everyone,

      This is Alex from the Jira Service Management Data Center & Server team.

      As of JSM DC version 4.22 this is now possible with the support of multiple incoming emails.

      You can now configure as many dedicated email channels as required, using a custom URL specific for Microsoft GCC accounts, for better communication with customers.

      For detailed instructions on how to configure a GCC account using a JSM incoming mail handler, please refer to the KB article Guide explaining how to configure a GCC account with a Jira or a Service Management mail handler using Oauth 2.0.

      You can learn more about email channels here, and creating custom links using OAth 2.0 Configuration here.

      Kind regards,

      Alex

      Jira Service Management, Data Center & Server

      Issue Summary

      Since Jira Service Desk 4.12, support to connect mail channels to Office 365 accounts using OAuth 2.0 has been introduced. However, it doesn't support GCC (Government Community Cloud) accounts.

      It isn't supported because regular Office 365 accounts connect to outlook.office365.com whilst GCC accounts connect to outlook.office365.us.

      Therefore, the connection is not established and the mail channel can't be connected using OAuth 2.0

      Workaround

      Manually update the hosts file of the operating system to point to the US domain. However, doing this will remove the automatic failover to a new IP address in case of outages in the primary IP address.

      Example:

      40.66.16.130 outlook.office365.com

              Unassigned Unassigned
              rbaldasso Rodrigo Baldasso
              Votes:
              14 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: