3802369 - EWS Vs Graph - Feature, Behavior Differences And Limitations In Server Side Integration

This document describes the different behavior between EWS and Graph API and its limitations.

SAP Cloud for Customer

Outlook category / tagging model:

    EWS: every synced item gets one shared category ("SAP Cloud for Customer" in V1 / "SAP Sales Cloud" in V2), plus a second, more specific category for some object types (e.g., Visit, Phone Call, Account, Individual Customer).
 
   Graph: each object type gets exactly one dedicated category instead - SAP Email, SAP Appointment, SAP Visit, SAP Phone Call, SAP Contacts, SAP Accounts, SAP Individual Customers, plus a dedicated error category. Tasks are the exception: Graph does not support categorization for tasks at all, so the old "SAP Task" category is gone, and all synced tasks simply land in a dedicated "SAP Tasks" list.

Known limitations on the Graph side

   --> Categories are not supported for Tasks.
   --> Recurring task synchronization is not supported (both V1 and V2)
   --> Deleted tasks cannot be processed through Graph the way they were via EWS.
   --> Migrating tasks back from Graph to EWS is not supported - task migration is effectively one-directional.
   --> Instant sync of calendar events from Outlook to SAP Sales Cloud is not available both in V1 and V2 for Graph users.
   --> Notifications for non-essential meeting updates (including past meetings) made by the organizer are sent to all attendees automatically; this behavior needed further verification and may differ from EWS.
   --> Centralized/mass Add-in deployment through our own admin panel is not available for Graph  app-only sign-in and end-user sign-in - it must go through the "Deploy Add-ins" feature in the Microsoft 365 Admin Center, using a manifest exported from Groupware Settings. This is a genuine Microsoft-side platform limitation (confirmed with Microsoft, on their roadmap as high priority but with no committed date), not a gap in our implementation. We're also working on a Microsoft Store listing for the add-in as an alternative deployment path.

Consent and permissions

For EWS, only a single all-encompassing scope was granted ('full access'), without any breakdown. Graph, by contrast, requires a more granular set of permissions — most of which are mandatory, while some are optional. For delegated access, the requested Microsoft Graph permissions include offline access, sign-in/profile, reading basic profiles of all users, and read/write access to mailbox settings, mail, calendars, tasks, and contacts (with Mail.ReadWrite.Shared and Calendars.ReadWrite.Shared being optional, needed only for shared mailbox/calendar scenarios). App-only access uses a similar but distinct permission set, granted once at the tenant level. There is no difference in the permission set between C4C V1 and V2 — both use the same application and the same underlying scopes.

Help Portal: Use Microsoft Graph for Working with Microsoft 365 Data

Server Side; SSI; Graph; API; EWS; Limitation;  , KBA , LOD-CRM-GW-SCC , Invisible CRM - Smart Cloud Connect Solution , How To

SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications 2608