Solved

Future of Exchange Connector

  • 10 June 2022
  • 3 replies
  • 165 views

Userlevel 2
Badge +3

Hello everyone,

We asked Thinkwise Support about the way to set up the Exchange Connector in cases where the legacy EWS Connector is missing from Azure. The reply was to add full Application permissions for the newer Office 365 Exchange Online connector in Azure. However, that Office 365 Exchange Online option is not present in Azure either.

Microsoft advices to use the MS Graph connector for as much as possible. We might be able to go that route. But we're curious about the contingency plan for the Thinkwise Exchange Connector. Is there such a plan? What is the future for this connector?

Best regards,
- Alex

icon

Best answer by Jasper 15 June 2022, 14:28

View original

This topic has been closed for comments

3 replies

Userlevel 2
Badge +3

Hi Alex,

In theory it should be possible to do this with a process flow and using the OAuth connector. For example, it should be possible to set up webhooks for incoming emails and to send messages with the MS Graph API.

I would like to make this so that end users can connect to their o365 mailbox themselves. I have made several attempts, but so far it has not worked. Configuring it is too complicated and there is no guarantee of success.

A turn-key solution within TSF to allow end users to connect securely to the O365/MS Graph environment would be very desirable.

Regards,

Harm

 

Hi Harm,

Your experience is equal to ours; things are theoretically possible, but it turns out to be very cumbersome to effectively realise a solution. Thanks for sharing your findings!

Best regards,
- Alex.

 

Hi Alex and Harm,

We have actually already planned upgrading the Exchange connector to the Microsoft Graph API for Q3 this year.

If possible, we will do this entirely using standard Thinkwise platform functionality, leveraging protocol independent web services and the OAuth 2.0 connector, for example. This will possibly also make it easier to adapt the connector to your own liking, e.g. using delegated permissions instead of application permissions.

Our goal is to ship this new Exchange connector (through the Thinkstore) with the next release of the platform, which is currently scheduled for November.


Jasper, hi,

Thanks for this information! We had a good talk with one of your senior developers about this, and about the Scheduler, that - for us - is related to the Exchange Connector and our client's needs. We're very much looking forward to this next release!

Best regards,
- Alex.

Userlevel 7
Badge +11

Hi Alex and Harm,

We have actually already planned upgrading the Exchange connector to the Microsoft Graph API for Q3 this year.

If possible, we will do this entirely using standard Thinkwise platform functionality, leveraging protocol independent web services and the OAuth 2.0 connector, for example. This will possibly also make it easier to adapt the connector to your own liking, e.g. using delegated permissions instead of application permissions.

Our goal is to ship this new Exchange connector (through the Thinkstore) with the next release of the platform, which is currently scheduled for November.

Userlevel 5
Badge +20

Hi Alex,

In theory it should be possible to do this with a process flow and using the OAuth connector. For example, it should be possible to set up webhooks for incoming emails and to send messages with the MS Graph API.

I would like to make this so that end users can connect to their o365 mailbox themselves. I have made several attempts, but so far it has not worked. Configuring it is too complicated and there is no guarantee of success.

A turn-key solution within TSF to allow end users to connect securely to the O365/MS Graph environment would be very desirable.

Regards,

Harm