Hi @Microsoft Q & A,
Thanks for posting in our Q&A forum.
By research, this error may occur when using IMAP with OAuth authentication to access Office 365 or Outlook mailboxes. Below are some possible solutions:
- Make sure "IMAP4" is added to Client Access Rules in O365, and when testing the input in O365 using Jira context, the test is completed successfully. https://v4.hkg1.meaqua.org/en-us/exchange/clients-and-mobile-in-exchange-online/client-access-rules/client-access-rules#how-client-access-rules-are-evaluated
- Complete the Authorize request using OAuth2.0 with username and password for the required email account.https://confluence.atlassian.com/jirakb/imap-fails-with-a3-bad-user-is-authenticated-but-not-connected-error-in-jira-server-integrated-with-office365-665420269.html Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
- Check if the mailbox is disabled or hidden from the address list. reference: https://v4.hkg1.meaqua.org/en-us/answers/questions/280259/user-is-authenticated-but-not-connected
Hope it can help.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.