Einstein Activity Capture with Microsoft Graph API (Beta): Known Gaps and Limitations

This section explains the specific gaps and limitations customers may run into when using Einstein Activity Capture with the Microsoft Graph API Beta integration, so administrators can set expectations before enabling it in a sandbox org.

Concurrency Limits and Throttling

Compared to existing EWS connections, the Graph API has much stricter concurrency limits. As a result, Einstein Activity Capture may be throttled more frequently, which can cause sync delays. While Salesforce is actively investigating and optimizing to address sync delays, escalate this issue with Microsoft to increase the Graph API concurrency limits.

Functional Data Synchronization Gaps

Several synchronization functions are unavailable or restricted when using Graph API:

• Recurring Events: Graph API 1.0 doesn't handle exceptions and deletions in a recurring series. This functionality is only available in Graph API Beta. For onboarding/day 0 sync, the Graph API does not support retrieving recurring series that started in the past but have occurrences within the sync window.
• Event Sync: Microsoft Graph Beta supports bidirectional event sync.
• Deletions: If a deletion notification is missed, it can't be recovered from the recycle bin.
• Contact Sync: Not all Contact fields are available in the Graph API. The unavailable fields include Assistant Phone, Business Fax, Home Fax, and Other Phone.

Einstein Activity Capture Product Experience Impact

Functionality that leverages the Graph API Beta impacts testing, support, and feature availability.

• Functionality leveraging the Beta feature does not undergo the rigorous performance and quality testing of a standard release. It may have unforeseen performance bottlenecks or quality issues that could negatively impact the user experience. After the Graph API features transition to General Availability (GA), they will undergo the rigorous testing required for standard releases.
• Several connected features and products may not be supported when using the Graph API Beta integration:
  • Inbox and Email Send are unsupported connected features. Attempting to send emails results in an error message.
  • Only Global Authentication via the Salesforce Admin is supported in the Beta. There is no support for User Authentication owned by each individual user.
  • Ongoing incident and issue support related to a Beta feature is usually delayed, because GA features are considered higher priority in the Support queue.

Beta Scope Reminder

This article applies exclusively to the Beta version of EAC with Graph API. The content does not apply to the GA version release. If you are not a participant in the Beta program, disregard this information.