← All Trainings

Copilot Studio Training — Trainer Guide

Low Code, Big Results — Build Copilot Studio Agents in Minutes. A 60-minute, demo-heavy tour of Copilot Studio for low-code makers. Three live agent builds of increasing sophistication — declarative, topics + actions, and autonomous — each a “wow” moment, each reproducible on the attendee’s own tenant tomorrow.

⚠️ Disclaimer
All prompts, scenarios, examples, and referenced entities (Contoso, Northwind, Contoso Orbit, etc.) are fictional and provided only for training and demonstration purposes. Do not use this material for decision-making, reporting, or external distribution.
📝 Session Details
Duration: ~60 minutes
Format: Presentation · 3 live demos · Copy-paste prompt handout
Level: 200-Level — Low-Code Makers & Power Users
Audience: Low-code makers, power users, and curious IT pros who want to build Copilot Studio agents without writing code.
License key: Copilot Studio = requires Copilot Studio capacity  •  M365 Copilot Premium = required for Agent Builder segment  •  Power Automate Premium = required for Demo 2 action
Classification: Trainer Version — For Trainer Use Only, Not for Distribution to Participants
⏲
Overview

Session Timing Breakdown

Run of Show 60-Minute Plan ▼
Time Segment What success looks like
0:00 – 0:05 Welcome & the big idea Frame why agents matter NOW and why low-code changes the game.
0:05 – 0:15 Agent Builder vs. Copilot Studio Attendees can explain when to reach for each tool.
0:15 – 0:28 Demo 1 — Contoso Concierge Declarative agent built live, grounded on uploaded content.
0:28 – 0:43 Demo 2 — Contoso Service Hero Topics + actions; agent files a real ticket via Power Automate.
0:43 – 0:55 Demo 3 — Contoso Deal Desk Autonomous agent; generative orchestration posts to Teams.
0:55 – 1:00 Wrap-up, resources, call to action Attendees commit to an agent idea before leaving.
📝 Trainer Tip
The class lives or dies on pacing. If Demo 1 runs long, compress Demo 2’s build-from-scratch portion by starting from a partially-staged agent. Never sacrifice Demo 3 — the autonomous agent is the mic-drop moment attendees will remember.
✅
Day Before

Pre-Class Setup Checklist

Accounts & Access Licenses & Permissions ▼
  • A Microsoft 365 tenant with a Copilot Studio license assigned to your demo account.
  • An M365 Copilot license for the Agent Builder segment (optional — you can do the whole class inside Copilot Studio).
  • A Power Automate premium license (for the custom connector/action in Demo 2).
  • Permission to publish agents to Teams in your demo tenant.
Content to Stage Files, Sites, Mailboxes, Channels ▼
  • Contoso Employee Handbook (PDF, 10–40 pages) — fabricate or anonymize. Put on a SharePoint site called “Contoso HQ”.
  • Contoso Product FAQ (DOCX or PDF) — 2–3 pages covering the fictional “Contoso Orbit” product line.
  • A public website for use as a knowledge source (e.g., contoso.com or your tenant’s demo site).
  • A shared mailbox deals@contoso.com (or any test mailbox you control) for Demo 3’s trigger.
  • A Teams channel named “Contoso – Deal Desk” where the autonomous agent will post.
  • A Power Automate flow named “Create Contoso Ticket” with inputs: customerName, productName, severity, description. Returns a ticket number.
  • A SharePoint list called “Contoso Tickets” with columns Title, Customer, Product, Severity, Description, Status.
  • A Contoso Rate Card Excel file on SharePoint with columns Product, List Price, Floor Price.
  • A sample deal-request email drafted and ready to send from a second mailbox during Demo 3.
Browser & Screen Presentation Setup ▼
  • Sign in to copilotstudio.microsoft.com in a clean browser profile.
  • Pin these tabs, in order: Copilot Studio home → Contoso HQ SharePoint → Power Automate → Teams.
  • Zoom browser to 125%. Hide the bookmarks bar. Turn on Do Not Disturb.
  • Have the HTML demo prompts handout open in a second window for quick copy-paste.
