-
Suggestion
-
Resolution: Fixed
-
16
-
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
- is related to
-
- Gathering Interest
- is resolved by
-
- Closed
- relates to
-
JSDSERVER-11219 'Other' option for Email service provider missing when creating new email channel
-
- Closed
-
-
- Closed
- was cloned as
-
- Gathering Interest
[JSDSERVER-6998] Office 365 using OAuth 2.0 doesn't support GCC customers
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 606807 ] |
| Link | New: This issue is related to JSDSERVER-14090 [ JSDSERVER-14090 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 704711 ] |
| Link |
New:
This issue relates to |
| Description |
Original:
{panel:title=Atlassian Update – 07 March 2022|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ebf2f9}
Hi everyone, This is Alex from the Jira Service Management Data Center & Server team. As of [JSM DC version 4.22|https://confluence.atlassian.com/servicemanagement/jira-service-management-4-22-x-release-notes-1114802916.html#JiraServiceManagement4.22.xreleasenotes-requests] 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. You can [learn more about email channels here|https://confluence.atlassian.com/servicemanagementserver/receiving-requests-by-email-939926303.html], and creating [custom links using OAth 2.0 Configuration here.|https://confluence.atlassian.com/adminjiraserver/link-to-other-applications-938846918.html] Kind regards, Alex Jira Service Management, Data Center & Server {panel} h3. 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 h3. 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: {code} 40.66.16.130 outlook.office365.com {code} |
New:
{panel:title=Atlassian Update – 07 March 2022|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ebf2f9}
Hi everyone, This is Alex from the Jira Service Management Data Center & Server team. As of [JSM DC version 4.22|https://confluence.atlassian.com/servicemanagement/jira-service-management-4-22-x-release-notes-1114802916.html#JiraServiceManagement4.22.xreleasenotes-requests] 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|https://confluence.atlassian.com/display/JIRAKB/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|https://confluence.atlassian.com/servicemanagementserver/receiving-requests-by-email-939926303.html], and creating [custom links using OAth 2.0 Configuration here.|https://confluence.atlassian.com/adminjiraserver/link-to-other-applications-938846918.html] Kind regards, Alex Jira Service Management, Data Center & Server {panel} h3. 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 h3. 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: {code:java} 40.66.16.130 outlook.office365.com {code} |
| Description |
Original:
h3. 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 h3. 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: {code} 40.66.16.130 outlook.office365.com {code} |
New:
{panel:title=Atlassian Update – 07 March 2022|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ebf2f9}
Hi everyone, This is Alex from the Jira Service Management Data Center & Server team. As of [JSM DC version 4.22|https://confluence.atlassian.com/servicemanagement/jira-service-management-4-22-x-release-notes-1114802916.html#JiraServiceManagement4.22.xreleasenotes-requests] 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. You can [learn more about email channels here|https://confluence.atlassian.com/servicemanagementserver/receiving-requests-by-email-939926303.html], and creating [custom links using OAth 2.0 Configuration here.|https://confluence.atlassian.com/adminjiraserver/link-to-other-applications-938846918.html] Kind regards, Alex Jira Service Management, Data Center & Server {panel} h3. 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 h3. 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: {code} 40.66.16.130 outlook.office365.com {code} |
| Fix Version/s | New: 4.22 [ 99907 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Link |
New:
This issue is resolved by |
| Remote Link | New: This issue links to "Page (Confluence)" [ 625602 ] |
| UIS | Original: 13 | New: 16 |