{"slug": "microsoft-moves-ai-governance-from-policy-to-runtime-enforcement", "title": "Microsoft Moves AI Governance From Policy to Runtime Enforcement", "summary": "Microsoft has introduced an AI governance architecture that shifts from documented policies to runtime enforcement, continuous evaluation, observability, and audit evidence, spanning nine governance domains and four functions: policy, control, visibility, and proof. The framework, detailed in a Microsoft Tech Community blog post, combines Microsoft Foundry with services such as Microsoft Purview, Microsoft Entra ID, Defender, and Azure API Management, and uses the AI Gateway to enforce authentication, token limits, quotas, and policy at runtime. Principal Cloud Advocate Anthony Bartolo stated, 'Your AI policy is not governance until production can prove it.'", "body_md": "Microsoft has outlined an [AI governance architecture](https://techcommunity.microsoft.com/blog/azurearchitectureblog/from-policy-to-proof-governing-ai-to-scale-human-ambition-and-machine-intelligen/4535137) that moves governance from documented policies toward runtime enforcement, continuous evaluation, observability, and audit evidence as organizations deploy AI applications and agents in production. The framework spans nine governance domains and four functions: policy, control, visibility, and proof, addressing the need to verify that governance requirements are enforced and observable during AI system operation.\n\nMicrosoft AI governance architecture (Source: [Microsoft Blog Post](https://techcommunity.microsoft.com/blog/azurearchitectureblog/from-policy-to-proof-governing-ai-to-scale-human-ambition-and-machine-intelligen/4535137))\n\nThe architecture treats governance as a continuous operational loop. Policies establish requirements and risk classifications, controls translate them into access and runtime rules, observability captures system behavior, and evaluations test quality and safety. Audit processes then turn operational telemetry into evidence for compliance and incident investigation.\n\n[Manasa T. Ramalinga](https://www.linkedin.com/in/trmanasa/), Cloud Solution Architect at Microsoft, [described](https://www.linkedin.com/posts/trmanasa_from-policy-to-proof-governing-ai-to-scale-activity-7485038327943942144-KBfX?utm_source=share&utm_medium=member_desktop&rcm=ACoAAArnikgBqzTxA9Y838-O55QUcB2McACIq94) the motivation in a LinkedIn post accompanying the architecture. She added that organizations moving AI workloads into production are re-architecting their foundational structures to build safer systems, rather than treating governance as an afterthought.\n\nOrganizations cannot scale what you cannot control\n\nMicrosoft identifies nine governance domains: policy, data governance, model governance, observability, evaluations, security, identity and access, audit and compliance, and agent governance. Runtime controls can span interactions among users, agents, models, tools, APIs, MCP servers, and enterprise systems.\n\nThe architecture combines Microsoft Foundry with services including Microsoft Purview, Microsoft Entra ID, Defender, and Azure API Management. Foundry's AI Gateway provides a runtime boundary for authentication, token limits, quotas, and policy enforcement. Microsoft also documents using the gateway to govern MCP tools, providing centralized authentication, rate limiting, IP restrictions, and audit logging without modifying MCP servers or agent code.[ Microsoft Foundry AI Gateway documentation](https://learn.microsoft.com/en-us/azure/foundry/configuration/enable-ai-api-management-gateway-portal?utm_source=chatgpt.com),[ Microsoft guidance for governing MCP tools](https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/governance?preserve-view=true&view=foundry&utm_source=chatgpt.com)\n\nEvaluations are positioned both before deployment and in production. Microsoft Foundry supports evaluation of AI applications and agents against datasets using built-in and custom evaluators, allowing teams to assess quality and safety before release and monitor production behavior afterward.\n\n[Anthony Bartolo](https://www.linkedin.com/in/wirelesslife/), Principal Cloud Advocate at Microsoft, [described](https://www.linkedin.com/posts/wirelesslife_aigovernance-responsibleai-aiagents-activity-7483501964157214721-OJtP?utm_source=share&utm_medium=member_desktop&rcm=ACoAAArnikgBqzTxA9Y838-O55QUcB2McACIq94) the operational distinction in a LinkedIn post\n\nYour AI policy is not governance until production can prove it. He outlined the loop as policy defining rules, runtime controls enforcing them, observability capturing behavior, evaluations testing quality and safety, and audit converting telemetry into evidence.\n\nAI governance lifecycle from policy and risk classification (Source: [Microsoft Blog Post](https://techcommunity.microsoft.com/blog/azurearchitectureblog/from-policy-to-proof-governing-ai-to-scale-human-ambition-and-machine-intelligen/4535137))\n\nThe approach is broader than a Microsoft-specific control plane. The[ NIST AI Risk Management Framework and Generative AI Profile](https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence) provide a vendor-neutral framework for managing AI risks across the lifecycle, including governance, measurement, evaluation, and risk mitigation. Microsoft's architecture maps those governance concerns into concrete platform controls and operational telemetry.\n\nAgent governance adds controls around agent identity, access, activity, and workflow checkpoints. Microsoft's open-source[ Agent Governance Toolkit](https://opensource.microsoft.com/blog/2026/04/02/introducing-the-agent-governance-toolkit-open-source-runtime-security-for-ai-agents/) provides runtime security capabilities for autonomous agents, including policy enforcement and interception points. The architecture also describes the Agent Control Specification as a mechanism for checkpoints across agent inputs, model calls, tool execution, and outputs, with higher-impact actions able to require human approval", "url": "https://wpnews.pro/news/microsoft-moves-ai-governance-from-policy-to-runtime-enforcement", "canonical_source": "https://www.infoq.com/news/2026/08/microsoft-ai-governance/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global", "published_at": "2026-08-24 13:49:00+00:00", "updated_at": "2026-08-24 14:12:56.014687+00:00", "lang": "en", "topics": ["ai-policy", "ai-infrastructure"], "entities": ["Microsoft", "Microsoft Foundry", "Microsoft Purview", "Microsoft Entra ID", "Defender", "Azure API Management", "Manasa T. Ramalinga", "Anthony Bartolo"], "alternates": {"html": "https://wpnews.pro/news/microsoft-moves-ai-governance-from-policy-to-runtime-enforcement", "markdown": "https://wpnews.pro/news/microsoft-moves-ai-governance-from-policy-to-runtime-enforcement.md", "text": "https://wpnews.pro/news/microsoft-moves-ai-governance-from-policy-to-runtime-enforcement.txt", "jsonld": "https://wpnews.pro/news/microsoft-moves-ai-governance-from-policy-to-runtime-enforcement.jsonld"}}