Please upvote this if you want this to work with application permissions as well as delegated rights:

JSDSERVER-13955 Allow Microsoft Graph API integration for Incoming Mail handlers (JSM) using the client credentials flow - Create and track feature requests for Atlassian products.

And they removed outgoing email from the text . I will be recommending moving away from Atlassian, since they are not able to deliver emails properly in a professional way.

It's been silently bumped to Q2 according to the public roadmap. Can we please have an approximate release date.

Is this still expected in Q1?

@Charlie Marriot

We are still awaiting a response from the ATLASSIAN team.

It's not normal to wait so long and not have a precise answer on the subject.

I ask again, do you have a delivery date for these new features.

@cmarriott would it be possible to get an approx estimate on which build it will be released i.e. 9.4 LTS or upcoming LTS? This will help in planning our next upgrade.

Hello,

Do you have any news on the subject?

My request is urgent?

Hello,

Do you have any news on the subject?

My request is urgent?

Please escalate this ask. Many MS admins are deprecating IMAP/POP3 and we need a way to securely integrate Jira with Azure!

No security team will approve IMAP/POP3 nowadays, therefore this is a mandatory and critical feature for us Jira admin. 

Must have since POP3 and IMAP are not approved by our security team.

We're looking in the possibility to support the functionality for our end-users to be able to comment on existing issues, or create new issues, through e-mail. Together with our Digital Workplace-team, we've spent time on configuring and creating a connection with OAuth 2.0. There are raised concerns in our departments about using an Azure App Registration and the way it's granting permission; IMAP/POP3 will be decommissioned in the near future and should be migrated to Microsoft Graph.

Reference: [Deprecation of Basic authentication in Exchange Online | Microsoft Docs|https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online]

Our security department will not allow IMAP/POP3 access to our Exchange Online server which prevents us from using Jira Mail Handler until it supports Graph API (and application permissions - not just delegated!). Right now we're either facing a security risk or immensely reduced value of the Jira offering. Neither beneficial for using Jira at our company.

Please update this issue with a tentative roadmap, so we at least know when we should expect it, instead of 'maybe'.

I'm sure you have many other customers using Exchange Online with IMAP/POP3 disabled? They're all facing this issue...

We are moving from POP3 to MS Graph API. Please can Atlassian indicate when this functionality will become available?

As of this issue being opened, the suggested course of action is to disable legacy protocols in favor of more secure ones.  Adding this will open the previously used functionality for many Office 365 users.

You may want to escalate this issue, as the incoming mail feature will mostly become inaccessible for Office 365 users on Oct 1, 2022.

Reference: https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online

This is a key requirement for our org as well as for most corporate infosec teams. PLEASE escalate this with urgency. 

We are in the same situation, security won't allow us to use IMAP(S) or POP3, only EWS (which Microsoft wants to deprecated too) or Graph. 

We are also in need for this as org has decided to kill all POP3 mailboxes in near future. Please give some priority to this request.

Same issue , our mailboxes are getting migrated to MS graph .

POP and IMAP will be deprecated. When Jira will start supporting it ? 

Maybe we can update the title of this ticket to be more specific to email integration - "Microsoft Graph API Email Integration"

Same boat here, Cyber is turning off IMAP support in our O365 tenancy. Jira needs to include Microsoft Graph API as a connection method in the System/IncomingMail and Project/EmailRequest setup, of course with the backend code to support that. 

Any news about this?

We are not allowing IMAP access due to security reasons and so we couldn't utilise "Incoming mail handler" feature at all in our org. "OAuth 2.0" in Jira is a very good feature but Jira should be capable to work with other {{Microsoft GRAPH API's in scopes. }}

Below scopes isn't the rightful approach for us and should have scopes as,

Please any update about this? Is very important to my customer. Is the recomendation of microsooft

https://developer.microsoft.com/en-us/office/blogs/end-of-support-for-basic-authentication-access-to-exchange-online-apis-for-office-365-customers/

We are still blocked with issues, can you please update on this request.

One of our customers also asked for the integration. They switch to MS Graph soon.

can you please provide an update on this issue.

any update on this ticket.

It looks like feature request already create around 2018 and still there resolution on this issue.

https://jira.atlassian.com/browse/JRASERVER-68068?focusedCommentId=2410333&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2410333

@here can you please provide update on this issues?  as you know we are still blocked with this issues by affecting ~2500 users.

Note: Here is an Atlassian community discussion thread on the subject of connecting Jira to Microsoft Exchange issues which has been opened since 2012 and we don't have promising answer. Which means all US Government offices have this issues. Hope this will help to escalate this issues.
https://community.atlassian.com/t5/Jira-questions/JIRA-mail-server-with-Exchange/qaq-p/90235

As you know we have blocked and because of this issues Inbound email notification is not working for all our users (more than 2500 users) at our organization (AO office). 
Is that possible to make this bug as priority, or else is that possible to escalate this issues to make I High Priority bug!  Please confirm.