Hi Dietmar Schmid (Didi)
We have already an Enhancement Request open regarding Oauth 2.0 authentication for connector for Exchange and awaiting a response from the Product Team.
For Microsoft Graph I cannot answer. But I'll create a case on your behalf to gather the required information and eventually pass this on to the Product Team as well.
Hi Dietmar, could you please outline some use-cases for an MS Graph integration. What kind of benefits would the customer expect? This kind of information greatly helps to better understand customer needs and supports the "roadmap eligibility" evaluation.
Hi Michael! Currently the connector check always the full Inboxes what is very time consuming and not in real time. The customer expects that he has a real time connection to the Exchange Server that the people with CRM and without CRM has the same view on data.
Currently we have one example where it is important, that the know it a room is booked or not. Because what the want in the future, that the CRM Users are able to book rooms in the CRM software, the other one book it in Outlook and in the future customers should be also possible to book directly a room over a portal. So it is important that the user knows in real time, if a room is available or not.
With MS Graph it is possible to ask in real time which rooms are free.
We had a similar problem -> as the connector exchange used the pull strategy (v10.2.20) :
We decided to not use the connector as the "latency" between changes in the same mailbox were to high (depending on all other mailboxes) and a "nearly realtime" processing was not possible.
I don't know if this has changed since then (v11.9)?
Ticket # 443983 - Exchange Webservices EWS using Publish / Subscribe or Poll?
..and Microsoft has already pre-deprecated EWS:
Exchange Web Services (EWS) was launched as a part of Microsoft Exchange 2007 as a SOAP based API that allows access to Exchange and Exchange Online data. Starting today, Exchange Web Services (EWS) will no longer receive feature updates.