CISO
CIO
Enterprise Architect
Compliance Officer
Industry relevance
Financial Services
Healthcare
Government
APRIL 30, 2026
No published standard defines what an authorization record for a multi-agent chain must contain or whose name is accountable when the chain acts outside any individual agent's approved scope.

CISA, the NSA, and allied agencies from Australia, the UK, Canada, and New Zealand published Careful Adoption of Agentic AI Services on April 30, 2026. The guidance recommended integrating agentic AI into existing zero trust and identity management frameworks. It explicitly acknowledged that existing security frameworks have not fully caught up with agentic AI and that some risks unique to these systems are not yet covered. One of those uncovered risks: how authorization and accountability should flow across multi-agent orchestration chains, including which agent's scope covers the outcome and whose name is accountable when the chain acts outside any individual agent's approved scope.
GOVERNANCE IMPLICATION
When Agent A instructs Agent B which instructs Agent C, no published standard specifies what an authorization record for that chain must contain, which agent's scope covers the aggregate outcome, or whose name is accountable when the chain acts outside any individual agent's approved scope. That gap now has a working name: Chain Authorization Gap. It is distinct from prompt injection, agent sprawl, and the Intent Gap. The Chain Authorization Gap is the absence of any authorization record for the outcome of a multi-agent chain, where no single agent held individual authorization for what the chain collectively did. Entra Agent ID provides identity and parent-child relationships for orchestrations. It does not prescribe who approves the chain or who is accountable when the chain causes harm.
SCENARIO
A regulated financial institution deploys a three-agent Copilot Studio orchestration: an orchestrator that receives customer requests, a retrieval agent that queries SharePoint for policy documents, and a drafting agent that produces loan modification recommendations. Each agent has an Entra Agent ID and a parent-child relationship documented in the platform. An OCC examination asks for the authorization record for the orchestration chain, specifically who approved the combined scope of all three agents acting together, what that combined scope permits, and who is the named accountable owner for the chain's output. The Entra Agent ID records exist. The chain authorization record does not.
THE GOVERNANCE QUESTION
For each multi-agent orchestration currently running in your environment, can you produce a single authorization record that names who approved the chain, defines the aggregate scope of permitted actions across all agents, and identifies the human accountable if the chain produces an outcome outside that scope? If not, the Chain Authorization Gap exists in your environment.
CONTROL GAP
No regulatory body, vendor platform, or published framework specifies what an authorization record for a multi-agent orchestration chain must contain. Enterprises deploying multi-agent systems on Copilot Studio and Entra Agent ID are defining their own accountability structures with no external standard to validate against.
REGULATORY RELEVANCE
NIST Ai RMF
OCC
FINRA
FFIEC
PRIMARY SOURCE
Careful Adoption of Agentic AI Services
CISA, NSA, ASD's ACSC, and international partners
April 30, 2026
Read the primary source ->(opens in new tab)CONTINUE READING

OCTOBER 19, 2026
Agent SecurityOn October 19, 2026, Microsoft published a post by Nadim Abdo, Corporate Vice President, Identity and Network Access, that treats AI agents already inside the enterprise as insiders. Microsoft says it is expanding discovery to 35 additional types of local agents, for a total of 60 supported local agents, including Claude Code, OpenAI Codex, and GitHub Copilot. Microsoft says agents should begin with no authority and describes Dynamic Permissions scoped to the task and time-bound, with organization-wide policy setting the outer boundary. It also describes Dynamic Agent Risk, Dynamic Conditional Access, and Guardian Agents in Project Perception. The post says people define policy, approval boundaries, and delegation rules. It gives no availability dates for any capability.

OCTOBER 16, 2026
ComplianceOn October 16, 2026, Microsoft and NVIDIA published Risk Management for Open-Weight Models in Enterprise, the first in a planned series of joint resources. The paper introduces a shared taxonomy of five risk categories: Cybersecurity, Data Protection, Content, Human-AI Interaction, and Bias. Microsoft says enterprises should connect relevant risks to evaluations, mitigations, and accountable owners, and the paper draws on ISO standards and the NIST AI Risk Management Framework. Microsoft states that weight openness alone does not determine risk, that responsibility for safeguards depends on the service and deployment configuration, and that evaluating a model alone does not establish the safety of an agent or application. The first paper focuses on the model layer.

OCTOBER 13, 2026
Identity DataThree Microsoft Learn pages describe Copilot Studio agents built before Microsoft Entra Agent ID in different ways. The Copilot Studio page last updated September 15, 2026 says agents created before the May 2026 rollout continue to use app registrations and can be migrated manually in the Power Platform admin center, with PowerShell scripts, or with Power Platform APIs. A second Copilot Studio page last updated October 13, 2026 says they will migrate automatically with no manual action, and gives no timeline. A Microsoft Entra page last updated June 15, 2026 says no automated or in-place migration path exists, that Microsoft Entra treats these service principals as standard applications and not as AI agents, and that automatic agent identity creation began March 18, 2026.