Copilot Studio Workshop

A two-day, hands-on workshop for building, extending, and governing AI agents with Microsoft Copilot Studio.

Workshop Overview

	Day 1 — Recruit Track	Day 2 — Operative Track
Theme	Foundation-building	Governed enterprise extension
Scenario	Contoso IT Helpdesk Agent	Hiring Agent & Operative solution
Labs	00–12	13–25
Audience	Makers, IT Pros, Developers	Same — building on Day 1 skills

Quick Start

1. Prerequisites — A work or school Microsoft 365 account, Copilot Studio access, and a Power Platform environment. See Lab 00 for full setup.
2. Participant guide — Start with Welcome and Overview.
3. Facilitator guide — See Facilitator Guide for delivery flow, environment readiness, and automation.

Workshop Materials

Presentation Slides

The workshop includes 13 committed PowerPoint presentation decks covering the full two-day curriculum.

• Location: workshop\Copilot-Studio-Workshop-Slides\
• Format: Delivery-ready PPTX files for instructor-led presentation and screen sharing
• Size: 98 slides total across 13 module decks

Module	File	Focus area
00	Module-00-Workshop-Framing.pptx	Workshop introduction and objectives
01	Module-01-Agents-Today.pptx	Current state of AI agents
02	Module-02-Studio-Foundations.pptx	Copilot Studio basics
03	Module-03-Reuse-Patterns.pptx	Template and pattern reuse
04	Module-04-Custom-Agent-Design.pptx	Custom agent architecture
05	Module-05-Topic-Design.pptx	Conversational topic patterns
06	Module-06-Actions-and-Events.pptx	Actions and event-driven design
07	Module-07-Hiring-Architecture.pptx	Enterprise hiring scenario
08	Module-08-Automation-and-Models.pptx	Automation and model strategy
09	Module-09-Multimodal-and-Data.pptx	Multimodal capabilities and data grounding
10	Module-10-MCP-and-Extensibility.pptx	MCP and extensibility patterns
11	Module-11-Channels-and-Feedback.pptx	Channel rollout and feedback loops
12	Module-12-Evaluation-and-ROI.pptx	Evaluation and ROI measurement

Companion Materials

• Markdown outline: workshop\assets\slide-deck-outline.md — 95 numbered entries with speaker notes, narrative structure, and teaching intent
• Delivery notes: workshop\assets\slide-deck-delivery-notes.md — speaker support, transition planning, and facilitation cues
• Visual plan: workshop\assets\slide-deck-visual-plan.md — visual planning companion for slide layout and design review
• Lab timing guide: workshop\assets\lab-timing-guide.md — detailed pacing and delivery guidance for labs
• Session splitting guide: workshop\assets\session-splitting-guide.md — alternative multi-session delivery formats
• Facilitator guide: workshop\facilitator-guide\facilitator-guide.md — complete delivery flow, readiness guidance, and recovery notes

The repository maintains slides in two parallel formats:

• PPTX decks are the authoritative delivery artifacts with visual design and live presentation flow.
• The markdown outline is the narrative companion used for speaker notes, teaching intent, and text-first review.

When slide structure, sequencing, or teaching intent changes, keep both assets aligned.

For Facilitators

Before live delivery, review these materials together:

1. The PPTX decks in workshop\Copilot-Studio-Workshop-Slides\
2. The markdown outline in workshop\assets\slide-deck-outline.md
3. The facilitator guide in workshop\facilitator-guide\facilitator-guide.md
4. The lab timing guide in workshop\assets\lab-timing-guide.md
5. The session splitting guide in workshop\assets\session-splitting-guide.md

Use the PPTX decks for presentation and screen sharing, then use the markdown outline when you need detailed speaker notes or a text-first review of the teaching flow.

Sample Data and PII Hygiene

• Keep all sample identities fictitious.
• Use example.com for sample email addresses unless a file explicitly needs a placeholder token such as <replace-with-org>.
• Do not commit customer-specific names, mailboxes, tenant URLs, Teams routing IDs, or other environment-bound values in exported assets or starter solutions.
• Preserve the canonical workshop fiction: Contoso, Contoso IT, Contoso Helpdesk Agent, Hiring Agent, Hiring Hub, Operative, and AgentCreators.

