Comparison
Keep Purview. It answers a different question.
This is not a replacement. Purview governs Microsoft 365 Copilot from inside Microsoft, and it is the only thing that can. Lyntway produces a record of it that holds up when the person asking doesn't work for you — and says, on every line, how we came to know it.
Sourced, not asserted
| microsoft, in its own words | lyntway | |
|---|---|---|
| Stopping a sensitive prompt in Microsoft 365 Copilot | “It prevents Microsoft 365 Copilot and Copilot Chat from returning a response when prompts contain sensitive data…”Purview DLP for Microsoft 365 Copilot ↗ | Cannot, and does not try. Nothing of ours sits in that path. This is Purview DLP's job; keep it. |
| Sitting inline in Microsoft 365 traffic | “Bypass Microsoft 365 domains from TLS decryption, traffic interception, deep packet inspection, and network packet and content filtering.”Microsoft 365 network connectivity principles ↗ | We don't, for the same reason. Anyone claiming to govern Microsoft 365 Copilot inline is describing a different product. |
| What the audit record holds | “These audit records contain details about which user interacted with Copilot, when the interaction took place, and where it occurred.”Audit logs for Copilot and AI applications ↗ | One signed receipt per prompt and per response, read afterwards from Microsoft's Graph export. It carries SHA-256 digests of the text and our own findings. It is marked attested, because Microsoft reported it and we did not watch it. |
| Copilot Studio agents | “This API doesn't retrieve interactions in agents created by Copilot Studio.”Graph interaction export ↗ | Point an agent's MCP servers and connectors at the gateway. Every call and result then crosses us, and the receipts are observed. Purview's audit log does list these agents, as metadata. |
| Before a Copilot Studio tool runs | “If the agent doesn't receive a decision from the system (either allow or block) within one second, by default, it proceeds to allow the tool to execute as planned.”Copilot Studio external threat detection ↗ | Allow or block on the inputs Copilot Studio proposes, answered well within that second, with an observed receipt of what was judged. This is in preview on both sides. Ours stays off until it has been exercised against a live tenant. |
| How long the record lasts | “You can retain audit logs for up to 10 years.” The 10-year option needs an add-on licence.Audit log retention policies ↗ | Receipts are sent to a log you control, so how long they last is your decision. Checking one needs no account with us. |
Only Purview
- Stops a prompt inside Microsoft 365 Copilot before Copilot answers it. Microsoft describes the prompt control as “in preview and … rolling out to all tenants”. DLP ↗
- Keeps labelled files and emails out of Copilot's answers. In Microsoft's words, “the content of the item isn't used in the response or accessed by Copilot.” DLP ↗
- Records the files, sites and emails Copilot touched to write each answer, with their sensitivity labels. Audit ↗
- Lists Copilot Studio agents in the audit log, which Graph's export leaves out. Audit ↗
What Lyntway adds
- A signature over every record (Ed25519 over the record's RFC 8785 canonical form). Anyone can check it offline against a published key.
- The source, written inside the signature. Observed means the bytes crossed us. Attested means Microsoft reported them. A reader can tell which is which.
- Detection by our own rules on Copilot's prompts and responses. The findings are ours, and the receipt says so.
- The rest of your AI, on the same record: every model, MCP tool and API you route through us, not only Microsoft's.
“Set a lock on your Log Analytics workspace to block all activities that could delete data… However, keep in mind that this lock can be removed. If you need a fully tamper-proof solution, we recommend you export your data to an immutable storage solution”Microsoft Learn · Secure your Azure Monitor deployment ↗
That is not a criticism of Microsoft. It is Microsoft's own guidance for the workspace where audit data usually ends up, correctly describing what a log is for — and pointing elsewhere for the other thing.
When your customer's auditor asks you to prove that log wasn't edited — what do you hand them?
If the answer is “the log”, the auditor is being asked to trust your vendor. Sometimes that's fine. When it isn't, that's what we're for.