Jira and JSM customers using Microsoft OAuth for automatic email-to-ticket creation were unable to process incoming emails for approximately 6 days. The issue has been resolved for new incoming emails, though affected customers must manually re-authorize their Microsoft mail server via Jira Admin settings to fully restore functionality. Atlassian proactively contacted impacted organizations with re-authorization instructions.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below.
If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing.
The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions.
To re-authorise an incoming Microsoft mail server:
Login in Jira as Admin
Select > System
Select Mail > Incoming Mail.
Select Edit incoming mail server.
Select re-authorise .
Enter your Microsoft credentials to continue using your Microsoft mail server.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with