AgentsThe story, in brief

Microsoft Moves AI Governance From Policy to Runtime Enforcement

Microsoft shifts AI governance from the policy layer to runtime: nine domains, four functions, continuous enforcement as agents operate in production.

Illustration of independent geometric mechanisms passing paper tasks along branching amber tracks.
AI agents and the coordination of work.AI illustration by KeyNews
The KeyNews take

Why it matters

As agents move into production workflows, governance can't be a pre-deployment checklist — it has to happen live. Microsoft's architecture (policy + runtime enforcement + continuous eval + audit) is the infrastructure that makes agentic deployments auditable and compliant at scale.

The key facts

12 to know
  1. Nine governance domains outlined

  2. Four governance functions: policy, control, visibility, proof

  3. Runtime enforcement (not just pre-flight policy)

  4. Continuous evaluation and observability during operation

  5. Identity, security, and audit evidence as first-class components

  6. Designed for production agents and AI applications

  7. Published August 2026 — current architecture guidance

  8. Four core functions: policy, control, visibility, proof

  9. Runtime enforcement tied to policy

  10. Continuous evaluation and observability as core components

  11. Identity, security, and audit evidence integrated

  12. Focus on production agent operation and verification

Go to the source

InfoQ AI/MLinfoq.com

Publisher excerpt: Microsoft has outlined an AI governance architecture spanning nine governance domains and four functions: policy, control, visibility, and proof. The approach connects policies with runtime enforcement, continuous evaluation, observability, identity, security, and audit evidence to help…
Read original report
Back to today's editionMore agents news

Keep reading

Related stories

More from Agents