Skip to content
Adoptiv

Exchange Sync

The calendar and address-book half of a Microsoft connection: the diary and the contacts hanging off the same consent that carries the mail, kept in a store of their own and routed to whichever backend the mailbox needs.

Routing a mailbox to a backend

question 3 of 4
Incoming
Four questions, in order
  1. 1a saved setting on the connection
  2. 2the kind of connection it is
  3. 3a lookup on the mail domain
  4. 4otherwise, the modern interface
The guard runs inside every question, not after them
Modernimplemented
  • three subscriptions per mailbox
  • calendar written in either direction
  • contacts read into their own table
A lost subscription marks itself inactive and the ten-minute pass covers the gap
On premisesscaffold
connectdisconnectsyncCalendarcreateEventupdateEventcancelEventsyncMailsendMailreadContactscreateSubscriptionrenewSubscriptiondeleteSubscription
Twelve operations, every one raising not-implemented
Mailrefused

a connection typed as Exchange is turned away by the message worker. Mail arrives over the Microsoft connection instead

Calendarboth ways

matched on the provider event identifier, thirty days behind to a year ahead, and a cancellation deletes the row

Contactsread only

two hundred pages in one pass, into a table of its own, and never written back to the mailbox

What this sync pulls lands in its own store. The calendar screen reads the platform table and not this one
There are two doors onto this and they are not the same door. The empty-state tile sends you through the ordinary consent flow; the Exchange panel sends you through the admin one, which answers 400 unless an Azure directory id has been set. Both end in a Microsoft mailbox connection when they end at all.
0
resources the subscription layer covers
0
days of calendar kept in view
0
steps in the backend decision

Product figures from the platform’s own defaults - not customer averages

The mechanism

How it works.

01

Four steps settle which backend answers

A saved choice, then the connection kind, then a lookup on the mail domain, then a cloud-first default. Every one of those routes through a guard that throws if a hosted mailbox is aimed at the legacy protocol, which Microsoft is switching off.

02

Both backends satisfy one contract

The on-premises and the cloud path implement the same twelve operations, so nothing upstream branches on which one it was handed. A server behind your own firewall and a hosted mailbox are the same object to everything above the routing.

03

Calendar both ways, address book one

Events are matched on the provider's identifier and travel in both directions, so a booking made here reaches the mailbox and an edit made there comes home to the same row. A cancellation deletes it. Contacts are read into a table of their own and never written back.

04

Subscriptions are a shortcut, not a leg

A change subscription pushes what it can and the ten-minute pass runs underneath it regardless. A failed renewal marks the subscription inactive and that same pass covers the gap, so a lapsed push costs latency rather than data.

Where it sits

Two moments in every message.

Every message passes through the same seven. Exchange Sync is the lit ones, and everything either side of it is a different page in this category.

  1. 01
    Connect

    the account it syncs with

  2. 02
    Compose

    writing it, and from what

  3. 03
    Send

    leaving now, or on a schedule

  4. 04
    Arrive

    landing, and what it lands as

  5. 05
    Attach

    pinning it to the right record

  6. 06
    Book

    the meeting that comes of it

  7. 07
    Govern

    who may use what, and see what

The specifics.

8 facts
Connecting
Two doors, depending which screen you started from. The tile in the mail empty state sends you through the ordinary Microsoft consent flow; the panel on the connections page sends you through the organisation-wide one, which refuses to start without an Azure directory identifier
Backends
On-premises and cloud, both implementing the same twelve operations, chosen by the four-step routing
Calendar
Thirty days behind to a year ahead, matched on the provider event identifier, cancellations delete, writes travelling out on that same identifier
Contacts
Read-only, two hundred pages in one pass, into a dedicated table
Where it lands
Its own store. The calendar screen reads the platform's table and not this one
Mail
A connection typed as Exchange is refused by the message sync worker; mail comes through the Microsoft connection instead
Disconnecting
Subscriptions cancelled, stored credentials blanked, cursors cleared, and your login untouched
Not the same as
Outlook and Microsoft 365 carry the mail over this same connection. This page is the diary and the address book hanging off it

More in Email & Calendar

12 capabilities

Webmail, four sync providers, tracking, calendar and meetings.

Webmail

A full mail client inside the CRM, with snooze, send later, eight system folders and a reading sandbox that never runs a single thing the sender wrote.

Gmail Sync

Connect Gmail on one scope and mail arrives by push rather than polling, filed against the lead holding the address, with nobody having to forward anything.

IMAP & SMTP

Any mailbox that speaks IMAP and SMTP connects with a form and a live login test, so a provider nobody built an integration for is still a real inbox here.

Email Templates

Templates with merge variables, organised into groups and permissioned per team, so the answer your best rep writes becomes the answer everybody sends.

Template Permissions

Grant a whole template folder to particular roles and teams, so regulated copy stays with the people allowed to send it. Filing is the act of sharing here.

Open & Click Tracking

Opens and clicks recorded against the record, with signed link identifiers so the tracking endpoint never trusts a parameter it was handed.

Snooze & Send Later

Put a thread out of sight until it matters and schedule a send for the morning, with the parked thread coming back unread so you cannot walk past it.

Email Signatures

One signature per connected mailbox, added by the send path to new messages and forwards, so mail from the platform arrives looking like mail from a person.

Zoom

Connect Zoom and a booking creates, moves and cancels the meeting for you, with the joining link and passcode riding inside the calendar invitation.

Google Meet

Pick Google Meet on a booking and the calendar write mints the link with the invitation, so everyone on the account gets it rather than finding it in a note.

Microsoft Teams

Connect Teams and a booking makes the meeting through Microsoft's own interface, carrying its joining address into the invitation the guests receive.

Email-to-Record Matching

Inbound mail attaches to the lead holding any address on it, sender or recipient, matched exactly once lowercased. Two columns, one query, no resemblance.

Email & Calendar

See exchange sync on your own floor.

Thirty minutes, your numbers and your data. We will set exchange sync up live and you can decide from the thing itself rather than from this page.

14-day trial · no card · migration included