📝 Trainer Tip — Fallbacks
Record a 90-second screen capture of each demo the night before. If the tenant hiccups, narrate over the clip and keep the energy up. Also bookmark the final published agents — if you need to abandon a live build you can still show the working result.
🚀
Section 1 · 0:00–0:05

Welcome & The Big Idea

Talk Track Opening Hook ▼
Say this
Raise your hand if in the last month you’ve said: “I wish I had a bot that could…” Now keep it up if you’ve thought: “but I’m not a developer.” Today we’re going to fix that — together, live, in this hour you’ll see three agents get built. The first one takes less than five minutes. The last one would have been a six-month project two years ago. And you’re going to leave with the exact prompts and steps to rebuild them on your own tenant.

Points to land

  • Agents are the next phase of Copilot — they don’t just answer, they act.
  • Low-code means business users build, not just IT.
  • Every demo today uses the name “Contoso” so attendees can mentally swap in their own org.
📝 Trainer Tip — Energy Cue
Start standing. Open on a question, not a slide. Don’t introduce yourself until minute 2 — the promise first, the credentials later.
⚖
Section 2 · 0:05–0:15

Agent Builder vs. Copilot Studio

Talk Track Two Entry Points ▼
Say this
Microsoft gives you two entry points. If you live inside Microsoft 365 Copilot, Agent Builder lets you spin up a declarative agent in seconds — no new app to learn. When you need to go further — custom topics, connectors, multi-channel publish, autonomous triggers — you step up to Copilot Studio. Same family, bigger canvas.
Reference Capability Comparison ▼
Capability Agent Builder (in M365 Copilot) Copilot Studio
Authoring model Natural-language, in Copilot Natural-language + pro-code canvas
Knowledge sources Files, SharePoint, web Everything above + Dataverse, enterprise connectors, custom APIs
Custom topics Limited Full topic designer with triggers, variables, conditions
Actions / tools A small, curated set 1,400+ connectors, custom connectors, Power Automate flows, MCP tools
Publish surfaces Inside M365 Copilot Teams, web, custom apps, M365 Copilot, embedded
Generative orchestration — Yes — agent reasons over tools on the fly
Autonomous triggers — Yes — email arrival, record changes, schedule
🎯 One-Line Takeaway
Agent Builder = fastest path to a grounded assistant inside Copilot.
Copilot Studio = everything Agent Builder does, plus the muscle to automate real business processes.
🌟
Section 3 · Demo 1 · 0:15–0:28

Contoso Concierge — Declarative Agent

The Story Set the Scene ▼

“Contoso just rolled out a new employee handbook, and HR is drowning in ‘where do I find the PTO policy’ emails. Let’s build them a concierge.”

What this demo shows: describe-it-to-build-it authoring, grounding on an uploaded PDF plus a SharePoint site, one-click publish to Teams.

Pre-stage: Contoso Employee Handbook PDF on desktop · Contoso HQ SharePoint URL copied.

Live Build · 8 min Step-by-Step ▼
  1. Open Copilot Studio → Create → New agent.
  2. Switch to the Describe tab (not Configure). Paste the description prompt below.
  3. Let Copilot Studio generate the name, description, and instructions. Show the class how it auto-fills.
  4. Go to Knowledge → Add knowledge → Files. Upload the Contoso Employee Handbook PDF.
  5. Add knowledge again → SharePoint → paste the Contoso HQ site URL.
  6. Go to Starter prompts and replace the defaults with the four below.
  7. Click Test in the right-hand pane. Ask the first prompt live. Point out the citation.
  8. Click Publish → Channels → Microsoft Teams. Install to Teams and open it live.