Lab Index

Day 1 — Recruit Track

Lab	Title	Time
00	Environment Setup	45 min
01	Intro to Agents	20 min
02	Copilot Studio Fundamentals	30 min
03	Declarative Agents	60 min
04	Solutions	45 min
05	Prebuilt Agents	30 min
06	Custom Agent	75 min
07	Topics & Triggers	60 min
08	Adaptive Cards	45 min
09	Agent Flows	45 min
10	Event Triggers	25 min
11	Publish Agent	30 min
12	Licensing	20 min

Day 2 — Operative Track

Lab	Title	Time
13	Hiring Agent Setup	45 min
14	Agent Instructions	25 min
15	Multi-Agent Hiring Team	40 min
16	Trigger Automation	40 min
17	Model Selection	30 min
18	Content Moderation	40 min
19	Multimodal Prompts	35 min
20	Dataverse Grounding	40 min
21	Document Generation	45 min
22	MCP Integration	45 min
23	User Feedback	30 min
24	Agent Evaluation	45 min
25	VS Code Extension (Optional)	30 min

Facilitator Automation

On a fresh Windows 11 machine, open PowerShell and run:

mkdir C:\workshop; cd C:\workshop
irm https://raw.githubusercontent.com/judeper/copilot-studio-workshop/master/workshop/automation/Invoke-WorkshopBootstrap.ps1 -OutFile .\Bootstrap.ps1
.\Bootstrap.ps1

This downloads and runs the interactive bootstrap wizard, which:

• Installs PowerShell 7 (if running PS 5.1), then re-launches itself
• Installs git, Power Platform CLI, and Node.js (via winget) if missing
• Clones this repository if not already on disk
• Installs required PowerShell modules (PnP.PowerShell, Microsoft.Graph, PowerApps Admin)
• Auto-creates an Entra app registration with required API permissions
• Walks through config setup interactively (tenant name → auto-derives all URLs)
• Sets up pac CLI authentication
• Downloads all workshop assets
• Runs the scripted prerequisite checks and shows a readiness dashboard for shared facilitator setup signals

If you already have the repo cloned, run the wizard directly:

pwsh -File .\workshop\automation\Invoke-WorkshopBootstrap.ps1

After the wizard completes:

# 1. Pre-stage shared Day 1 prerequisites (Contoso IT site, lists, schema, and sample data)
powershell -File .\workshop\automation\Invoke-WorkshopLabSetup.ps1 -Mode StudentReady

# 2. Optional: create or reserve a separate facilitator demo environment
# Use -UpdateConfig to write the discovered or created URL back to workshop-config.json
powershell -File .\workshop\automation\Initialize-WorkshopPowerPlatformEnvironment.ps1 -CreateEnvironment -UpdateConfig

# 3. Optional: pre-import the Day 2 base state in the facilitator demo environment only
# Import target comes from -EnvironmentUrl or config.EnvironmentUrl; pac auth only supplies tenant/account context
powershell -File .\workshop\automation\Import-WorkshopOperativeAssets.ps1 -ImportSolution -EnvironmentUrl https://<facilitator-demo>.crm.dynamics.com
# -ImportBaseData also requires a Dataverse-capable client secret plus one-time Power Platform app registration
powershell -File .\workshop\automation\Import-WorkshopOperativeAssets.ps1 -ImportBaseData -EnvironmentUrl https://<facilitator-demo>.crm.dynamics.com

# 4. Optional advanced path: qualify a completed facilitator gold source, then rebuild the fallback environment
powershell -File .\workshop\automation\Set-WorkshopFacilitatorFallbackSource.ps1 -ListCandidates
powershell -File .\workshop\automation\Set-WorkshopFacilitatorFallbackSource.ps1 -SourceEnvironmentUrl https://<completed-source>.crm.dynamics.com -UpdateConfig
powershell -File .\workshop\automation\Invoke-WorkshopFacilitatorFallbackBuild.ps1

