Question
UnitedHealth Group
US
Last activity: 20 Jun 2023 5:17 EDT
Unable to configure Email Account to connect to Outlook 365
We have configured email account on Outlook 365 (Exchange Cloud). Followed the steps to register application on Azure Portal, and enable API access.
We have setup Authentication Profile to use OAuth2 with Client Credential (and also tried with Password Credential).
We have configured Email Account with provider as Microsoft Office 365 to use Microsoft Graph to Send/Retrieve email. However the test connection fails on both Sender and Receiver with the following error.
ERROR:
Failed while retrying to fetch accesstoken for clientID = xxxxxxxxx-xxxxxxxx-xxxxxxxxxxxxxx: java.net.SocketException: Connection reset
We need your assistance to setup the email integration.
Pegasystems Inc.
GB
@PulakDebnath Did you check steps in OAuth 2.0 authentication for email providers and Configuring outbound email?
Could you please configure with client credentials grant type with required API permissions?
Have you checked with Azure team to get the details of User principal name that can be used? Ideally this is the actual email address of the INBOX used.
Please check the details of the logs.
UnitedHealth Group
US
Hi Marije, I have followed the pega's doc as well as MS Graph API doc and I think I did all the due diligence before seeking for help. This is what I did so far.
- configured User Principal Name (i.e. the email id) on Outlook 365.
- Went into Azure Portal to register an App and set up client secret.
- Worked with Azure admin to grant required roles to use Graph APIs related to email.
- Configured an OAuth2 custom Auth Profile in pega to use Client Credential type. Here, used the clientID/ClientSecret and token endpoint which generated after registering app.
- Configured the Email Account and chose Outlook 365 as provider, and Microsoft Graph for protocol.
The test connectivity is failing. Please let me know if I am missing any configuration.
Pegasystems Inc.
GB
@PulakDebnath if other users on the PSC forum can offer no other suggestions then I would suggest that you log a support incident on the MSP .
Please provide the INC reference as a reply here so that we can help track this.