Prompt Agent Description ▼
Paste into the Describe tab
Build an internal employee assistant for Contoso called “Contoso Concierge”. Its personality is warm, concise, and never corporate. It helps Contoso employees with HR policies, benefits, time off, IT basics, and finding the right person to talk to. It always cites the policy page it’s quoting from. If it doesn’t know the answer, it offers to open a ticket with HR and never guesses.
Prompt Starter Prompts (replace defaults) ▼
Four starter prompts
How much PTO do I get as a new Contoso employee? What's Contoso's policy on remote work? Who do I contact about parental leave? Summarize the Contoso code of conduct in 5 bullets.
Prompt Live Test — Run These In Order ▼
Test sequence
How much PTO do I get as a new Contoso employee? What about after 5 years? Who do I contact about parental leave? What if I still need help?
🌟 Wow Moment — Say This When It Answers
“Notice what just happened: no training data, no prompt engineering degree, no code. I described what I wanted in plain English, dropped in a PDF, and 90 seconds later Contoso has a concierge that cites its own handbook. This is what Microsoft means by low-code AI.”
🚨 If Something Goes Sideways
  • If knowledge indexing is slow → flip to the pre-built backup agent. Don’t stall.
  • If the first answer is off → ask “Find me the exact policy number and page.” Models recover well on the second turn.
  • If Teams publish prompts for admin consent → stay in the web test pane — the demo still lands.
🔧
Section 4 · Demo 2 · 0:28–0:43

Contoso Service Hero — Topics + Action

The Story Set the Scene ▼

“Concierge is great for ‘what’s the policy’ questions, but the real business magic is when the agent does something. Contoso’s product support team gets 400 tickets a week — a huge chunk of them low-complexity. Let’s teach Contoso Service Hero to take the ticket itself.”

What’s new vs. Demo 1

  • A custom authored topic — deterministic behavior for a known process.
  • Entities and slot-filling — collecting structured info from conversation.
  • A Power Automate action that actually creates a record.
  • Publishing to multiple channels from one agent.

Pre-stage: Power Automate flow “Create Contoso Ticket” · SharePoint list “Contoso Tickets” · Contoso Orbit Product FAQ uploaded.

Live Build · 13 min Step-by-Step ▼
  1. From Copilot Studio home, create a new agent and paste the Agent description below.
  2. Add three knowledge sources: Contoso Orbit Product FAQ (file), the Contoso support website (URL), and Contoso HQ SharePoint site.
  3. Go to Topics → + Add a topic → Create from description with Copilot. Paste the Topic generation prompt below.
  4. Let Copilot Studio scaffold the topic. Walk the class through the visual canvas — point out the trigger phrases, the Question nodes, and the placeholder for the action.
  5. Click the action placeholder → Add an action → Choose an existing Power Automate flow → select “Create Contoso Ticket”. Map the topic variables to the flow inputs.
  6. Back in the Overview, update the Instructions with the text below.
  7. Open the Test pane. Run the three test prompts in order — the last one triggers the topic and files a live ticket.
  8. Open the SharePoint list in a new tab — show the live row the agent just created. This is the “no way” moment.
  9. Publish → Channels → enable Microsoft Teams and Demo website. Drop the web chat URL in the class chat.
