Question
TAL
AU
Last activity: 25 May 2022 3:02 EDT
Configuration of Microsoft Graph API endpoints for Email Listeners
Pega provides configurable Email Account form to use Microsoft Graph API as a way to Send and Receive emails.
While doing so, Pega calls Graph API endpoints for various operations such as browse, read, send download, delete etc..
MS Graph on public Azure is at https://graph.microsoft.com.
We have a requirement for the Email Listeners to use the Graph APIs deployed on a facade service on an API gateway.
By doing so, If the system wants to get a list of users it’d call https://api.CustomInternalGW.com/ms-graph/users & the API G/W would forward the request to https://graph.microsoft.com/v1.0/users.
However, there seem to be no way of configuring custom end-points if we wish to use MS Graph as a send/receive mechanism.
Does anyone have come across similar requirements or have any suggestions about implementation?
***Edited by Moderator Marije to change Content Type from Discussion to Question; added capability tags***
Updated: 24 May 2022 9:50 EDT
Pegasystems Inc.
GB
@PURNENDU-1 do the following forum posts help?
Using Graph API for inbound email integration
Outbound Email - MS Office 365 using MS Graph - Customer API Headers
TAL
AU
Hi @MarijeSchillern , referred the above article and documentations. These didn't help with what we wanted to achieve.
To give you an example, in R-U-F pxSendEmail, there are Pega Private Java APIs which refers the Email Account instance and sends an email using a Private Java API. There isn't an option available to configure Graph API custom end-points.
This can be though as using a proxy or facade instead of public Azure Graph APIs.
