Outlook and Microsoft 365: the answer you need before a trial
No, not today. The Outlook mailbox and Outlook calendar clients are fully written and Outlook is a first-class provider in the code, and on the production service the Microsoft credentials are not configured, so there is nothing to connect to. The equivalent Google endpoint, running in the same process on the same day, does open. We would rather publish that asymmetry than let you find it during an evaluation.
Not connected. The Outlook mail and Outlook calendar clients are written, and the connection is not open on the production service. There is nothing you can connect today.
Last verified October 5, 2026. All integrations
What moves, and which way
None available. The OAuth flow exists in the code and has no configured application behind it in production.
- Into SAGARIS
- Nothing, today. No Outlook mail syncs into the SAGARIS inbox and no Outlook calendar free and busy time is read, so nothing on the Microsoft side is visible to the record or to the agents that act on it.
- Back into Microsoft 365
- Nothing. SAGARIS sends no mail from an Outlook mailbox and creates no events on an Outlook calendar. The booking flow and the AI receptionist write against a connected Google Calendar; with no calendar connected they have nothing to write against at all.
- The boundary
- Built is not the same as available, and this page exists to keep those two apart. The code being present means the work to open this is smaller than starting from nothing; it does not mean a switch exists that we are choosing not to flip for you, and it does not come with a date, because none is scheduled. If you run Microsoft and a connected mailbox or calendar is a hard requirement, SAGARIS does not meet it right now.
What teams on Microsoft actually do in the meantime
The most common answer is a Google mailbox and calendar for the reps who live in SAGARIS, connected per person, with Microsoft continuing to run everything else. That is a real operational cost and we are not going to pretend it is not, but it is a decision you can make with open eyes rather than a surprise in week two.
For the calendar specifically, the thing that breaks without a connection is automatic booking: an AI receptionist that cannot read free and busy time cannot offer a slot safely, so it takes the message and escalates instead of booking. That is a real downgrade in the most valuable part of the inbound flow, and it is the reason this is worth settling before a trial rather than during one.
For mail, the public REST API is the general-purpose path: a workspace key you mint and revoke, documented operations, and an automation tool or script of your own on the other end. It is not a mailbox connection and we will not describe it as one, but it is a real, authenticated surface if you want activity moving between SAGARIS and something we do not connect to.
If this is the blocker for you, tell us. Knowing which specific half matters, mail or calendar, and how many seats sit behind it, is what would move it up a roadmap. We would rather hear it from you before you buy than build in the dark.
How we checked
Probed on the production service at app.sagaris.ai. GET /api/calendar/microsoft/connect answered 503 with the body "Microsoft 365 Calendar OAuth is not configured on the server." The paired control was the identically shaped GET /api/calendar/google/connect in the same process on the same day, which answered 401 Unauthorized, past its own 503 guard: so the service is up and the route is reachable, and the difference between the two answers is one credential. The same probe settles the mailbox, because src/lib/microsoft-calendar/oauth.ts falls back to OUTLOOK_MAIL_CLIENT_ID when MICROSOFT_CALENDAR_CLIENT_ID is unset, so a 503 proves neither value is present. This status was first measured on September 18, 2026 and re-probed on October 5, 2026 with the same result.
Verified October 5, 2026. If this is out of date or wrong, email founders@sagaris.ai and we will correct it and move the date.
Microsoft 365 and SAGARIS, the questions people actually ask
- MOST ASKED
No, not today. The Outlook mailbox client is written and Outlook is one of the two providers the OAuth connect flow is built for, and the Microsoft credentials are not configured on the production service, so there is no connection to open.
No. The Microsoft calendar client exists and is not configured in production. The booking flow and the AI receptionist write against a connected Google Calendar.
No date is published, because none is scheduled, and publishing one we could not keep would be worse than this answer. If it is the blocker for you, email founders@sagaris.ai and say which half matters and how many seats are behind it. That is the input that moves it.
Because the Google application is configured on the production service and the Microsoft one is not. Both clients are written. The two connect endpoints are the same shape and run in the same process, which is how we can state the difference this precisely rather than guessing at it.
No, and it is a separate question from mail and calendar. There is no Teams notification channel and no Teams meeting connection you can turn on. Slack is the only chat destination SAGARIS delivers notifications to, and that is one-way delivery rather than an app.
Mail from your Outlook mailbox does not appear on the SAGARIS timeline, replies are not sent from that address, and nothing can be booked automatically because no calendar can be read. The dialer, the CRM, SMS and the AI coach are unaffected.
Next door