Einstein Activity Capture (EAC) usually fails to sync Outlook emails because of an incomplete or misconfigured connection between Salesforce and Microsoft 365, contacts that aren't matched to existing CRM records, users excluded from the active EAC configuration, or sync direction set to "Salesforce only." Most issues trace back to authentication scope, configuration assignment, or the contact-matching rules.
How Einstein Activity Capture Sync Actually Works
EAC connects to a user's Microsoft 365 mailbox through OAuth, reads sent and received emails, then matches the email participants against Salesforce contacts, leads, or person accounts. Only emails tied to a matched record show up on the activity timeline. If the match fails, the email never appears — even though the connection looks healthy.
That matching step is where most teams get tripped up. EAC doesn't log every email in your inbox; it logs emails where at least one external participant exists as a Salesforce record. No record, no sync.
Most Common Reasons Outlook Emails Aren't Syncing
The Connection Method Is Wrong or Broken
EAC supports connecting Microsoft 365 either at the org level (admin-authorized) or per user. If your Microsoft 365 tenant uses modern authentication and conditional access policies, the OAuth token can silently expire or get blocked. Check Setup > Einstein Activity Capture > Settings and confirm the connection status reads Connected, not Pending or Error.
A frequent culprit is Microsoft blocking the connection through a conditional access rule. Your Microsoft 365 admin may need to whitelist the Salesforce app in Entra ID app registrations.
Users Aren't Assigned to an Active Configuration
EAC only works for users included in a configuration. If a rep was added to Salesforce after the EAC config was created, they won't sync until you add them. Go to the EAC configuration, check the Assigned Users section, and confirm the rep is listed and the configuration is active.
Sync Direction Excludes Email Capture
Each configuration has settings for what to sync — emails, events, or both — and the direction. If email sync is toggled off, or set to sync events only, no Outlook emails will flow in. Verify that Email is enabled and the sync includes inbound and outbound messages.
Contacts Don't Match Salesforce Records
This is the quiet killer. If you're emailing a prospect whose address isn't on any contact, lead, or person account, EAC has nothing to attach the email to. Add the prospect as a contact or lead, and emails sent after that point should sync.
Excluded Addresses and Domains
EAC lets admins exclude specific email addresses or entire domains from capture. Internal company domains are often excluded by default to avoid logging internal chatter. If a legitimate external domain ended up on the exclusion list, those emails get filtered out silently.
Step-by-Step Troubleshooting Checklist
Work through these in order — the fix is usually in the first three.
- Confirm the Microsoft 365 connection status shows Connected under Einstein Activity Capture settings.
- Verify the affected user is assigned to an active EAC configuration.
- Check that the configuration has email sync enabled in both directions.
- Confirm the email participant exists as a Salesforce contact, lead, or person account.
- Review excluded addresses and domains for false positives.
- Have the user re-authenticate their Microsoft 365 mailbox if the token looks stale.
Sync Delays vs. True Failures
Don't confuse latency with a broken sync. EAC isn't real-time. Newly connected users can take up to 24-48 hours for historical email backfill, and ongoing sync runs on a delay measured in minutes to a few hours. Before declaring a failure, send a test email to a known matched contact and wait a couple of hours.
Historical capture also has limits. EAC typically backfills emails going back a set window (often six months) rather than your entire mailbox history. Older emails simply won't appear, and that's expected behavior, not a bug.
Permissions and Licensing Gotchas
EAC requires the right permission set license assigned to each user. Standard EAC is included with Sales Cloud, but advanced features may need an add-on. If a user lacks the Standard Einstein Activity Capture permission set, they won't sync regardless of how clean the configuration is.
The Microsoft side matters too. The mailbox account used for the connection needs sufficient mail-read permissions. If your org uses application-level (server-to-server) authentication, the service account must have impersonation rights across the mailboxes you want captured.
When the Problem Is Microsoft, Not Salesforce
Sometimes the breakdown sits entirely on the Microsoft 365 side. Multi-factor authentication prompts that go unanswered, license changes that strip Exchange Online access, or mailbox migrations between tenants all sever the EAC connection. Microsoft's Exchange Online connectivity documentation is a useful reference when ruling out mailbox-side issues.
If your team relies heavily on email tracking for outbound work, keeping EAC healthy matters as much as the messaging itself — the same way teams running AI-driven personalized cold email outreach need reliable activity logging to measure what's landing.
Key Takeaways
Einstein Activity Capture not syncing Outlook emails almost always comes down to one of four things: a broken or unauthorized Microsoft 365 connection, users missing from an active configuration, email sync disabled or pointed the wrong direction, or email participants that aren't matched to Salesforce records. Start with the connection status and configuration assignment, confirm the contact exists, then check for exclusion rules and permission gaps. Give new connections a day or two before assuming the worst — and if you're optimizing outreach generally, choosing the right tooling like ChatGPT vs Claude for cold outbound emails only pays off when your CRM accurately captures every reply.