Simple Council · Simple Intelligence Group

Show me the test. Not the slide that says it was tested.

Simple Council is the evidence layer for Microsoft Agent 365. You register every AI agent your organization runs, adopt the framework you answer for, and Council fans its controls out onto each agent. Your team captures evidence against those controls, hashed and chained so a change after the fact shows. When the examiner arrives, an administrator exports the pack: a machine-readable envelope, a printable report, and the integrity check that proves the chain held. Signed in with Microsoft Entra.

One thing to remember: Council is where an AI agent's controls are adopted, evidenced and proven.

Council never competes with Agent 365. It is the place the evidence an examiner asks for is kept, chained and handed over.

The slide is not the evidence

What does Simple Council add to Microsoft Agent 365 and Purview?

Council adds the registry you answer for, the framework's controls fanned out onto every agent, and the hash-chained evidence trail per control, which neither Agent 365 nor Purview produces. Your agents are already inventoried in Agent 365, and with the licensing Microsoft names for it, your Conditional Access policies can already target them. What they cannot tell you is whether the agent that touched a client record stayed inside the controls you adopted this quarter, what evidence says so, and what you can hand the examiner when they ask. That gap is where your name ends up on an incident.

Every quarter without an evidence pack is a quarter you will reconstruct from logs under pressure.

How it works, mechanically

How is evidence captured against each agent?

Four steps, each one written down. Here is the whole path from an agent nobody had listed to a pack an examiner can read.

1

One registry, every agent.

Register each agent by form, by JSON import, or by the pull from your Microsoft Agent 365 registry once your operator configures it: the Copilot Studio ones, the custom ones, the one another team's platform runs. Each entry carries an owner, a status and the people allowed to see it. Every status change lands in the audit log, and the continuous-evidence sweep snapshots each control's status on its cadence.

2

Blueprints fanned out onto every agent.

Adopt the framework you answer for (ISO 42001, HIPAA, NIST AI RMF, FFIEC, CMMC Level 2, or the EU AI Act high-risk obligations) and Council fans its controls out onto every agent in scope, so each agent carries a status for each control: compliant, exception, remediation or pending.

3

Evidence, hashed and chained.

Capture evidence against each control: attestations, configuration snapshots, log reviews, access reviews, drill records. Every row is hashed and chained to the previous row for the same agent and control, so a trail edited after the fact shows the break instead of hiding it.

4

The pack an examiner can read.

An administrator exports a machine-readable envelope, a printable report and a ZIP that carries both, with an integrity section that lists every break in the chain or confirms there are none. The window defaults to ninety days and widens to two years. Every export is itself written to the audit log.

The one thing to remember: Council is where an AI agent's controls are adopted, evidenced and proven.

Built on Microsoft, dated

How does Council fit Microsoft Agent 365, Purview and the EU AI Act?

As of May 1, 2026, Microsoft Agent 365 is generally available for the Commercial segment (Microsoft Learn, Microsoft Agent 365 overview, read November 2, 2026), and Microsoft Purview's audit, data security posture management, DLP, Insider Risk Management, eDiscovery and Compliance Manager are supported for Agent 365 agent instances (Microsoft Learn, Purview for Microsoft Agent 365, page dated May 1, 2026, read November 2, 2026). Council is designed to read your Agent 365 registry: the pull is built, your operator configures it, and it lists the agents in your tenant's registry through Microsoft Graph in the global cloud. Council leaves runtime blocking to Microsoft on purpose; what it adds is the framework adoption, the evidence chain per control and the pack those controls do not produce. The EU AI Act's obligations for high-risk systems are one of the six blueprints; the evidence pack is the record a firm will be asked for.

What will be working after two weeks

Your agents registered, by form or by import, each with an owner. One blueprint adopted for your industry and its controls fanned out onto every agent in scope. The first evidence rows captured and chained against the controls your examiner names first. The first auditor pack exported, with the chain verified. Provenance visible on every assessment answer the AI drafted and a person saved.

What this does not do yet

Council does not block or stop an agent at runtime; that stays with Microsoft, by design. Your policies are enforced on Council's own tool path only: a call into Council that names a registered agent runs through them, and nothing else does yet, so an agent's own actions in your tenant are not passed through a Council policy. The AWS Bedrock and Google Vertex connectors are not wired; those agents are registered by form or import. There is no approver role: the Inbox lists a held decision and its clock, but nobody can answer a hold inside Council yet, there is no multi-party approval, and evidence is captured by people. It is not an analyst-rated governance platform and claims no certification; readiness evidence is what it produces. There is no native PDF: the report prints from your browser.

Why a regulated firm picks it

Why does a regulated firm pick Simple Council?

The evidence chain is per agent and per control, hashed so a change shows, which a registry alone never gives you. Blueprints for the frameworks your examiner already names, so the first week is tuning, not authoring. Provenance on every AI-written row. The evidence lives in your workspace behind Microsoft Entra sign-in. It never competes with Agent 365, so there is nothing to rip out when Microsoft ships the next control. And the price is a flat amount per workspace, without a consumption meter you have to forecast.

You lose nothing by signing in: the pack you download is a file you keep.

What travels with the pack

What is in an evidence pack, and what else is recorded?

The pack carries every relevant row: the agents, the adopted blueprints, each agent's status per control, the evidence rows with their hashes, the maturity assessment scores, and the integrity section. Policies travel with it too: the rules you wrote down for how an agent call should be treated when it touches protected data (block, route, escalate, or allow with audit). Today they are enforced on one path: a tool call into Council that names a registered agent runs through your policies first, and a block, route or escalate outcome refuses the call and writes the decision beside the evidence. A quarterly pack for business reviews is generated from the same rows.

Provenance is on every AI-written row: whether it was generated by AI, how confident the model was, and the reasoning it gave, so the examiner can tell a machine-drafted assessment answer from a human one. Cost sits beside it: token spend per agent, with the budget alerts you set. What you lose without this is the quarter you spend rebuilding it from logs, and the examiner's question about which answers a person actually wrote.

Questions buyers ask

Does Simple Council replace Microsoft Agent 365?

No. Agent 365, generally available for the Commercial segment since May 1, 2026 per Microsoft Learn, is the registry and the runtime control. Council adds framework adoption, the hash-chained evidence per control and the auditor pack those controls do not produce.

Can Council stop an agent at runtime?

No, by design. Runtime blocking stays with Microsoft. Your policies are enforced on one path today: a tool call into Council that names a registered agent runs through them first, and a block, route or escalate outcome refuses the call and records the decision.

What is in the evidence pack?

A machine-readable envelope with every relevant row, a printable report, and a ZIP that carries both, with an integrity section that lists every break in the hash chain or confirms there are none.

Where is the evidence stored?

In your Simple Council workspace, isolated per workspace, behind Microsoft Entra sign-in. The pack you download is a file you keep.

Which frameworks come with Council?

ISO 42001, HIPAA, NIST AI RMF, FFIEC, CMMC Level 2 and the EU AI Act high-risk obligations, as blueprints you adopt and tune.

Council is where an AI agent's controls are adopted, evidenced and proven.

Access is granted one organization at a time. Start trial takes you to sign-in with the Microsoft account your organization already uses; if yours is not yet approved, the page you land on lets you apply for early access. If you would rather talk first, a person answers.