Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Microsoft will soon retire basic authentication:
In our environment we are using O365 and secure imap for ticket creation automation in Jira. After Basic Auth will be retired for Exchange Online - will it be possible to use their new OAuth 2.0?
Hi Community,
How do you understand below from Microsoft announcement?
"In response to the COVID-19 crisis and knowing that priorities have changed for many of our customers we have decided to postpone disabling Basic Authentication in Exchange Online for those tenants still actively using it until the second half of 2021. We will provide a more precise date when we have a better understanding of the impact of the situation.
We will continue to disable Basic Authentication for newly created tenants by default and begin to disable Basic Authentication in tenants that have no recorded usage starting October 2020. And of course you can start blocking legacy authentication today, you don’t need us to do anything if you want to get started (and you should)."
1) What do they consider to be active tenants - postpone disabling Basic Authentication in Exchange Online for those tenants still actively using it until the second half of 2021?
2) How to understand this part - begin to disable Basic Authentication in tenants that have no recorded usage starting October 2020?
Thanks in advance!
Have got this as a reply from Microsoft Support;
1. Active tenants are ones with at-least one mailbox per month using Basic Authentication for the specific protocol.
2. No recorded usage indicates that Basic Authentication was not used for a mailbox for the last x months
x is still being determined. Think 1 - 2 months. That's the current thinking. Feedback always welcome.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any update for this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We've got the same setup so I've created a suggestion for it. https://jira.atlassian.com/browse/JSWSERVER-20381
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Google just blasted out announcement that they'll be turning off support for less secure applications as well.
June 2020 -> no new instances
Feb 2021 -> all existing disabled
Atlassian really needs to get OAuth support added to their Incoming mail handlers.
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.