Outlook & Microsoft 365
Microsoft hands you a change token rather than a change log, and rotates your refresh token every single time you use it. Both of those shape how this connection is built and where it used to break.
A delta run on a Microsoft mailbox
delta querywritten back, old one into grace
re-read and compared before any write
- newRe: Q3 haulage schedulestored, with its one parent folder taken as the whole truth
- @removedStatement of account (old id)a tombstone. The stored row goes with it
- newStatement of account (new id)the same message after a folder move, arriving as a fresh entry
- @removedNewsletter, deleted in Outlookremoved here too. There is no soft flag on this connection
Product figures from the platform’s own defaults - not customer averages
How it works.
One parent folder, never a set of labels
Microsoft gives each message exactly one containing folder, and that value is taken as the whole truth. Moving a message elsewhere removes the old filing here instead of leaving it in two places at once.
The refresh token changes every use
Microsoft issues a new one on each refresh and retires the old after a short grace period. Keeping the old value eventually fails the refresh and disables an account that was still authorised, so the new one is written back each time.
Two jobs, one token, no clobber
Before the new change token is stored, the saved value is re-read and compared with what the run started from. If another run already advanced it, only the status is updated and the newer token stands.
A tombstone removes the local copy
Deletions arrive as removal markers and take the stored row with them. A folder move produces a new identifier plus a marker for the old one, so it reads as a delete and a create rather than a duplicate.
Two moments in every message.
Every message passes through the same seven. Outlook & Microsoft 365 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- Consent
- Six Graph permissions: mail read, mail read-write, mail send, calendar read-write, contacts read, and offline access
- Two doors
- The common endpoint for one person's mailbox, or a named Azure directory with admin consent for a whole organisation
- Incremental
- A change query across the entire mailbox rather than the inbox alone, so sent items and drafts move too
- First sync
- The whole mailbox from the epoch forward, a hundred pages deep
- Push
- A change subscription on the whole mailbox lasting seventy hours, with an hourly pass renewing anything inside two hours of expiry
- Trusting a notification
- Only when its subscription identifier matches the unguessable one we created and stored. The tenant hint in the payload is never enough on its own
- Attachments
- Files are stored, a OneDrive reference keeps its link, and an attached message keeps only its name and size
- Not the same as
- Exchange Sync, which drives the diary and the contact list over this same Microsoft connection
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 sync providers, tracking, calendar and meetings.
Google Calendar writes out the moment you save and mails the invitations, and reads back on demand, so a meeting booked on a call is there before it ends.
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.
Templates with merge variables, organised into groups and permissioned per team, so the answer your best rep writes becomes the answer everybody sends.
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.
Opens and clicks recorded against the record, with signed link identifiers so the tracking endpoint never trusts a parameter it was handed.
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.
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.
Book from the conversation, with the invitation, the joining link and the record all created together instead of in three separate tabs afterwards.
Connect Zoom and a booking creates, moves and cancels the meeting for you, with the joining link and passcode riding inside the calendar invitation.
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.
Connect Teams and a booking makes the meeting through Microsoft's own interface, carrying its joining address into the invitation the guests receive.
Inbound mail attaches to the lead holding any address on it, sender or recipient, matched exactly once lowercased. Two columns, one query, no resemblance.
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 outlook & microsoft 365 on your own floor.
Thirty minutes, your numbers and your data. We will set outlook & microsoft 365 up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included