Thanks for reaching out ahead of time to prepare for Microsoft's deprecation of TLS 1.0 and 1.1 for email connections to Office 365. After June 2020 when TLS 1.0 and 1.1 will be rejected on Microsoft's side, POP3 and IMAP will continue working if they're handled over TLS 1.2.
In Jira Server, some extra configuration is needed to enable TLS 1.2 for incoming and outgoing mail. In order to apply these settings, you'll need to be running Jira on Java 8 or above. If you're not sure about this, you can use Jira's System Information Page to determine which version of Java you're running under. Again, you want Java 8 or above in order to apply these settings. Most installations of Jira should be fine, although you may find Java 7 in very old versions of Jira or servers that were set up a long time ago.
After this, Jira should negotiate a TLS 1.2 connection with Office 365!
Atlassian documentation reference: JIRA Mail initiates TLSv1 connection only
Hi Daniel Eads,
We are using Jira service desk = no server where I can do any changes! Sorry about not writing that in to the question. All that we have is a web login.
I can see that the mail addresses that we are using accessing 0365 using TLS 1.0.
So do you have a soultion for me, when you have this new parameters?
Not sure if this helps. Here's what I've done to get email working between Office 365 and Jira Service Desk Cloud edition, and hopefully, I'm not anticipating and issues when MS deprecate the support for TLS 1.0.
I think the selection for SECURE_IMAP automatically ensures port 993 is set.
And that should be it.
Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond. A long time favorite, Team Cale...
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