Einstein Activity Capture with Microsoft Graph API - Beta Integration: Known Gaps and Limitations

Note: This article applies exclusively to the Beta version of Einstein activity Capture (EAC) + Graph Application Programming Interface (API). The content is not applicable to the GA version release. If you are not a participant in the Beta program, please disregard this information.

The Einstein Activity Capture integration with Microsoft Graph API features has known gaps and limitations when compared to the existing Exchange Web Services (EWS) connection. These gaps cover critical performance issues, core synchronization limitations, and Einstein Activity Capture product experience impacts resulting from the use of Beta functionality.

Note: The use of the Microsoft Graph beta functionality is limited to testing in sandbox orgs. The deployment of Microsoft Graph beta in production orgs is not supported. 

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/day0 sync, the Graph API does not support retrieving recurring series that started in the past but have occurrences within our 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 leveraging 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. Functionality utilizing the Graph API Beta 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.

• When using the Einstein Activity Capture data capture with Graph API Beta integration, several connected features and products may not be supported:

  • Unsupported connected features include Inbox and Email Send. The Send Email function is currently unsupported; attempting to send emails will result 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. This delay occurs because GA features are considered higher priority in the Support queue.

Note: This article applies exclusively to the Beta version of EAC+Graph API. The content is not applicable to the GA version release. If you are not a participant in the Beta program, please disregard this information.