IntegrationLiveLast tested 2026-08-27Email

Outlook / Microsoft 365 for Manufacturing

Two-way mail and calendar sync for shops on Microsoft 365, with shared mailbox support for a quotes address the whole team works from.

In short

KanchanFlow, the RFQ-to-Order CRM, syncs Outlook and Microsoft 365 mail and calendar in both directions through Microsoft Graph, including shared mailboxes. A shared quotes address is the usual setup in a USA job shop, and it is the one meaningful capability this connector has that the Gmail one does not.

Start Free Trial (No Credit Card)See a Live Quote Draft

Diagram of the Outlook / Microsoft 365 integration: fields KanchanFlow writes to Outlook on the left, fields it reads back on the right.

Most USA manufacturers we speak to are on Microsoft 365, and most of them run a shared mailbox for quote requests. That shared mailbox is the real RFQ queue, and it usually has no owner, no status and no way of telling whether a request from Tuesday was ever answered.

This connector treats the shared mailbox as a first-class source. Messages arriving there create or thread onto records, attachments land on the RFQ, and the queue gains a response clock and an owner. Individual mailboxes sync too, so an estimator's own correspondence with a customer shows on the account.

Status: Live in production
Category: Email
Plan availability: All tiers — AI extraction and OCR from email consume AI credits, which vary by tier
Sync cadence: Near real time via Graph change notifications; a 15-minute poll reconciles anything missed

Field by field

What syncs, in both directions

These are the actual fields that move. Anything not on these two tables does not sync, and we would rather write that down than let you assume it does.

KanchanFlow → Outlook / Microsoft 365

What we write out when a record moves forward.

Field	What we send
Outbound quote email	Sent through the user's own mailbox or the shared quotes mailbox, so it lands in the correct Sent Items and replies return to the right place.
Threaded follow-ups	Follow-up messages send as replies in the original conversation, preserving the conversation ID Outlook uses for threading.
Category tagging	An Outlook category is applied to synced conversations where enabled, so a person working in Outlook can see what the CRM is tracking.
Calendar events	Meetings created from a CRM activity are written to the user's Microsoft 365 calendar with attendees and a Teams link where the account provides one.

Outlook / Microsoft 365 → KanchanFlow

What comes back onto the customer, quote or order record.

Field	What we read
Inbound messages on matched addresses	Mail to and from addresses on customer or lead records, in individual and shared mailboxes alike.
Attachments	Drawings, POs and specifications attach to the record, subject to our 25 MB per-attachment ceiling. OCR is available at three credits per page.
Calendar events and free-busy	Meetings involving CRM contacts appear on the account timeline, and free-busy is read for scheduling.
Delivery failures	Non-delivery reports mark bad addresses so quotes stop going to a contact who has left.
Automatic replies	Out-of-office detection defers automated follow-up rather than sending nudges into an empty office.

Sync cadence. Near real time via Graph change notifications; a 15-minute poll reconciles anything missed. Every record also carries a Sync now control, and the last successful sync time is shown on the record so nobody works from a number of unknown age.

Figures

What this looks like in the product

We do not ship stock imagery or mocked-up screens. These three figures describe the exact shots a designer must capture from a live workspace, each carrying a visible date stamp and recaptured at every quarterly re-test.

Figure 1 · to be captured

The shared quotes mailbox rendered as a CRM queue, with each message showing its matched customer, owner and response clock.

Capture date required. Capture from a live workspace with a genuinely busy shared mailbox. Date stamp required; mask sender domains in the product.

Figure 2 · to be captured

The Microsoft consent screen showing the Graph permissions requested and whether admin consent is required.

Capture date required. Capture the genuine Microsoft screen including the admin consent notice. Date stamp required.

Figure 3 · to be captured

An RFQ record showing a purchase order attachment captured from the shared mailbox and its OCR extraction result.

Capture date required. Capture a real PO OCR result including a field the OCR flagged as uncertain. Date stamp required.

12 steps

Setting it up

Written for the person who will actually do it, in the order they will do it. Nothing here assumes you have done this before.

