Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | - | Nov 2025 |
Business value
Makers can now manage triggers natively in Copilot Studio and securely share autonomous agents that run with end-user credentials. This helps organizations save time, reduce complexity, and scale the adoption of secure, autonomous agents across their organization.
Feature details
You can configure custom agents to perform actions or call topics in response to something happening using event triggers. Unlike topic triggers, which require user input, event triggers let your agent act autonomously when a defined event occurs.
With this feature, you can create triggers for autonomous agents that run with end users' credentials. You can build an agent that operates entirely in the background, triggered by external events, and share it with end users so they can configure the agent to run on their behalf.
As a maker, you can:
- Create an agent and add a trigger.
- Configure the trigger to run with end-user credentials.
- Publish and share the agent with end users.
- Once configured and enabled by end users, the agent begins to operate on their behalf.
By using event triggers and end-user credentials, this feature offers a seamless way to automate tasks and improve efficiency. With this feature, agents act independently, and multiple users can easily configure and use them.
Furthermore, triggers are now a fully native capability in Copilot Studio. This means that makers can create, configure, test, update, and delete triggers directly within Copilot Studio, managing their full lifecycle end-to-end. Any existing triggers built on Power Automate will continue to function as they did previously.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.