Platform and integration ยท Coming soon
SimpleFlow

SimpleFlow
The checker and approval layer over the agents and workflows your team builds in Copilot Studio.

For Platform and governance leads at organizations whose teams build agents and workflows in Copilot Studio, and who have to answer for what those agents are allowed to do.

Microsoft now lets a team build agents, workflows and apps in one place, and the number of them in a tenant grows faster than anyone can review. The question is no longer how to build one. It is which ones are allowed to run, against which rules, with whose approval, and where the record of that decision lives. SimpleFlow is being designed as that layer: it does not design the workflow, it checks it.

Replaces Reviewing automations by reading them An approval buried in a chat thread A spreadsheet of who approved which agent
Web Planned Copilot Planned

When you can get SimpleFlow

Coming soon

Not open yet. Tell us where to send word when it is.

What you can do now

Get product updates

None of these creates an account, a trial, or access. Each one records what you asked for so a person can answer it.

Where this stands

Availability
Coming soon

What it costs

Pricing is shared when access is set up.

Routes that are not open

  • Direct trial with Simple Intelligence Not open yet
  • Direct subscription from Simple Intelligence Not open yet
  • Microsoft Marketplace listing pending Not published yet
  • Sponsored subscription for member companies Not open yet

The design surface is Microsoft's now. What is left to build is the check.

A team can build an agent, a workflow and the app around them in one Microsoft system, and that system decides for them whether a problem wants a workflow or an agent. Building a second canvas beside that would be a canvas nobody asked for. What nobody has yet is the layer that reads what each of those agents is allowed to do, compares it with the rules the organization wrote, and makes a person sign the ones that cross a line. That is the whole of what SimpleFlow is being designed to be.

A check is only worth having if the approval and the evidence are one record.

The design hands every decision to Simple Council: which agent, which version, which rule it tripped, who approved it and when. An approval that lives in a chat thread is not evidence a reviewer can use. An approval bound to a version, in a hash-chained record, is.

It runs nothing, which is the point.

SimpleFlow is designed to hold no runtime of its own. The agents and workflows run where Microsoft runs them. The checker reads their definitions and their allowed actions, decides, records, and gets out of the way. A product that does not execute anything cannot be the thing that executed something it should not have.

Who this is being built for.

Forty agents in the tenant, four people who can approve one

Platform lead at an organization building in Copilot Studio

The intended shape: each agent and workflow a team publishes is read by the checker, the ones that touch a system or a data class on the rules list go to the named approvers, and the rest pass with a record that they were checked.

The auditor asks who approved the agent that sends mail

Governance or compliance lead

The answer is designed to be one record in Simple Council: the agent, the version, the rule, the approver, the date. Not a search through a chat.

A workflow changed after it was approved

Security reviewer

The approval is designed to be bound to a version. A new version is a new check, and an old approval does not carry over to actions it never covered.

How it is designed to work.

1

You write the rules once

Which systems an agent may touch, which data classes need a person, which actions are never automatic. The design keeps these as rules a reviewer can read, not as code.

2

The checker reads what each agent is allowed to do

From the agent's or workflow's own definition as Microsoft exposes it, the checker is designed to derive the actions, connections and data it can reach, and to compare that with the rules.

3

A person approves where a rule says so

The ones that cross a line are routed to the named approvers. The approval is bound to the version it was given for.

4

The record lands in Simple Council

Every check, every approval and every refusal is designed to be written to Council's evidence ledger, so there is one governance record rather than one per tool.

Design decisions worth knowing about.

Nothing on this list is available today. This is the product we intend to build, written down so you can tell us whether it is the right one, and it will change.

Read the 3 capabilities in detail

No canvas of our own, and that was a decision with the reasoning recorded

The earlier SimpleFlow was an integration platform with its own runtime and authoring surface. On 18 November 2026 that was retired in favour of the checker, because the design surface and the runtime are Microsoft's and a second one would compete with them for no gain to the buyer.

The approval is bound to the version

An approval that is not tied to what was approved is a signature on a blank page. The design binds each approval to the agent or workflow version it was given for, so a change is a new decision.

The evidence belongs to Council, not to this product

SimpleFlow is designed to write into Simple Council's ledger rather than keep a ledger of its own, so a reviewer has one place to look.

What is designed to sit where.

Read the 3 architecture notes

The agents and workflows, where Microsoft runs them