1Establish whether your Microsoft 365 tenant requires administrator consent for third-party applications. Most manufacturer tenants do, and if yours does, an individual user cannot complete the connection alone.
2Have a Global Administrator or Application Administrator grant consent from the connector's admin consent link. The permissions requested are listed on that page before consent.
3Decide the sync scope: matched contacts only, or full mailbox. Matched contacts only is the default and the right choice for most shops.
4In KanchanFlow, open Settings, Integrations, Outlook and connect the individual mailboxes that need syncing. Each user authorises their own.
5Add the shared mailbox separately using Connect shared mailbox. The connecting user must have Full Access permission on it in Exchange.
6Assign an owner and a response target for the shared mailbox queue. Without an owner, a shared mailbox stays exactly as unaccountable as it was before.
7Set the historical import window; thirty days is the default.
8Configure send-as for the shared address so estimators can reply as quotes@ rather than from their personal address.
9Enable attachment sync and set the OCR policy. Manual OCR triggering is cheaper than automatic and usually sufficient.
10Enable calendar sync if you want site visits and customer meetings on the account timeline.
11Send a test message into the shared mailbox from an external address and confirm it creates a queue item with the correct clock.
12Review the shared mailbox queue after one week and set routing rules based on what actually arrived.

Honest ceilings

What this integration cannot do

Every connector has limits. You will find these in week three whether or not we write them down, so we write them down.

Admin consent is required on most tenants. If your IT department will not grant it, this connector cannot be used, and no workaround exists that we would be willing to describe.
Microsoft Graph applies throttling per mailbox and per tenant. Large historical imports and busy shared mailboxes can be throttled, which shows as delayed rather than failed sync.
Attachments above 25 MB are not synced. The message threads with a marker naming the skipped file.
We do not sync Teams chat messages, only calendar events and mail. A quote negotiated in a Teams chat leaves no CRM record.
Shared mailbox sync requires Full Access permission for the connecting user. If that user leaves the company, the shared mailbox connection breaks and must be re-established by someone else.
On-premises Exchange without a Microsoft 365 hybrid configuration is not supported. Graph is the only interface we implement.

From the quarterly re-test

Errors you will actually hit

Each of these was reproduced deliberately during testing. The wording is the error as the system reports it, not a paraphrase.

Error	Likely cause	Fix
Connect fails with Need admin approval	The tenant requires administrator consent for third-party applications and it has not been granted.	Send the admin consent link from the connector page to your Microsoft 365 administrator. Individual users cannot bypass this and should not try.
Shared mailbox connects but no mail appears	The connecting user has Send As but not Full Access on the mailbox.	Have an Exchange administrator grant Full Access, then reconnect the shared mailbox. Send As alone permits sending but not reading.
Sync shows Throttled during business hours	Graph is rate-limiting the tenant, often because another application is consuming the same quota.	The queue drains automatically. If it persists, narrow the sync scope to matched contacts and reduce the historical window.
Calendar events duplicate	Both the CRM and an Outlook add-in are creating events for the same activity.	Disable one. Running two systems that both write to a calendar always produces duplicates and no configuration prevents it.
Shared mailbox stopped syncing after an employee left	The connection was authorised by that employee's account, which has been disabled.	Reconnect the shared mailbox with a current employee who has Full Access. Use a service account rather than a person's account if you can, so this does not recur.

Questions people ask about the Outlook / Microsoft 365 integration

Yes, and that is the main reason this connector exists for USA shops. A quotes@ mailbox becomes a queue with owners, clocks and routing.

Related integrations

Gmail two-way sync

Every RFQ email, drawing attachment and quote reply threads onto the right record without anyone forwarding anything.

Google Calendar

Put site visits, capability audits and quote review calls on the calendar from the record, with travel time and free-busy respected.

Zoom

Create a Zoom link from the record for a drawing walkthrough, and get the recording and an AI summary back on the account timeline.

Keeping this page true

This connector was last tested end to end on 2026-08-27 against a live sandbox: fresh authorisation, an outbound write, an inbound read checked field by field, and the failure paths above triggered deliberately. It is re-tested every quarter and the date on this page changes when it is. Read how we test integrations, or see what is shipping today.

See a live quote draft built from a real RFQ

Fourteen days, no credit card, sample data pre-loaded. If it does not fit your shop, we will tell you in the first call.