Copilot Studio hooks add lifecycle workflow controls
Diesen Beitrag auf Deutsch lesen
Preview hooks run workflows at six agent lifecycle events, including before a tool call, but failed hooks do not stop the agent.
Posted 
News card: Copilot Studio hooks can inspect, change or deny tool calls before they run.
By Power Platform Daily
1 min read
TL;DR
Copilot Studio preview hooks for agents using the GitHub Copilot harness can run workflows at six lifecycle events. A before-tool hook can inspect or modify arguments and deny a call, while post-call hooks can alter results or log activity. Failed, timed-out or unreadable hook responses allow the agent to continue.
Original by Josh Cook, on Flow Alt Delete. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Pilot one update tool with a before-tool hook, then test both an explicit denial and a broken workflow.
- Admins/IT: Keep mandatory authorization and business-rule enforcement in the underlying service because a failed hook does not block the agent.
- BI/Data teams: For Dataverse scenarios, log update-tool activity and validate that rejected requests do not violate business rules.
This post is licensed under CC BY 4.0 by the author.