Office365 SMTP configuration receives authentication errors
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
The following appears in the atlassian-jira.log:
Unable to connect to the server at smtp.office365.com due to the following exception: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessfulThe following appears in the atlassian-jira-outgoing-mail.log:
MessageId='null' com.atlassian.mail.MailException: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not authenticatedDiagnosis
The JIRA Server is unable to send mail to the Office365 SMTP server because it fails to authenticate. This can happen even if it is able to receive mail successfully.
Cause
For the username, Office365 requires the username in your SMTP configuration to be your full email address, which includes the domain. For example: your_username@yourOffice365domain.com
Resolution
Go to Administration > Outgoing Mail, and Edit the SMTP Server configuration. When filling out the Username, put in the full email address.
Additionally, Microsoft frequently requires password updates, so it is advisable to check your Office365 account by logging in directly with Microsoft to make sure that a password change is not currently mandated.
For further reference, review the following configuration information from Microsoft:
Outlook settings for POP and IMAP access for Office 365 for business or Microsoft Exchange accounts