Mike.ai

Integration blueprint

The low-friction route into Microsoft and DMS workflows.

Regional law firms do not need a giant integration programme to judge value. The first useful step is a permissioned, audited matter-folder import contract that turns existing SharePoint or OneDrive structure into Mike.ai source metadata, review queues and ROI evidence.

Blueprint only. No Microsoft admin consent, mailbox import, DMS connection, private document body storage or external send is enabled.

View command centre Build source mapCreate pending workspace

Step 1

SharePoint/OneDrive matter-folder map

release candidate

Step 2

Outlook evidence pack import

planned

Step 3

DOCX reviewed-output export

planned

SharePoint/OneDrive matter-folder map

Lets a property team point Mike.ai at a known matter-folder structure without changing the practice-management system.

release candidate

Implementation

  • Capture tenant id, site id, drive id, folder path, matter reference pattern and allowed file classes as metadata.
  • Import file names, extensions, modified time, size, checksum placeholder, owner, folder lane and source requirement mapping.
  • Keep raw document bodies disabled until retention, deletion, Access and source-vault approvals pass.

Controls

  • Owner/admin approval required before any folder mapping is activated.
  • Every imported metadata record is workspace-scoped and matter-scoped.
  • Import failures create visible queue rows rather than silent skips.

Outlook evidence pack import

Captures completion-critical email evidence only after the folder import pattern proves value.

planned

Implementation

  • Start with selected thread metadata and attachment inventory, not mailbox-wide ingestion.
  • Use reviewer-selected threads and explicit matter mapping.
  • Separate external client emails from internal work product in the source hierarchy.

Controls

  • Mailbox import requires separate admin consent and user notice.
  • External sharing policy must block accidental client-data export.
  • Sensitive email body storage remains disabled until the private-source gate is approved.

DOCX reviewed-output export

Gives partners and fee earners a familiar Word handoff while preserving citations, reviewer status and export locks.

planned

Implementation

  • Generate DOCX-ready structured sections from approved review rows.
  • Attach source map, missing-evidence list, reviewer actions and export-lock status.
  • Keep external export blocked while high-risk review items remain open.

Controls

  • Reviewer approval required for external-use exports.
  • Export package records audit event, version label and destination intent.
  • Output states never represent unsupported legal advice as approved work.

Acceptance evidence

Integration blueprint route is public and describes the boundary honestly.

Internal v3 keeps Microsoft/DMS as blueprint/planned until live admin consent and connector tests exist.

Benchmark scorecard describes the Microsoft/DMS gap without claiming Harvey parity.

Clean commercial domain exposes the blueprint at `/integrations` through host-aware routing.