Purpose
This guide outlines the functional differences between Microsoft Exchange Web Services (EWS) and Microsoft Graph. It serves as a central hub for comparing legacy EWS behaviors with new Graph outcomes, ensuring a smooth transition for all users.
Background
Microsoft is officially deprecating EWS for Exchange Online on October 1, 2026. Beyond this date, third-party integrations relying on EWS will cease to function. Migrating to the Graph API is required to:
Maintain Service Continuity: Avoid sync interruptions after the deprecation deadline.
Enhance Security: Align with modern authentication and Microsoft’s latest security frameworks.
Future-Proof Workflows: Leverage Microsoft’s primary platform for all future 365 innovations.
Known Behavior Changes
Here are some of the cases we have identified so far:
| Feature | Description | Date |
|---|---|---|
| Unsent Meetings with Classic Outlook | When the custom directive field This applies to meetings created in Classic Outlook where:
Under EWS, these meetings are correctly marked as not sent. This is a Microsoft Graph limitation, not a defect in Riva’s logic. Impact
Notes: Microsoft Graph does not expose a built-in |
7th May, 2026 |
|
|
Moving to Microsoft Graph changes how you recover deleted data. Unlike the older EWS connection, Graph removes the "SoftDelete" safety net for Calendar and Contacts. Additionally, Tasks can only be moved to the "Deleted Items" folder. If your team relies on recovering items from a secondary "hidden" bin, you’ll need to adjust your workflows, as that middle recovery step is no longer available. |
6th May, 2026 |
| Universal Change Detection for Tasks |
Universal Change Detection is currently not supported for Tasks with Microsoft Graph. Per Microsoft’s current architecture, change subscriptions for ToDo/Tasks are only supported via Delegated Permissions. They do not support Application-level permissions or impersonation. As Riva utilizes application authentication for security and scalability, UCD cannot support real-time Task subscriptions at this time. |
9th Dec, 2025 |
| Bi-directional calendar updates with attendees | Microsoft Graph API automatically triggers meeting invitations/updates to all attendees whenever an update is made to an event that contains participants. Riva can no longer suppress these notifications. | 3rd Oct, 2025 |
| Decline Appointment Polling |
While Riva’s Declined Appointment Polling ensures CRM accuracy by tracking meetings moved to the "Deleted Items" folder, this feature is currently limited to the EWS (Legacy) Connector. The Microsoft Modern Exchange (Graph) Connector does not currently provide the necessary API access to the Deleted Items folder. Consequently, if a user on a Graph connection declines an invite before Riva’s initial sync (usually within a 5-minute window), the system cannot detect the removal. In these rare "race condition" cases, the attendee will incorrectly remain listed as "Active" in the CRM. |
14th Jul, 2022 |
Next Steps
If you observe unexpected synchronization behavior or encounter an issue not documented here, please submit a support ticket via Zendesk or contact the Riva support team for further assistance.
Related to