Create and configure custom agents in Microsoft Copilot Studio via a guided web app process, including triggers, knowledge, tools, topics, and publishing.
Create agents in Microsoft Copilot Studio using the web app. This skill guides you through the complete agent creation process based on Microsoft Learn documentation.
Documentation: https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-first-bot
Key Limits:
< >)Option A - Natural Language:
Option B - Create from Scratch:
Option C - Advanced Create:
After provisioning, configure:
| Feature | Description |
|---|---|
| Primary AI Model | Change agent model |
| Triggers | Define what activates the agent (About triggers) |
| Knowledge Sources | Add enterprise data, websites, SharePoint, Dataverse (Knowledge) |
| Tools | Add Power Automate flows, connectors (Add tools) |
| Other Agents | Add sub-agents (Add agents) |
| Topics | Define conversation flows (Create topics) |
| Starter Prompts | Add suggested prompts for users |
Rename & Edit Description:
Edit Instructions:
Change Icon:
Change Language/Solution:
⚠️ Note: Cannot change primary language after creation. Can change region or add secondary languages.
| Node Type | Purpose |
|---|---|
| Message | Send a message to user |
| Question | Ask user for input |
| Adaptive Card | Interactive cards with buttons/inputs |
| Condition | Branch conversation based on logic |
| Variable | Set, parse, or clear variables |
| Topic Management | Redirect, transfer, or end conversation |
| Tool | Call Power Automate flows, connectors |
| Advanced | Generative answers, HTTP requests, events |
| Source | Description |
|---|---|
| Public Website | Bing search on provided URLs (max 25 in generative mode) |
| Documents | Uploaded to Dataverse |
| SharePoint | Connect via URL |
| Dataverse | Query tables in environment |
| Enterprise Data | Microsoft Search via connectors |
Web App:
Event triggers allow agents to act autonomously in response to external events—without user input.
| Trigger | Source | Example |
|---|---|---|
| When a row is added/modified/deleted | Dataverse | New record in table |
| When a file is created | OneDrive | New file uploaded |
| When an item is created | SharePoint | New list item |
| When a task is completed | Microsoft Planner | Task marked complete |
| Recurrence | Scheduled | Time-based trigger (every X minutes) |
The payload is a JSON/plain text message sent to the agent containing:
Default payload example: "Use content from Body"
Custom payload example: "Summarize the changes and send to the user"
| Approach | Use Case |
|---|---|
| Agent Instructions | General behavior, simple agents with few triggers |
| Payload Instructions | Complex agents with multiple triggers/goals |
⚠️ Before publishing: Agent won't react automatically until published.
Each trigger activation counts as a message toward Copilot Credits. A recurrence trigger running every 10 minutes = ~4,320 messages/month.
Agents can call Power Automate cloud flows as tools to perform actions and get data.
| Requirement | Details |
|---|---|
| Trigger | Must use When an agent calls the flow |
| Response | Must include Respond to the agent action |
| Mode | Real-time (Async toggle = Off) |
| Timeout | Must respond within 100 seconds |
| Flow Run Limit | Up to 30 days (after response) |
Option 1: From Topic
Option 2: From Overview
In the When an agent calls the flow trigger, add input parameters:
| Parameter | Type | Example |
|---|---|---|
| City | Text | "Seattle" |
| ZIP code | Number | 98101 |
| Date | DateTime | "2024-01-15" |
In Respond to the agent action, define output parameters:
| Output Parameter | Type | Variable Name |
|---|---|---|
| day_summary | Text | Day Summary |
| location | Text | Location |
| chance_of_rain | Number | Day Rain Chance |
When an agent calls the flowRespond to the agent actionRespond to Copilot action| Auth Type | Description |
|---|---|
| Maker credentials | Default - uses author's account |
| User credentials | Users run with their own permissions (generative orchestration) |
For user credentials: Configure flow's "Run-only permissions" to Provided by run-only user.
⚠️ CMK Environments: Cloud flows can't run with customer credentials. Use specific connections instead.
When publishing an agent with event triggers, you'll see a warning about author credentials. Users may access data using the agent maker's authorization.
| Mode | Trigger Behavior |
|---|---|
| Test | Manual activation required |
| Published | Automatic activation on events |
ZIP package — ready to use