Hello Taras Podoroha,

Thanks for your question.

Recent Pega platform release 8.4 includes native support for email listener using Microsoft Graph APIs with OAuth 2.0. This feature allows customers to use OAuth2 client credentials grant in the email listener to connect to Office 365 mailboxes.

Thanks,

Prasad Akella.

Hello Sekhar,

Thanks for your response.

We are evaluating on providing additional options for Pega platform 8.x versions and please reach out to me incase you are are using office365 with email listener so that I can keep you updated.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

We evaluated multiple options and I just want to provide an update that this is a new feature and as such will not be backported to older versions. If you are using Pega email listener on Pega versions prior to 8.4, please contact your account executive so we can support you in your upgrade.

Thanks,

Prasad Akella.

Please note that I have edited this to provide latest update on the current status. I would request you to follow this https://collaborate.pega.com/discussion/microsoft-office-365-retire-basic-auth-support-imappop for future updates on this topic.

Hello All,

We are on Pega Infiniti 8.4.3 version and we are also facing the same issue. We have few email accounts configured that connects to the mailbox with in our organization for processing our cases that comes via email.

My organization is migrating from IMAP authentication to OAUTH2.0 with Microsoft Graph via Microsoft O365 provider.

And Pega allows the client credentials and password credentials only if you select Microsoft Graph as receiver in the OAUTH 2.0 profile. And clearly we cannot use password credentials as we want to come out of that approach. Hence, the left over is only client credentials which uses the access token methodology.

When we do this the scope parameter is required which Pega says its optional.

After we fix that we got the access token successful.

However, the test connectivity is still failing due to permissions issue in azure configuration. See below ,"NoPermissionsInAccessToken","message":"The token contains no permissions, or permissions cannot be understood.

At this point, we are kind of stuck and trying to see if anyone else has experienced this situation and if so, how this was resolved, any inputs is much appreciated.