@Randy Padgett - if you are using an unlicensed account, like a shared mailbox in O365, try adding a license. Another user in this thread was using a shared mailbox, he added a license, converted it to a user mailbox and reauthorized. He then converted back to a shared mailbox.
Which permissions are required in Azure Enterprise app?
I have to approve the admin consent but this just adds my email address to the incoming server instead of the proper email address.
Anyone knows how to fix this?
Thanks
---Edit---
I resolved this by deleting the Enterprise app in Azure and then run thr re-authorize process again > user does not have permissions so I logged in as Azure admin > this gave me a Consent box which I checked (while signed as Azure Admin).
@Björgvin Arnarsson , our Outlook admin had to authorize JIRA app request in his console. If your Outlook is managed by a 3rd party, you have to contact them and have them look for new request. (we had to do the same a few weeks ago when Atlassian pushed this change out, had issues and rolled it back).
Once that's done, try authorizing again. Keep in mind it will try to authorize using YOUR account if you are logged in. This is not correct - you need to say use different account and use email and password combination that was used to set up mailbox. If you don't have that info, you need to change password for that mailbox first and then come back and authorize again.
If anyone has still the issue that Jira doesn't process mails after re-authorization and you are using Exchange Online accounts, then check if your user/mailbox has the language set to English.
We were using mail accounts with German language setting and it didn't work. Connection succesful but no processing of emails in the Inbox. After changing the language to English it worked immediately.
According to the Atlassian support this is a known issue they are already working on but it's still not clear if the cause lies in Jira or Microsoft side.
To fix this, I had to delete the Enterprise app in Azure > reauthorize it to create a fresh enterprise app with admin consent permissions > re-authenticate the mailboxes
Atlassian Team members are employees working across the company in a wide variety of roles.
July 17, 2024 edited
If you've re-authenticated your Office365 mail server in Jira and the emails are still not pulling through.
To resolve this issue, please perform one of the following steps:
Change the Language: Change the language of Outlook Web and Outlook app to English. After making this change, please wait for a while and check if the issues have been created.
Update Folder Name: You can update the translated name of Inbox from Outlook in the Folder Name section on the mail handler configuration
Changing the inbox name to your local language should fix the issue as Microsoft has recently updated their API and we are supposed to enter the inbox name in the local language.
You must re-authorise with the email account's login, not your email admin account. This was something that was not explained as previously when we configured a new email account it requires your mail admin to login to authorise the config. With this change, you need to re-authorise with your email account's login details.
Once re-authorised, the banner should disappear if successful.
Emails will now remain in the mailbox when the email processing is successful where as previously it would get deleted. This could be bad as you can't tell if it has failed.
There isn't any entries in the Audit Log regarding the mail processing so you can't tell what is happening so the only way is to test it and see if it works.
Not sure we use this (we use Jira Service Management instead), I tried to authorise what looks to be a default 'Cloud Support Mailbox' and it fails... Do I simply delete it, or should I raise a support call to try to understand how it's failed?
When I reauthorized on this page .All the incoming mail id , it picked my email by default , it should have been mail id for that project as it was configured earlier. So the incoming mail to that mail id is used to create issues in a particular project.
e.g My email id is Abc
project catch email id is xyz for xyz project
when I reauthorize its abc for xyz project.
Now its creating issues in that project that I received. Its entirely wrong.
@Anuradha Das- you need to reauthenticate as the original catch ID. So when it asks you to login to reauth, don't put your own ID in, use the catch ID/password.
44 comments