Microsoft 365 and Outlook agent

How it works

1. 01

   Connect Microsoft 365 or Outlook.com

   OAuth into your work or personal Microsoft account in under a minute. Helix uses the Nylas v3 connector — the same plumbing thousands of production email apps already use against Microsoft Graph.

2. 02

   Pick a template and calibrate tone

   Drop in a stalled-deal chaser, recruiter coordinator, or lead qualifier. Tone, approval rules, and scopes are bound to the identity — not to the mail provider — so the agent reads the same on Outlook as it does on Gmail.

3. 03

   Drive it from any MCP client

   Point Claude, ChatGPT, Cursor, or n8n at the Helix MCP endpoint. Outbound sends and calendar writes queue for approval; the audit log captures provider, identity, and approver per action.

In plain prose

Microsoft 365 has been the email backbone for roughly half of large enterprises for a decade, and yet most "AI inbox" products ship Gmail-first with an Outlook preview months behind. Helix treats the two providers as peers — the same agent identity reads availability, drafts replies, and queues sends regardless of which side of the Microsoft-Google line the mailbox lives on.

The mechanics matter. Microsoft Graph has its own quirks — shared mailboxes, delegated access, retention labels, Information Protection sensitivity tags — and Helix inherits Nylas v3's production handling for all of them. Tokens refresh on their own; revoked grants surface in the dashboard; per-identity scopes mean the agent never sees more of the tenant than it needs.

For regulated buyers, the audit log is the answer to the "what did the agent do as me last week" question. Every send, calendar write, and approval decision is captured with identity, approver, and timestamp, and the data is exportable for compliance review.

FAQ