Copilot Studio hooks cannot be your only control
Diesen Beitrag auf Deutsch lesen
Hooks can deny or modify tool calls, but failed, timed-out or unreadable hook workflows let the agent continue.
Posted 
Governance card: A failed hook does not stop the tool call. Keep critical controls in the service.
By Power Platform Governance
1 min read
TL;DR
Copilot Studio preview hooks can run at six lifecycle events, including before a tool call, where they can inspect or change arguments and deny the call. However, if the hook workflow fails, times out or returns an unreadable response, the agent continues. Enforce mandatory authorization in the underlying service and test broken-hook behavior.
Original by Josh Cook, on Flow Alt Delete. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Test a denied Dataverse update and then deliberately break the hook workflow to verify the service still protects the record.
- Admins/CoE: Treat Copilot Studio hooks as preview controls and document their failure-open behavior before approving production use.
- Security/Compliance: Keep authorization rules for sensitive updates in the underlying service, because a failed hook does not block the agent action.
This post is licensed under CC BY 4.0 by the author.