Microsoft 365 integration — sign-in and Outlook email

The Microsoft 365 integration covers two surfaces: signing in, and each rep’s own Outlook mailbox.

What it does

Sign in with Microsoft. Team members log in to Oneop with their Microsoft account — one password fewer to manage.

Per-rep Outlook email. Each rep connects their own Microsoft 365 / Outlook mailbox in one click via OAuth (XOAUTH2). Outbound one-to-one email and sequence steps send from the rep’s real mailbox rather than a shared platform address, and inbound mail is polled every minute, threading replies back onto the deal or contact. This is on by default.

What syncs, in which direction

• Bi-directional: Outlook mail send and receive, per user.
• OAuth tokens are stored per user and refreshed automatically; stored credentials are encrypted with AES-256-GCM.

Setup

Each user connects from their own settings via the Microsoft consent screen. No tenant-wide admin grant is required for individual mailboxes.

What it does not do

State this plainly, because it is the question Microsoft shops ask first:

• No Outlook / Microsoft calendar connection. Calendar-aware booking currently works with Google Calendar only. If a booking workflow against an Outlook calendar is essential, Oneop does not do it today — the roadmap is public and dated.
• No SharePoint or OneDrive integration. Microsoft Teams is a separate, much narrower thing: Oneop can post outbound notifications to a Teams channel via an incoming webhook — see the Microsoft Teams integration — but connecting Microsoft 365 here does not connect it, and Teams is not a chat channel.
• Mail sync covers the connected mailbox’s send/receive for CRM purposes — it is not a full mailbox client replacement.

Related module and plan notes

Per-user email accounts are on for every plan. Sequences ship in every workspace, entitled from Starter and above — but nothing sends until a rep connects their own mailbox. See CRM and Sequences.