Hi @ninixink​ ,

Is this the thread you are referring to?  

We don't have a specific example of using EWS and the HTTPCaller, but below are some resources that may help you get started. To fill out the HTTPCaller parameters, you'll need to refer to the EWS API documentation.

• Working with Soap Services
• Getting Started with APIs
• Making a GET Request with HTTPCaller (instead of JSONfragmentor, use XML transformers as EWS returns XML)
• https://stackoverflow.com/questions/70746930/send-receive-email-using-ews-rather-than-imap-smtp
• You can create a workspace using the HTTPCaller to check the mailbox using the API and then set this on a schedule, similar to how the poll option works in IMAP (https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/ews-operations-in-exchange).

Microsoft Graph connector is a viable option. You can update the web connection with your own client id and secret.

• Thread on Microsoft Graph connector

Hope this helps!

-Kezia

Hi @keziaatsafe​ , thank you very much for your answer, really appreciate it.

We decided to use Microsoft Graph and we actually tried with MS Graph Type Application Web connection https://hub.safe.com/publishers/supporter/web-connections/microsoft-graph-type-application.

However, we are having a token expiration issue as it keeps expiring every hour and we have to keep reauthenticating it.

Have you seen this issue before and do you have any suggestion, please?

In the Web Service Configuration, we kept the default setting and I notice the grant_type=client_credentials, is this correct?

Do we need to ask our Cloud team to grant us a refresh token & grant_type = refresh_token?

Also, do we need to ask them to add the fmeoauth URL to the Redirect URI in the MS Graph App like how we normally do with other Oauth2 App?

Thanks and looking forward to hearing from you!

Hi @ninixink​ ,

Thank you for the update! I think you're on the right track.

Did you follow this article, "How to create a web service for Microsoft Graph" when setting up the web connection? If not, please ensure you followed the steps in the article. In step 8, the refresh token parameters should look similar to this:  

client_id=�CLIENT_ID]&client_secret=lCLIENT_SECRET]&refresh_token=�REFRESH_TOKEN]&grant_type=refresh_token

Here's another resource on refresh token that may be helpful: https://community.safe.com/s/article/Web-Connections-and-FME

Please let me know if the resources I've shared are not what you're looking for!

Kezia

Thanks @keziaatsafe​  for the info, we finally resolved this issue with HTTPCaller and didn't use the Web Connection.

We reached out to MS support and there are 2 different Oauth2 flows - Oauth2 client credential flow (App Identity flow) or the Oauth2 code grant flow (User Identity flow). The one that we are using is App identity flow as this allows us to read multiple mailboxes including shared mailboxes. These mailboxes will need to be added to a security group that links with our App (Application ID/ Client ID).

So what we did was:

• Reauthenticate by calling this send “Client_id” + “Client_secret” to AAD token endpoint again. Reference: https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow
• Retrieve the access token from the authentication call, and add it to the next call when we make a request to get mailboxes' message details.

Hope that helps if anyone else has the same issue with MS Graph API reauthentication.

Thanks! 🙂