SoftTech AI Registry
Microsoft · Microsoft Copilot Studio

Event Triggers

Event and schedule based initiation for Copilot Studio agents. A defined event in a connected system, or a recurrence schedule, sends a payload to an agent with generative orchestration turned on; maker-authored instructions and the payload determine which of the agent's existing topics, actions or tools are invoked. No originating user message is required. Trigger connections are authenticated with the agent maker's account.

Recorded characteristics

Function
A maker adds an event trigger to a Copilot Studio agent. Microsoft states that "unlike topic triggers, which require input from a user, event triggers allow your agent to act autonomously in response to the defined event occurring", and that the feature "is only available for agents with generative orchestration turned on". Documented trigger examples include an item created in SharePoint, a file created in OneDrive, a task completed in Planner, and a Recurrence trigger that fires after a set amount of time. Microsoft describes the workflow as: the trigger registers that a specific event occurred; it sends a payload containing information about the event and instructions; and the agent has instructions to choose one or more actions or topics based on the payload. The agent selects only from what the maker has already built - Microsoft states "your agent doesn't create a new action or topic on the spot". Documented responses include invoking actions that reach connected systems, for example sending a new team member a welcome message with onboarding resources. This record covers initiation, payload handling, payload and instruction driven selection, and the authentication behaviour of triggered execution; the mechanics of individual connector tools are recorded separately under Connector Tools.
Data access
Recorded conservatively. What a triggered agent can read or act on is governed by the permissions available through the configured authenticated connection - where maker authentication is used, the maker's own permissions, since Microsoft states "the agent maker can only set a trigger for your agent based on events in systems you have permission to access as agent author" - together with the connectors and tools the maker has added, the knowledge or data sources attached to the agent, and the organisation's data policies. Microsoft states that "what triggers are available depends on your organization's data policies, configured in Power Automate by an administrator". No unrestricted access to Microsoft 365 or to external systems is documented or implied.
Actions
Can take actions
External actions
Yes
Human confirmation
Conditional
Permission basis
Mixed
Administrative control
Administrators control event-triggered behaviour at the environment and environment-group level. Power Platform data policies configured in Power Automate determine which connectors are available as triggers. The "Control maker credential options" setting in the Power Platform admin center (Environments > Settings > Product > Features > Copilot Studio agents) governs whether maker-provided credentials may be used; Microsoft states that by default both end-user and maker-provided credentials are enabled. Generative orchestration must be turned on for the agent before event triggers can be used. Agent identity is governed through Microsoft Entra Agent IDs.
Default state
Disabled
Availability
Event triggers are documented as a Copilot Studio authoring feature for agents with generative orchestration enabled, added per agent by a maker. No Event Trigger-specific geographic or regional limitation is publicly established in the documentation reviewed.
Licensing
Copilot Studio licensing applies. Microsoft states that "starting on September 1, 2025, the common currency for agents changed from messages to Copilot Credits", and that event trigger activity counts towards consumption: payloads sent to agents from event triggers are billed as messages, with the documented example of a recurrence trigger set to activate every 10 minutes sending a trigger payload every 10 minutes. A Copilot Studio user and tenant licence, a Microsoft 365 Copilot licence, or a trial licence is documented as a prerequisite.
External model or provider
Not established. Microsoft does not name a model or model provider for event-triggered generative orchestration in the documentation reviewed.
Limitations and uncertainty
Human confirmation is recorded as conditional, not required. Microsoft documents no platform-level contemporaneous confirmation requirement for event-triggered execution; oversight is presented as maker-configurable guidance - "for high-stakes tasks, keep a human in the loop. Configure the agent to request approval or confirmation from a person before executing actions that could be sensitive" - alongside "scoped permissions, explicit decision boundaries, and auditable processes". No action-level approval control is claimed here, and community material was not relied upon. Permission basis is recorded as mixed because two distinct layers are documented and neither replaces the other: (1) trigger and tool authentication, where Microsoft states "you can only authenticate trigger connectors using the agent maker's account (agent author authentication)" and that with maker-provided credentials "the agent uses the maker's credentials, not the end user's credentials, to authenticate with connected services", with the documented security implication that this can expose data or capabilities available to the maker that an interacting end user might not independently possess; and (2) agent identity, where Microsoft states that all new agents automatically receive Microsoft Entra Agent IDs - Entra service principals with an "Agent" subtype - while older agents can retain legacy app registrations pending migration. The Entra Agent ID does not replace the maker credentials used by event-trigger connectors and tools. Two different defaults must not be conflated: event triggers are opt-in per agent and must be added explicitly by a maker, whereas maker-provided credentials are permitted by default at the environment-policy level. Microsoft documents a consequential governance interaction: when maker-provided credentials are prevented from being used, "agents triggered by scheduled or autonomous events, or that attempt to run in the background, fail due to missing credentials. All agent triggers must involve an active user." Region, model and provider are not established.

Evidence