Outlook Calendar logoConnects LegalVoice to a firm-configured Outlook Calendar account. No official partnership is implied.

Outlook Calendar integration · Microsoft OAuth scheduling path available

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

LegalVoice can use a firm-connected Microsoft 365 calendar to check configured availability, create consultation events, work with supported shared calendars, and apply online-meeting handling. The firm controls account access, calendars, appointment rules, timezone, and meeting policy.

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

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

  • Read free/busy availability from the connected Microsoft calendar.
  • Offer returned consultation times under the firm’s scheduling policy.
  • Create confirmed events on supported user or shared calendars.
  • Request supported online-meeting behavior and preserve pending-link states.
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.

  • Client identity and approved contact details.
  • Appointment type, start and end time, timezone, duration, and consultation format.
  • Calendar owner, event description, location, and meeting instructions.
  • Microsoft event ID, meeting-link state, and booking result.
How to configure Outlook Calendar

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

  • Connect the approved Microsoft 365 account through the LegalVoice OAuth flow.
  • Select the user or shared calendar and grant the required calendar scopes.
  • Configure appointment types, timezone, duration, buffers, and meeting policy.
  • Test availability, event creation, and any Teams behavior before launch.
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.

  • Teams creation depends on Microsoft account type, tenant policy, and granted scopes.
  • A meeting link may be pending or require staff completion even when the calendar event succeeds.
  • Availability and shared-calendar behavior depend on the exact connected mailbox and tenant permissions.
Example Outlook Calendar workflow

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

  • A caller reaches the scheduling stage and LegalVoice checks the configured Outlook calendar.
  • The agent offers only returned times and confirms the caller’s consultation format.
  • The calendar event is created on the selected user or shared calendar.
  • LegalVoice records the event and meeting-link state for the caller and staff follow-up.

checklist

Outlook Calendar 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 approved Microsoft 365 account through the LegalVoice OAuth flow.
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 reaches the scheduling stage and LegalVoice checks the configured Outlook calendar.