LegalVoice LegalVoice
Get started
Outlook Email logoConnects LegalVoice to a firm-configured Outlook Email account. No official partnership is implied.

Outlook Email integration · Microsoft mailbox sending available

Connect LegalVoice to Outlook Email with explicit data and workflow boundaries.

LegalVoice can send configured intake, consultation, document, and staff follow-up email through a firm-connected Microsoft 365 mailbox. Available sender and shared-mailbox behavior depends on the tenant, account permissions, and mail scopes granted by the firm.

Review your Outlook Email workflow About LegalVoice
A business team collaborating around a shared workflow in a modern office. Make intake operational
Photo by Vitaly Gariev on Unsplash
What the Outlook Email workflow supports

LegalVoice describes only the actions supported by the configured Outlook Email path. Availability still depends on the firm’s account, permissions, field mappings, and enabled workflow.

  • Connect a Microsoft 365 mailbox through the approved OAuth flow.
  • Send configured caller confirmations, links, and follow-up messages.
  • Use supported shared-mailbox sending when the tenant grants the required permission.
  • Record send results and provider errors for staff review.
What data is exchanged

The connector should move only the fields required for the approved intake or follow-up action and preserve provider identifiers and result states for review.

  • Approved sender mailbox and recipient addresses.
  • Configured subject, branded body, links, and permitted attachments.
  • Call, intake, consultation, or workflow reference.
  • Microsoft message result and failure context.
How to configure Outlook Email

Begin with the narrowest useful connection, test it with controlled records, and enable additional actions only after the firm reviews the result.

  • Connect the firm’s Microsoft 365 account.
  • Grant required mail scopes and configure any shared mailbox.
  • Review sender identity, templates, attachments, recipient rules, and fallback behavior.
  • Send controlled test messages before enabling live follow-up.
Known limitations and review boundaries

A connected credential is not blanket permission to read or write every record. Provider success, partial success, and failure must remain visible to staff.

  • Send and shared-mailbox capabilities depend on Microsoft tenant policy and granted scopes.
  • LegalVoice should promise delivery only after the Microsoft send result succeeds.
  • The connector does not imply unrestricted access to the firm’s mailbox or message history.
Example Outlook Email workflow

This example shows the operational sequence without using customer data or promising that every firm uses the same configuration.

  • A caller or staff workflow selects email delivery.
  • LegalVoice prepares the approved message using the firm’s identity and content rules.
  • The connected Microsoft mailbox sends the message.
  • The delivery result remains attached to the intake or consultation record.

checklist

Outlook Email launch checklist

Confirm these items before enabling the integration for production records.

Account owner Name the firm administrator responsible for the connected account and provider permissions.
Authentication Connect the firm’s Microsoft 365 account.
Data map Approve the exact objects, fields, provider IDs, and source-of-record rules.
Allowed actions Enable only the read or write actions the firm has approved and tested.
Failure handling Define who reviews rejected, partial, duplicate, expired-token, and permission-denied results.
Controlled verification A caller or staff workflow selects email delivery.

Written by LegalVoice Editorial Team. Reviewed by LegalVoice Product and Engineering Review. Published 2026-08-23; updated 2026-08-23.