Skip to main content

Office 365 Email Sync: What Admins Need to Know

Written by James Graham
Updated this week

Overview

Jiminny's Email Sync captures customer emails alongside calls and meetings, giving reps and managers a complete view of customer interactions. This article explains what Email Sync does, how it handles your data, and how users enable it, so you can feel confident about what you're turning on.

Looking to grant email permissions? Email consent is handled in the Grant Consent for Office 365 Integration article. Use the "Grant access to Mailbox" or "Grant access to all recommended resources" consent link to include the Mail.Read permission.


How Users Enable Email Sync

Once your administrator has granted the Mail.Read permission via the Grant Consent article, each user can enable email syncing in their profile:

  1. Go to Profile Settings in Jiminny

  2. Click Integrations

  3. Toggle on "Import Email Conversations"

Email syncing will begin immediately.


What Jiminny Syncs

Which Emails Are Included

Jiminny imports inbound and outbound emails (received and sent) from connected Office 365 mailboxes. Deleted emails and drafts are excluded.

Only customer and prospect correspondence is imported. Internal emails and other non-customer messages are automatically excluded through:

  • Cross-referencing with your CRM accounts, contacts, and leads

  • Blocked domain list filtering

  • Transactional and marketing email filtering

What Jiminny Does Not Sync

  • Internal emails (filtered via blocked domain list)

  • Drafts and deleted items

  • File attachments (not downloaded or stored)

  • Bcc recipients

  • HTML formatting (stripped to plain text)

Sync Frequency and History

  • Initial sync: Looks back to the oldest open opportunity date in your CRM (minimum 1 week)

  • Ongoing syncs: Every 15 minutes for new messages

Data Captured Per Email

Jiminny processes plain text content only. The following metadata is captured:

  • Sender and recipients (To/Cc fields)

  • Subject line

  • Message body (plain text)

  • Date and Message-ID headers

  • Reply threading information

When multiple users appear in an email thread, Jiminny deduplicates and assigns the email to the opportunity owner or inbox owner.


How Emails Appear in Jiminny

Synced emails are displayed as customer engagements within Deal Insights and customer records, alongside calls and meetings. This gives your team a single timeline of all customer interactions.


How Email Matching Works

Jiminny determines relevance by cross-referencing your CRM:

  1. Extracts sender and recipient email addresses from each message

  2. Matches these against your CRM accounts, contacts, and leads

  3. Only emails with a confirmed CRM match are imported

  4. Unmatched emails are discarded and never stored in Jiminny

Additional filtering removes transactional emails (e.g., receipts, automated notifications) and marketing emails. Internal emails are excluded based on a configurable blocked domain list.

This approach ensures your team sees only business-relevant correspondence while protecting employee privacy.


Security and Data Handling

  • Permission model: Jiminny uses the Mail.Read delegated permission, which is read-only. Jiminny cannot send, modify, or delete emails.

  • Data in transit: All connections to Microsoft Graph API are encrypted via TLS.

  • Data at rest: Imported emails are stored in Jiminny's MariaDB and Elasticsearch databases on AWS.

  • Processing: Emails are processed in temporary memory before being stored. Attachments are never downloaded or stored.

  • Retention: Imported emails are retained according to your Jiminny subscription and configuration. You can export or delete specific conversations at any time.

For a complete technical breakdown of all permissions, data processing, and architecture, see Office 365 Integration: Technical Details.


Frequently Asked Questions

How does Jiminny connect to Office 365 for email? Via OAuth 2.0 authentication through the Microsoft identity platform. Jiminny uses the Mail.Read delegated permission on the service principal in your Microsoft Entra tenant, connecting to Microsoft Graph API to read email data on behalf of signed-in users.

Can Jiminny read all of a user's emails? Technically, the Mail.Read scope grants access to a user's mailbox, but Jiminny only processes emails where the sender or recipient matches a CRM account or lead. Everything else is discarded and never stored.

Can Jiminny send emails or modify my mailbox? No. Jiminny only has Mail.Read (read-only) access. It cannot send, delete, forward, or modify any emails.

What happens if I don't grant the Mail.Read permission? Email Sync simply won't be available. All other Jiminny features (calendar sync, Notetaker, Teams sharing) work independently.

How do I disable Email Sync for a specific user? The user can toggle off "Import Email Conversations" in their Jiminny profile under Integrations. To revoke the permission at the tenant level, remove the Mail.Read consent grant from the Jiminny service principal in the Entra admin center under Enterprise applications > Jiminny > Permissions.

Did this answer your question?