Empower Your Automation: Configure Event Triggers with End-User Credentials in Microsoft Copilot Studio

January 8, 2026 | Copilot and AI | 5 min read

Empower Your Automation: Configure Event Triggers with End-User Credentials in Microsoft Copilot Studio


The Power Platform continues to evolve rapidly and the 2025 release wave 2 brings a powerful new capability to Microsoft Copilot Studio, the ability to configure triggers that run with individual end-user credentials. This feature unlocks secure, autonomous, event-driven automation that can be shared across your organization, without sacrificing data security or user autonomy.

What’s This Feature All About?

Previously, Copilot Studio agents could react to events or user input only through mechanisms like topic triggers or Power Automate workflows. With this update, makers can define event triggers that execute on behalf of the signed-in user, driven by external events and running entirely in the background.

These autonomous agents aren’t just intelligent, they’re secure, context-aware and user-specific.


Why It Matters

👉 Enterprise-Grade Security

By executing actions using each end user’s credentials rather than shared or maker credentials, your automation respects user permissions and least-privilege access, reducing oversharing and minimizing risk.

👉 Scalable, Shareable Automation

Instead of building separate automations for each user or team, you can create one agent with an event trigger, publish it and let individual users configure it themselves to act on their behalf. This greatly simplifies deployment and scaling across your organization.

👉 Native Trigger Management

Triggers are now a fully native capability in Copilot Studio, meaning makers can create, configure, test, update and delete triggers right inside the Studio environment without switching tools.


How It Works

Building and using an agent with end-user credential triggers revolves around four core steps:

  1. Create the Agent

    2. Start by building your custom agent in Copilot Studio, include all actions or topics it needs to execute.

  2. Add and Configure the Trigger

    3. Add an event trigger to your agent and configure it to run using the end user’s credentials. This tells the system to authenticate using each user’s identity whenever the trigger fires.

  3. Publish and Share

    4. Publish the agent and share it with your intended users. They’ll receive the agent and can enable it for their account.

  4. Run Autonomously

    5. Once enabled, the trigger runs autonomously, responding to events and acting on behalf of the user, executing actions or calling topics as defined.


Conclusion

This update represents a significant milestone in Microsoft’s vision for Copilot Studio: putting secure, autonomous automation directly in the hands of users while maintaining organizational governance and data integrity.

This feature is especially useful in scenarios like automated approvals, where agents detect system changes and start approval workflows using the identity of the requesting user. In addition, it enables event-driven alerts by sending personalized notifications or updates whenever specific conditions are met. All these actions happen securely and transparently, using the right user context.

By using event triggers, user credentials and built-in trigger management, Copilot Studio now supports secure and enterprise-ready automation.


  • Enabled for : Admins, makers, marketers, or analysts, automatically
  • Public Preview : -
  • General Availability: Nov 2025