How to Set Up Agent Triggers in Microsoft Copilot Studio
Diesen Beitrag auf Deutsch lesen
Configure Copilot Studio agent triggers for Dataverse events, permissions, scope, filters, run-as options and testing.
TL;DR
Microsoft Copilot Studio agent triggers start agent activity when configured events occur, such as adding an Account record in Dataverse. The setup covers trigger selection, connections, permissions, scope, filters, run-as properties and additional instructions. Makers can test the result by creating a record and checking the Test Pane.
Original by Griffin Lickfeldt, on Citizen Developer. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Select a suitable Dataverse trigger, define its event properties, filters and instructions, then test it with a new record to confirm the agent receives the intended message.
- Admins/IT: Review the trigger connections, user privileges, scope and run-as choice because these settings determine which data context executes the trigger.
- BI/Data teams: Check the selected Dataverse table and change type, especially when filtering events such as active Accounts, so automation responds to the intended records.
Frequently asked questions
How do I create a Dataverse Add a record trigger in Copilot Studio?
Open the agent Overview tab, choose Add Trigger, select Dataverse | Add a record, then configure its name, connection, table and properties.
What run-as options are available for Copilot Studio agent triggers?
A trigger can run as the flow owner, modifying user or row owner. Each option determines whose context executes the agent or flow.
How can I test an agent trigger after configuring it in Copilot Studio?
Create the configured Dataverse record, use the test feature and inspect the Test Pane to verify the message sent and resulting functionality.