Prompt Agent Description ▼
Paste into the Describe tab
Build me a customer support agent for Contoso called “Contoso Service Hero”. It helps customers troubleshoot the Contoso Orbit product line and, when it can’t solve the issue in chat, creates a support ticket on their behalf. It is patient, asks one question at a time, always confirms before filing anything, and always returns a ticket number the customer can reference.
Prompt Topic Generation — “File a Support Ticket” ▼
Paste into Create from description with Copilot
Create a topic called “File a Support Ticket” that triggers when a customer says they want to open a ticket, log an issue, report a problem, escalate, or talk to a human. The topic should collect the customer’s name, the product name (default to Contoso Orbit), the severity (Low, Medium, High, Critical), and a description of the issue. Confirm the details back to the customer, then call the action “Create Contoso Ticket” to file it. Return the ticket number in the confirmation message and offer to email the customer a copy.
Prompt Agent Instructions ▼
Paste into Instructions
You are Contoso Service Hero, a friendly product support specialist. Always try to solve the issue in chat first using your knowledge sources. If the customer explicitly asks to open a ticket, or you’ve tried two approaches and haven’t resolved it, use the File a Support Ticket topic. Never make up a ticket number — always use the one returned by the action. When you file a ticket, restate the ticket number clearly and give the customer a realistic expectation of response time based on severity (Critical: 1 hour, High: 4 hours, Medium: next business day, Low: 3 business days).
Prompt Live Test — Run These In Order ▼
Test sequence (three turns)
My Contoso Orbit won't connect to Wi-Fi after the latest firmware update. I tried that. It still won't connect. I need someone to help me. Yes, please open a ticket. My name is Priya Desai, the severity is High, and the issue is: Orbit unit #A47 will not associate with the corporate SSID after firmware 4.2.
🌟 Wow Moment — Say This After the Ticket Appears
“Pause on this for a second. A business user just built, in twelve minutes, an agent that understands a product catalog, troubleshoots in natural language, collects structured data, calls a business system, and returns a real ticket number. No C# developer was harmed in the making of this demo. THIS is what Copilot Studio unlocks that Agent Builder can’t.”
🚨 If Something Goes Sideways
  • If the Power Automate action errors → switch to a mocked action that returns a hard-coded ticket number. The narrative still lands.
  • If slot-filling trips → finish the slots manually in the test pane; the class learns more from you narrating the debug.
  • Keep a screenshot of a successful SharePoint list row on your desktop — ultimate fallback.
🤖
Section 5 · Demo 3 · 0:43–0:55

Contoso Deal Desk — The Autonomous Agent

The Story Why This Is the Mic Drop ▼

Demos 1 and 2 respond to a human in a chat window. This one doesn’t need a human at all. It wakes up when an event happens, reasons over a set of tools, and completes a business outcome on its own. This is agent-as-employee, not chatbot.

“Contoso sales reps get deal requests emailed to deals@contoso.com. Every request needs to be summarized, priced against the rate card, posted to the deal-desk Teams channel, and flagged for approval if over $50k. Today, a human spends 15 minutes on each one. Watch what happens when we hand that off.”

Pre-stage: deals@contoso.com mailbox · Contoso Rate Card Excel on SharePoint · “Contoso – Deal Desk” Teams channel · sample deal email ready to send from a second mailbox.

Live Build · 10 min (mostly show) Step-by-Step ▼
📝 Trainer Tip
Pre-build the agent’s skeleton so you only need to finish the last 2–3 steps live. This is a showcase demo, not a from-scratch build.
  1. In Copilot Studio, create a new agent. Switch the orchestration setting to Generative (use generative AI to orchestrate).
  2. Paste the Agent description below.
  3. Add tools (not topics — tools). Show the class that generative orchestration lets the agent pick which tool to use.
  4. Set the trigger: when a new email arrives in deals@contoso.com.
  5. Paste the Agent instructions into the agent.
  6. From a second mailbox, send the test email below to deals@contoso.com. Then switch to Teams and wait for the Adaptive Card to appear.
