Exchange Sync
The diary and the address book half of a Microsoft connection, riding on the same sign-in that carries the mail. Whether the mailbox sits in Microsoft 365 or on an Exchange server in your building is worked out for you.
Routing a mailbox to a backend
question 3 of 4- 1a saved setting on the connection
- 2the kind of connection it is
- 3a lookup on the mail domain
- 4otherwise, the modern interface
- three subscriptions per mailbox
- calendar written in either direction
- contacts read into their own table
a connection typed as Exchange is turned away by the message worker. Mail arrives over the Microsoft connection instead
matched on the provider event identifier, thirty days behind to a year ahead, and a cancellation deletes the row
two hundred pages in one pass, into a table of its own, and never written back to the mailbox
Product figures from the platform’s own defaults - not customer averages
How it works.
Nobody has to tell it where the mailbox lives
A saved choice, then the connection kind, then a lookup on the mail domain, then a cloud-first default. If a hosted mailbox is ever aimed at the old protocol Microsoft is switching off, it is stopped right there rather than failing quietly a month later.
A server in your building and a hosted mailbox look the same
The on-premises and the cloud path do the same twelve things, so nothing above them has to know which one answered. A rep gets the same calendar either way, and moving between the two is not a rebuild.
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.
The push is a shortcut and the sweep runs anyway
Microsoft pushes what it can, and the ten-minute pass runs underneath it regardless. When a push lapses it is marked inactive and that same pass covers the gap, so what you lose is a few minutes rather than a meeting.
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.
- 01Connect
the account it syncs with
- 02Compose
writing it, and from what
- 03Send
leaving now, or on a schedule
- 04Arrive
landing, and what it lands as
- 05Attach
pinning it to the right record
- 06Book
the meeting that comes of it
- 07Govern
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 organization-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 traveling 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
- A connection typed as Exchange is refused by the message sync worker; mail comes through the Microsoft connection instead
- Disconnecting
- Subscriptions canceled, 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
What this sits beside.
Mail and diary are one surface with several parts. These are the ones a person passes through in the same minute.
More in Email & Calendar
12 capabilitiesWebmail, four mailbox connections, tracking, calendar and meetings.
The thread and the lead it belongs to are one screen apart, not one tab apart. Snooze, send later, and a reading pane that runs nothing the sender wrote.
Mail is here without anybody pressing refresh or forwarding anything, filed against the lead holding the address. Google knocks the moment something changes.
The connection for a mailbox nobody hosts for you. We sign in for real before saving the hosts and ports, so a typo is caught while you are still at the form.
Templates with merge variables, organized into groups and granted per team, so the answer your best rep writes becomes the answer everybody sends.
Regulated copy stays with the people allowed to send it. Filing a template into a group is what shares it, so there is no second step for anybody to forget.
What does not count is the useful part: a rep opening their own message, a crawler, the same person twice in five minutes. A figure a supervisor can act on.
Park a thread and it comes back at the hour you named, unread, so nobody walks past it. Hold a send and it leaves at the hour you named, once, never twice.
Nobody retypes their sign-off. It is held once per mailbox and added on the way out, so mail from the platform arrives looking like mail from a person.
Move the meeting an hour and the Zoom room moves with it, on the link guests already have. Delete the booking and the room goes too, with nobody chasing it.
The join link is made by the calendar itself, on the same save that books the meeting, so nobody hunts for it later. One Google account is the whole setup.
Pick Teams on a booking and the join link is written into the invitation guests receive, so nobody chases it in a follow-up. A room you own travels too.
Mail files itself against the lead, on a rule short enough to print: the addresses on the lead, matched exactly. No domain guessing, and nothing to dispute.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
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