Enterprises standardised on Microsoft 365 expect the platform to handle Outlook the way Google-standardised enterprises expect Gmail support : email send, mailbox query, attachment handling — all without leaving the platform's permission perimeter. The previous Outlook integration sat on the legacy EWS authentication path, which Microsoft has flagged for retirement and which fails the modern conditional-access policies most enterprises now enforce.
This release moves Outlook to Microsoft Graph with OAuth 2.0 and MSAL bearer-token flows — the same authentication shape Microsoft's own client applications use. Outlook now sits as a peer to Gmail and Google Calendar in the platform's unified cloud-connector protocol ; application code that sends email through the connector targets Outlook or Gmail by configuration, not by call-site selection.
- Email send. Plain-text and HTML body, multiple recipients with TO / CC / BCC, attachment upload up to the Graph 4 MB inline / large-attachment threshold.
- Thread-based message retrieval. List messages by conversation ID, retrieve the full thread with reply-chain preserved.
- Attachment handling. Inline attachments (images embedded in HTML) and standard attachments handled symmetrically with Gmail.
- OAuth 2.0 + MSAL. Bearer tokens fetched and refreshed through MSAL ; conditional access, MFA and tenant restrictions enforced by Microsoft Entra without platform-side workarounds.