Outlook & Microsoft 365
Microsoft is stricter about how it hands mail over and about the credential that keeps a connection alive. Both are handled here, which is why the mailbox stays connected and a message somebody moved is not sitting here twice.
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.
A message lives in one folder, so moving it moves it here
Microsoft gives each message exactly one containing folder, and that 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 credential changes every time it is used
Microsoft issues a new one on each refresh and retires the old after a short grace period. Holding on to the old value eventually fails and switches off an account that was still perfectly good, so the new one is written back every time.
Two runs at once do not tread on each other
Before the new mark is stored, the saved value is read again and compared with what this run started from. If another run already moved it on, only the status is updated and the newer mark stands.
Deleted there means gone here
Deletions arrive as removal markers and take the stored copy with them. A folder move arrives as a delete and a create rather than as a second copy of a message you already have.
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 organization
- 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 mailbox connections, tracking, calendar and meetings.
Book a slot while the customer is still on the line and the invitation is in their inbox before you say goodbye. What they change comes back when you sync.
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.
A meeting agreed on a call is never lost because somebody else's service was slow. The booking is saved here first, then the room and the calendar entry.
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 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