Hello,
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:
Scopes:
https://graph.microsoft.us/IMAP.AccessAsUser.All
https://graph.microsoft.us/SMTP.Send
https://graph.microsoft.us/User.Read
https://graph.microsoft.us/offline_access
https://graph.micosoft.us/openid
Authorization endpoints (Tenant-ID has been sanitized):
https://login.microsoftonline.us/<tenant-id>/oauth2/authorize
Token Endpoint:
https://login.microsoftonline.us/<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 "outlook.office365.com" We need to change this to outlook.office365.us 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":"outlook.office365.com","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":"outlook.office365.us","port":"993","broken":false,"timeout":50000,"clientConfigurationId":"202c5a4f-a857-4444-85e5-62f027f324eb"}
Any ideas on how to fix this?
Has anyone als determined if add-ons are allowed to similarly be connected to Microsoft Office 365 Government?
Were you able to find a fix for this? We are experiencing the same problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.