Skip to main content

Email integrations

There are two email configuration paths: the curated Microsoft 365 Email connector and existing Konnie mailbox settings for Exchange, Gmail, and generic incoming/outgoing mail. They have different setup and action lifecycles. Do not configure both to process the same mailbox simultaneously.

Microsoft 365 Email prerequisites​

Your Microsoft administrator supplies an Entra application restricted to the selected Exchange Online mailbox. Reading/attachments require Mail.Read; sending requires Mail.Send. The Ennea operator supplies an eligible scoped managed worker and ingress configuration. You need connection-management permission and an explicit UTC import start.

Configure and test​

  1. Open the curated Microsoft 365 Email setup in Operations Studio → Integrations.
  2. Enter Microsoft tenant ID, client ID, mailbox ID, folder ID, import start, and client secret.
  3. Test the selected folder. Have the Microsoft administrator separately verify that an out-of-scope mailbox is denied.
  4. Enable only the required read, attachment, status, and draft/send capabilities and publish.
  5. Send an authorized test message to the selected folder and inspect intake and downstream state. Intake acknowledgement means saved input, not completed processing.
  6. Open a message or use Ask Konnie. Konnie resolves the saved source under current permissions; email content does not authorize business changes.

Before migrating a legacy mailbox, deactivate and drain its old worker. Review unfinished replies. Disable the Graph connection before reactivating the legacy path if rolling back. Multiple active connections in one Microsoft tenant require distinct mailbox identities; aliases do not prove distinct mailboxes.

Read attachments and send reviewed mail​

The connector provides bounded message/thread reads and supported downloads up to 10 MiB. TXT, CSV, text-bearing PDF, and XLSX can supply extracted evidence. Extraction has no OCR; a scanned PDF needs visual review. Download-only formats require a separate review. Downloads are not malware-scanned.

Konnie can create an encrypted review draft containing recipients, subject, body, and an operational or transactional purpose. This draft is in the integration worker, not an Outlook draft. Review and approve the exact outgoing content through the action flow. Marketing is rejected by this connector. Outbound attachments, Bcc, and HTML composition are not provided by this path.

Submitted means Microsoft accepted the send request. Sent can indicate a matching Sent Items record for a new message. Neither proves recipient delivery. Unknown requires reconciliation of the original send; do not resend blindly. Replies do not yet have independent Sent Items reconciliation.

Existing mailbox settings​

Open the relevant Exchange, Gmail, or SMTP/IMAP integration configuration. Set Konnie's address and allowed senders/domains. Supply the required provider configuration: Exchange authentication, Gmail OAuth, or generic incoming host/port/protocol/mailbox and outgoing SMTP host/port with authentication. Use the secure connection controls required by your mail administrator. Save and inspect authorization/configuration feedback and activity.

OAuth popups require deployment-specific callback setup. Expired or revoked authorization needs a refresh/reconnection using the available provider controls. An allowlist determines eligible senders; it does not grant them Ennea permissions.

Recovery​

Check selected folder and import start for missing messages, provider authorization for connection failures, attachment size/type for download failures, and downstream deliveries for processing failures. Preserve original source and invocation IDs when escalating. See Integrations, Approvals, and Support.