Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to change Microsoft Project OAuth Authentication to GCC High Endpoints?


    We are attempting to process incoming service request emails from the Microsoft GCC High Endpoints. We are able to successfully configure OAuth with the Endpoints using the following configuration:



Authorization endpoints (Tenant-ID has been sanitized):<tenant-id>/oauth2/authorize


Token Endpoint:<tenant-id>/oauth2/token


However, when we attempt to configure Project Settings > Email Requests > Microsoft we receive the following error message:

Here's the error we received: "OAuth token not defined for connection. OAuth Authorisation required."

This appears to be due to the following API call that seems to hard code Microsoft as "" We need to change this to as the .com does not support GCC High OAuth requests as per Microsoft Documentation. Please note the URL has been sanitized of specific information.

https://<Jira Service Management URL> /rest/servicedesk/1/servicedesk/<ProjectKey>/incomingemail/oauth/update

Additionally here is a copy of the XHR request (Sanitized):

PUT /rest/servicedesk/1/servicedesk/<ProjectKey>/incomingemail/oauth/update HTTP/1.1
Host: <Jira Service Management URL>
Connection: keep-alive
Content-Length: 262
Pragma: no-cache
Cache-Control: no-cache
Accept: application/json, text/javascript, */*; q=0.01
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36 Edg/89.0.774.63
Content-Type: application/json
Origin: <Jira Service Management URL>
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Referer: https://<Jira Service Management URL>/servicedesk/admin/<ProjectKey>/email-settings
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
Cookie: atlassian.xsrf.token=B9VN-TQ5C-KGM9-BWAD_760c2bb42e388776c1920233fe03c2613a3090c3_lin; JSESSIONID=2A626FF988270B824A6C171C7B1A0DEC

And finally the response (sanitized):


{"id":8,"emailAddress":"<EMAIL Address>","requestTypeId":1,"requestTypeName":"Get IT help","requestTypeIcon":10627,"enabled":true,"username":"<EMAIL Address>","protocol":"imaps","host":"","port":"993","broken":false,"timeout":50000,"clientConfigurationId":"202c5a4f-a857-4444-85e5-62f027f324eb"}


The expected response should be:

{"id":8,"emailAddress":"<EMAIL Address>","requestTypeId":1,"requestTypeName":"Get IT help","requestTypeIcon":10627,"enabled":true,"username":"<EMAIL Address>","protocol":"imaps","host":"","port":"993","broken":false,"timeout":50000,"clientConfigurationId":"202c5a4f-a857-4444-85e5-62f027f324eb"}


Any ideas on how to fix this?


0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Announcing Mindville Insight is now part of Jira Service Management!

Hello Community! We’re excited to announce that Mindville Insight’s asset and configuration management capabilities will now be integrated into Jira Service Management Premium and Enterprise plan...

643 views 9 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you