Hi @shepthedog63

While FME doesn't have an out of the box solution for the Microsoft Exchange Web Services you can use the httpCaller transformer to send and receive XML SOAP messages. Feel free to post the idea of a Microsoft Exchange Web Service Connector to our ideas page. https://knowledge.safe.com/content/idea/list.html

https://knowledge.safe.com/articles/45314/working-with-soap-services.html

@RichardAtSafe is there any effort going into getting that as a supported option out of the box? Most corporate companies see iMAP as a security risk and running a local SMPT server (via FME Server) is frowned upon.

Hi @justincornell,

There isn't anything specific, but we are certainly open to suggestions. Would a built in publisher and subscriber using the Microsoft Graph API be the best solution for you?

Microsoft recommends: "we strongly suggest migrating to Microsoft Graph to access Exchange Online data "

We already have a Graph Connector in the hub if you want to give it a try:

https://hub.safe.com/web_connections/microsoft-graph#description

We would love to hear what your ideal scenario.

Thanks,

@RichardAtSafe - The Graph API would be helpful for those who are using O365 (Office 356) or Exchange 2016+, however, I don't believe it's supported for exchange 2013 on-prim. --While I don't see a graph publisher/subscriber being helpful in my current version of exchange, when our company migrates later this year it would be extremely helpful! If you all could please add that to the road map I know it would be a HUGE win!!

I recommended the Exchange Web Services because it could connect with legacy exchange systems on-prim as well as O365 versions. There are python libraries that already implement exchange web services that might provide a quick win for many of your clients.

Thanks!

Justin