Skip to content
LYVOR DE

Lyvor›Integrations›Microsoft 365

Integration · documented · in live use with a customer since July 2026

Microsoft 365: what has actually been tested.

This page is written for the person who asks the technical questions before rollout. It describes the documented status — checked on 08/20/2026 — and states what is not available today.

What it does

Inside the existing inbox — no new system.

01

Read and classify

Incoming emails in the agreed inbox are read, classified by topic, and urgent cases are flagged. Attached PDFs are read as well.

02

Assign and structure

Emails are assigned to cases and properties; categories and flags appear directly in the inbox.

03

Create drafts

Reply and forward drafts are created as regular drafts in the inbox — where your team reviews, edits, and sends them.

04

Follow up

Follow-up reminders ahead of deadlines, status tracking in the case, reminder drafts for anything missing.

Permissions & data flow

Your tenant stays your tenant.

Where the data lives

Your inbox and your emails stay in your own Microsoft 365 tenant. Lyvor’s system components run on servers in Germany.

What is sent for AI analysis

Only pseudonymized content: names, addresses, and contact details are replaced by placeholders beforehand; its effectiveness is checked on an ongoing basis. Covered by a data processing agreement (DPA); the list of service providers is disclosed in the DPA.

Scope of access

Access covers the agreed inbox and the agreed operations — verifiable by your IT provider before anything runs.

Limits

Just as important: what does not happen.

01

No automatic sending

Sending is done by people in Outlook. The documented mode is draft-for-approval; there is no automatic send path — the internal send endpoint is not implemented and responds with an error status.

02

No rule changes

Inbox rules, forwarding settings, or permissions are not changed unilaterally.

03

Not available today

Google Workspace/Gmail, IMAP/SMTP, and ERP/document management integrations are not built and not available to order. There is no “works with every inbox” promise.

04

No setup without review

Every rollout begins with a review of the inbox, process, and limits — personally guided, not a self-service installation.

Check the setup — with your IT team involved.

A short review is enough to answer whether your inbox and your requirements fit the documented status. Technical questions are answered by the person who builds the system.