Built in Copilot Studio and run on the runtime Microsoft provides for them. SimpleFlow changes nothing about where they live.

The checker, in our service

A multi-tenant service on Azure, signed into with the customer's own directory, holding the rules, the checks and the routing to approvers. Target design, not a running system.

The record, in Simple Council

Checks, approvals and refusals are designed to be written to Council's hash-chained evidence ledger.

What it is built on.

A name here is a system this product is built to work with, not a promise that the connection is live in your tenant. Where a connector carries a status label, that label is the current state. Anything that needs its own vendor registration, its own consent, or its own approval says so, and nothing on this page can be taken as available until it is confirmed for your tenant.

Show the integrations by group

Microsoft platform this is designed around

Microsoft Copilot Studio Microsoft Entra ID Azure Key Vault Azure Monitor and Log Analytics

Simple Intelligence products it feeds

Simple Council (evidence ledger and policy engine)

Reading data from an external system is not a way to sign in. Customer identity stays with Microsoft Entra ID, and no data source on this list authenticates a person.

Where this stands.

SimpleFlow is a decided scope and nothing more, as of 18 November 2026, with no customer environment available. An earlier build under this name, a multi-tenant integration platform with its own per-tenant runtime, was stopped and is not what this page describes. The checker is designed to be built after the five production products launch, and no part of it has been run for a customer.

Working today

  • A decided scope, recorded on 18 November 2026: the checker and approval layer over Copilot Studio agents and workflows, feeding Simple Council
  • The governance record it is designed to write into already exists: Simple Council runs in production with its policy engine and hash-chained evidence ledger
  • The rules of the portfolio it is built to: an agent drafts, a person approves, and the approval is bound to what was approved

Not yet

  • Nothing of the checker is built. There is no code, no environment and no date.
  • The reading of a Copilot Studio agent's definition and allowed actions depends on what Microsoft exposes for that purpose, and that has not been verified against Microsoft's documentation for this design.
  • Which rules can be expressed, and how a rule maps to an agent's allowed actions, is not designed yet.
  • There is no purchase route, no listing, and no price.
  • No certification is held.

Verified against the product on 2026-11-18.

Where each statement on this page comes from.

SimpleFlow is the checker and approval layer over Copilot Studio agents and workflows, and designs nothing of its own.
In the build A founder decision of 18 November 2026 retired the earlier integration platform and set this scope. This page describes that scope and nothing built. Checked 2026-11-18
Nothing of the checker is built.
In the build As of 18 November 2026 there is no code, environment or date for the checker. Checked 2026-11-18
The record lands in Simple Council.
In the build Simple Council runs in production with a policy engine and a hash-chained evidence ledger. The checker's writes into it are a design, not a built integration. Checked 2026-11-18
Storage posture
Persistent (Cosmos DB HPK)
Certification target
M365 Cert Tier 3
Distribution
Azure Marketplace (planned)
Status
Coming soon
Industries

What a platform team asks first.

Does SimpleFlow build or run workflows?

No. The agents and workflows are built in Copilot Studio and run where Microsoft runs them. SimpleFlow is designed to check them against your rules, route the ones that need a person, and record the decision.

What happened to the integration platform that used to be on this page?

It was retired on 18 November 2026. The design surface and the runtime are Microsoft's, and a second one would have competed with them for no gain to you. What survives is the check, the approval and the evidence, which is what this page now describes.

Can we have it?

Not yet. Nothing is built, and the checker is designed to be built after the five production products launch. "Get notified" on this page is the only action, and it creates nothing.

How does this relate to Simple Council?

Council is where the record lives. SimpleFlow is designed to write every check and approval into Council's ledger rather than keep a second one.

What does it cost?

No price is set and nothing can be bought.

What it sits next to in the portfolio.

SimpleFlow is designed to be the check beneath the suite rather than another application in it: the agents and workflows a customer builds in Copilot Studio are checked against rules and approved by a person before they act, and the record goes to Simple Council.

Delivered with Simplicity IT

Simplicity IT prepares the tenant and the Foundry agents the runtime will host.

Simple Intelligence Group builds the product. Simplicity IT Inc. is a separate legal entity that provides services under its own agreement.

The useful conversation right now is about your rules.

If your teams are building agents in Copilot Studio, the thing worth writing down is which systems and data an agent may touch without a person, and which never. That list is what the checker is designed to read.

Availability Get product updates