# 5. Optional: validate one student first, then batch-provision per-student environments for hands-on
powershell -File .\workshop\automation\Invoke-StudentEnvironmentProvisioning.ps1

# 6. Reset the shared environment for re-testing (deletes ContosoIT site + purges recycle bin)
pwsh -File .\workshop\automation\Reset-WorkshopEnvironment.ps1 -HardDelete

# 7. Post-workshop: tear down all student environments
powershell -File .\workshop\automation\Remove-StudentEnvironments.ps1 -HardDelete

# 8. Optional: tear down a disposable facilitator demo or fallback target
powershell -File .\workshop\automation\Remove-WorkshopFacilitatorEnvironment.ps1 -EnvironmentUrl https://<demo-or-fallback>.crm.dynamics.com

After any new Power Platform environment is created for the workshop, open Power Platform admin center and configure Copilot usage billing before agent testing. Use either Billing > Link Azure subscription for pay-as-you-go or allocate Copilot Studio capacity/credits to the environment. Treat this as a manual facilitator step: the repo can attempt preview student credit allocation, but that path is not reliable enough to replace PPAC billing setup and can still return 403 in some tenants. When that happens, Invoke-StudentEnvironmentProvisioning.ps1 records FollowUpRequired so the remaining billing step is explicit.

Treat setup as three separate readiness tracks:

• Shared prerequisites — bootstrap, the shared Day 1 SharePoint site, and Day 2 assets.
• Facilitator demo base — a separate demo environment used only for facilitator fallback demos and optional Day 2 solution/base-data imports.
• Student hands-on environments — either the shared StudentReady path or the optional per-student provisioning path.

Bootstrap and prerequisite checks help confirm shared facilitator setup signals. They do not prove the facilitator demo import path, fallback path, or optional student-provisioning path end to end; validate those separately before delivery.

If SharePoint setup or student provisioning falls back to DeviceLogin, open https://microsoft.com/devicelogin and then enter the current code shown by the script. On a first-time run, separate delegated prompts for the SharePoint admin center, tenant root, and target site are expected.

By default the automation is optimized for a clean validated facilitator demo base. If you intentionally maintain a completed facilitator-owned gold source environment, use Set-WorkshopFacilitatorFallbackSource.ps1 to list candidate environments, qualify the chosen source against the fallback manifest, and persist FacilitatorFallback.SourceEnvironmentUrl before you run Invoke-WorkshopFacilitatorFallbackBuild.ps1. The advanced build now refreshes a git-ignored source snapshot at workshop\automation\facilitator-fallback-artifacts.json before copy and writes a git-ignored post-copy repair report at workshop\automation\facilitator-fallback-repair-report.json so connection-reference and environment-variable drift can be reviewed after each rebuild. Keep that gold source and any copied fallback environments facilitator-only; do not use them as the student build path. You can validate either the copied target or the gold source itself with Invoke-WorkshopFacilitatorFallbackValidation.ps1, and override the environment under test with -EnvironmentUrl when needed.

See the Facilitator Guide for the quick facilitator runbook and the full delivery checklist.

PDF Workbooks

Generate printable PDF files for students and facilitators:

cd workshop\automation
npm install
node Generate-WorkshopPDFs.js

Output lands in workshop/pdf-output/:

#	Student PDFs	Facilitator PDFs
01	Welcome & Overview	Facilitator Guide
02	Day 1 Workbook (Labs 00–12)	Environment Readiness Pack
03	Day 2 Workbook (Labs 13–24)	Session Splitting Guide
04	Optional Developer Lab (Lab 25)	Lab Timing Guide
05		Slide Deck Outline (from slide-deck-outline.md, not the PPTX decks)
06		Lab Validation Reference

Generate a subset with --only: node Generate-WorkshopPDFs.js --only S2,F1

Key Scenario Names

Name	Purpose
Contoso IT	SharePoint site for Day 1 grounding
Contoso Helpdesk Agent	Day 1 custom agent
Hiring Agent	Day 2 orchestrator agent
Operative	Day 2 Dataverse solution
Hiring Hub	Day 2 model-driven app
AgentCreators	Security group for authoring permissions

License

This workshop content is provided for educational use. See the repository license for details.