Honest framing#
Microsoft Agent 365 went generally available on May 1, 2026 as Microsoft's control plane for AI agents. It assigns each agent its own Entra identity, applies Purview labels, governs runtime behaviour through Defender, and extends Intune device management to local agents on Windows. For organisations whose data, identity, devices, and security already run on Microsoft's stack, Agent 365 is a coherent and powerful choice.
LumenFlow is not trying to replace Agent 365 in those accounts. It is trying to be the answer for everywhere else.
Where Agent 365 is strong#
| Strength | What it means |
|---|---|
| Microsoft estate depth | Entra identity per agent, Purview labels, Defender for Cloud Apps, Intune device management — these are real, integrated, and supported |
| Distribution | Agent 365 ships into accounts that already have Microsoft 365, M365 E5, and Defender |
| Lifecycle controls | Agent registry, lifecycle posture, and DLP-style controls inside the suite |
Where LumenFlow differs#
| LumenFlow | Why it matters outside Microsoft estates |
|---|---|
| Stack-neutral Connections | Enrol any external runtime — laptop, server, CI runner, edge box — without an Entra dependency |
| Policy at the tool call | Rules evaluate every tool call before the side effect, not after-the-fact at job or process level |
| Signed, exportable Proof | Evidence bundles are detached-signed and verifier-checkable; Article 12 / NCSC log-protection requirements stay satisfied without exporting raw data into a Microsoft tenant |
| Bring-your-own-agent stance | LumenFlow governs agents you already run — Claude Code, Cursor, Aider, Continue, LangGraph, CrewAI, custom MCP — without forcing a runtime rewrite |
When to choose which#
Pick Agent 365 when:
- Your organisation is committed to the Microsoft estate
- Identity, device management, and DLP already run through Entra/Intune/Purview
- The agents you need to govern are predominantly Copilot-family or Copilot Studio agents
- You are comfortable with macOS and Linux being on Arc-attached parity rather than first-class
Pick LumenFlow when:
- You run on multiple clouds, or outside Microsoft entirely
- You need to govern third-party agents (LangGraph, CrewAI, custom MCP, OpenClaw-class runtimes) without rewriting them
- Your auditors or regulators want third-party-verifiable evidence bundles, not a tenant-bound audit log
- You have data residency requirements that prevent evidence from landing in a Microsoft tenant
The short version#
Agent 365 if you're all-in on Microsoft. LumenFlow everywhere else.
info See Connections: Trusted Compute for the trusted-compute pattern that lets governed AI work run on customer-owned compute, and Connected-Runtime Reference Bridge for the starter adapter that enrols an external runtime into LumenFlow.