Make agent actions safe under retries, races, and partial failure
Bind approval to a concrete action, enforce authorization at execution, make retries idempotent, and recover multi-step workflows without inventing an exactly-once guarantee.
Explore the topic
Constrain connectors, tool authority and the consequential actions an agent can take.
Questions this collection helps you answer
Build your understanding
Bind approval to a concrete action, enforce authorization at execution, make retries idempotent, and recover multi-step workflows without inventing an exactly-once guarantee.
Turn a Copilot Studio connector inventory into scoped data policies, verified endpoint controls, and accountable changes across environments.
Design per-request authorization, tool admission, downstream identity and consequential-action approval for remote MCP integrations with Microsoft Foundry.
Separate agent sign-in from tool authority, constrain shared connections, and verify approval and denial paths.
Move from control to evidence
Use these as investigation leads. Table coverage and context determine what the results can establish.
Compare successful workload resource identifiers against a prior baseline without treating token issuance as proof of new permissions or data access.
Preserve initiator identity and every target's permission-change evidence for successful app-role, delegated-permission and consent events.
Follow the connections