is it possible for JIRA mail server to access Office 365 shared mailboxes yet?

Ben Newport May 9, 2017

I know you have to use this format for login but it is not working/


username: <O365 user name>/<shared mailbox name>
password: <O365 user password>

3 answers

1 accepted

7 votes
Answer accepted
Maarten Cautreels
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 9, 2017

Hi Ben,

According to JRASERVER-30688 it should work using the following configuration:

Protocol: SECURE IMAP
Host: outlook.office365.com
Port: 993

Email address: sharedmailbox@mydomain.com

Username: sharedmailbox@mydomain.com
Password: (sharedmailbox user password)

Hope this helps.

Best,

Maarten

siboconnection October 3, 2018

According to the comments in JRASERVER-3088 it may also be necessary to reset the shared mailbox password. I was not able to authenticate from Jira until I had done this.

To reset the password in the Microsoft 365:

  1. Open the Microsoft 365 admin center.
  2. Go to Users > Active users
  3. Click the shared user you created for Jira
  4. Click Reset password
  5. Follow the instruction to create a new password
  6. Use the new password as described by @Maarten Cautreels
matthew.mellifont January 8, 2019

I am installing the server version of Jira now and I only have Secure_SMTP and SMTP as my protocol options? 

Thoughts on how I can get IMAP to get the shared mailbox feature working? Would be awesome. 

Thanks

Matt

Joshua Carpenter January 8, 2019

In the Microsoft Exchange admin panel (shared user > mailbox features) I have only IMAP enabled, and mail from Jira is working with the following settings for outgoing mail:

From address: sharedmailbox@mydomain.com

Protcol: SMTP
Host Name: smtp.office365.com
SMTP Port: 587
Timeout: 10000 (the default)
TLS: selected

Username: sharedmailbox@mydomain.com
Password: sharedmailbox user password

Like matthew.mellifont likes this
Ryan Carpenter January 8, 2019

Oops... I commented as my son. The comment from @Joshua Carpenter is actually from me. :-)

Like # people like this
matthew.mellifont January 8, 2019

Legend! Thanks mate, appreciate the quick response!

Like Ryan Carpenter likes this
Jason Ferris February 20, 2019

We are going through this same config however using the noted settings is not allowing a connection.


We reset the password to what it was originally just to reset it but no luck yet. 


Protocol: SECURE IMAP

Host: outlook.office365.com

Port: 993


Email address: sharedmailbox@mydomain.com


Username: sharedmailbox@mydomain.com

Password: (sharedmailbox user password)

Like Anderson Assis likes this
Jason Ferris February 20, 2019

Unfortunately no connection was possible. Review the errors below and rectify:

  • AuthenticationFailedException: AUTHENTICATE failed.
Jason Ferris February 20, 2019

Figured this out. UPN wasn't correct in AD. updated that and now we're good.

0 votes
Dieter Joseph February 27, 2020

I had the same issue and got resolved after following the advice on this thread. One thing to add.  I had DISALLOWED IMAP and POP against all accounts on our O365 tenant by default. So after some trial an error, discovered this and enabled IMAP. 

I believe you have to use IMAP as the modern authentication with O365, which would bring up a nice popup box and cater for 2 factor authentication is non existent. 

After setup, our team are now able to send an email direct to suppoert@ourcompanydomain.com and the tickets appear in Jira Service Desk correctly. And then replies from within Jira, go back to the end user. 

0 votes
Rich Wolverton February 15, 2019

Note:  To logon to Office365 requires a UPN (User Principle Name) – which for convenience sake, because no normal person would know what the heck that is – Microsoft says to make the UPN the same as the Primary SMTP (email) Address and tell users – login with your email address… that users understand.  Our Outlook admin provided a username which we entered into the 'username' field in the Incoming email configuration.  What was really needed was the email address. BTW. The failure to login successfully gets a socket timeout so we were blaming the network.  All in a days work. 

Suggest an answer

Log in or Sign up to answer