Microsoft has announced that on October 1st, 2026, EWS requests from non-Microsoft apps will be blocked to Exchange Online.
As a result, this request seeks to enable the connector to handle connecting to hosted Exchange environments by introducing support for MS Graph as a means to read the contents of the inbox (i.e. the emails used for processing), instead of using Exchange Web Services to do so. #171 includes many (but not all) of the steps that would need to be factored into the current connector.
As a result of the proposed changes, a unique benefit to Exchange Online users would exist wherein the connector would no longer have a dependency on the EWS dll. It would be a combination of SMLets, Active Directory (as has been the case for Reviewer management), and PowerShell's native Invoke-RestMethod for communicating with Graph.
Microsoft has announced that on October 1st, 2026, EWS requests from non-Microsoft apps will be blocked to Exchange Online.
As a result, this request seeks to enable the connector to handle connecting to hosted Exchange environments by introducing support for MS Graph as a means to read the contents of the inbox (i.e. the emails used for processing), instead of using Exchange Web Services to do so. #171 includes many (but not all) of the steps that would need to be factored into the current connector.
As a result of the proposed changes, a unique benefit to Exchange Online users would exist wherein the connector would no longer have a dependency on the EWS dll. It would be a combination of SMLets, Active Directory (as has been the case for Reviewer management), and PowerShell's native Invoke-RestMethod for communicating with Graph.
Maintain on premise support via EWS
Support connectivity via MS Graph and its native Mail.ReadWrite, Mail.Send, and Calendars.ReadWrite based permissions
Updating relevant documentation on configuring the Azure App associated with the connector