Prompt Agent Description ▼
Paste into the Describe tab
Build an autonomous agent for Contoso called “Contoso Deal Desk”. Its job is to process incoming sales deal requests end-to-end without a human in the loop, until approval is required. When a new deal-request email arrives at deals@contoso.com, it reads the email, extracts the customer name, the requested products, quantities, and any discount asks. It looks up list and floor pricing from the Contoso Rate Card. It drafts a deal summary. It posts an Adaptive Card to the “Contoso – Deal Desk” Teams channel with the summary and an Approve/Reject button. If the deal value is over $50,000 or the discount is deeper than the floor, it flags the card as Requires Approval. It never quotes below floor. It is precise, neutral, and short — sales leaders don’t want fluff.
Reference Tools to Add ▼
Add these tools to the agent
- Get a new email from the deals@contoso.com mailbox (Outlook connector) - Read an Excel file on SharePoint — Contoso Rate Card (Excel connector) - Post an Adaptive Card to a Teams channel (Teams connector) - Create an approval (Approvals connector, optional)
Prompt Agent Instructions ▼
Paste into Instructions
When a new email arrives at deals@contoso.com: 1. Read the email body and extract: customer name, requested products (as a list), quantities, and any discount asks. 2. For each requested product, look up List Price and Floor Price from the Contoso Rate Card. 3. Compute: subtotal at list, subtotal at requested price, and total discount %. 4. Draft a 4-line deal summary: customer, products, total value, discount %. 5. Post an Adaptive Card to the "Contoso – Deal Desk" Teams channel with the summary, a Details expander containing the line items, and an Approve/Reject action. 6. If total value > $50,000 OR any line is below Floor Price, tag the card "Requires Approval" and @mention the Deal Desk Lead. 7. Never quote below Floor Price. If asked to, post the card with "Blocked — below floor" and stop. 8. Reply to the original email with "Your request is with our deal desk, reference: <Teams post link>".
Trigger Email Live Demo Email — Send from a Second Mailbox ▼
Send to deals@contoso.com
To: deals@contoso.com Subject: Deal request — Northwind Traders Hi Contoso team, Northwind Traders would like to purchase the following: - 250 × Contoso Orbit Pro units - 250 × Contoso Orbit Care — 3-year support They're asking for a 22% discount off list across the bundle. Need to close by end of quarter. Thanks, Alex
🌟 Wow Moment — Say This While Teams Is Loading
“I never told it to read an email first, then look up the rate card, then post to Teams. I gave it a goal and a toolbox. The agent decided the sequence. That is generative orchestration — and that is something you cannot do in Agent Builder.”
🚨 If Something Goes Sideways
  • Autonomous triggers can take 30–90 seconds. Use the wait as narration time — walk the class through what the agent is doing right now.
  • If the trigger hasn’t fired in 2 minutes → switch to the pre-recorded screen capture and narrate.
  • If the Adaptive Card is plain → show the Power Automate run history. Point to each tool invocation and say “the agent chose to do this.”
🎯
Section 6 · 0:55–1:00

Wrap-Up & Call to Action

Recap Three Demos, Three Sentences ▼
  • Contoso Concierge — describe it, ground it, publish it. Five minutes to a real assistant.
  • Contoso Service Hero — topics + actions let your agent do the work, not just answer.
  • Contoso Deal Desk — give the agent a goal and a toolbox, and it runs the process itself.
The Ask Closing Line ▼
Say this
Before you leave this session, write down the name of ONE workflow at your company where people spend 15 minutes on something that should take 15 seconds. That’s your first agent. Ping me on Teams this week and I’ll help you scope it.
🎯 Final Thought for the Close
“The question isn’t whether your team will build agents. It’s whether they’ll build them now or after a competitor does. See you on Teams.”
💬
Reference

Anticipated Q&A

Prep Common Questions & Short Answers ▼
Question Short Answer
Do I need a Copilot license for every user of my agent? Depends on the publish surface. Agents published inside M365 Copilot require the M365 Copilot license. Agents published to Teams or web typically meter usage against the maker’s Copilot Studio capacity.
Is the data from my agent used to train public models? No. Tenant data stays in your tenant. Copilot Studio honors your existing M365 data boundaries.
What’s the difference between a topic and a tool? A topic is a deterministic conversation flow you author. A tool is a capability (connector, flow, API) the agent can choose to call. Generative orchestration means the agent reasons over tools on the fly.
Can autonomous agents run without anyone logged in? Yes. They run under a maker-configured service identity on their configured trigger (email arrival, schedule, record change, etc.).
How do I govern who can build agents? Through Power Platform admin center — environments, DLP policies, and managed environments. Your IT admin can share guardrails before you scale.
Can I move an Agent Builder agent into Copilot Studio? Yes — agents you start in Agent Builder can be opened and extended in Copilot Studio when you outgrow the Agent Builder surface.
📎
Resources

Resources to Share in the Class Chat