Morning Session

Copilot Studio fundamentals for all attendees

Course delivery kit

A fast first win changes the room

Open with momentum. The point of the morning is not depth. It is confidence. Tell the room they only need one working flow before lunch.

Sign-in should feel easy

Presenter cue

Name only four surfaces: create, instruct, ground, test.

Do not narrate every menu. Keep the interface tour anchored in user intent so beginners do not feel lost.

The interface should feel familiar fast

Look for

• create
• instructions
• knowledge
• test chat

If you have a real screenshot, replace the placeholder and point visually rather than verbally.

A first agent needs only role and boundaries

Minimal recipe

Role. Goals. Boundaries.

You are a helpful assistant for public-facing utility questions.

Goals:
- explain clearly
- stay grounded

Boundaries:
- do not invent details
- say when information is missing

Say out loud that this is intentionally short. The teaching point is that behavior can move before any extra data or tools are added.

Test prompts should reveal the edges

Good question

Clear and answerable

Ambiguous question

Forces a follow-up

Impossible question

Forces uncertainty handling

This is where attendees usually understand why boundaries matter. Make them test all three question types.

Good files beat clever prompts

Transition from instructions to grounding by saying that the fastest path to usefulness is often a clean document, not a more elaborate prompt.

Choice creates energy in the lab

Zones brief

Word document

Solar capacity

Spreadsheet

Price history

Spreadsheet or CSV

Keep the class aligned by giving structured choice rather than open-ended choice. Variety helps without creating chaos.

Grounding works when the source is clean

Teaching line

When the answers are weak, inspect the source before rewriting the prompt.

This is one of the most useful habits to teach. It reframes troubleshooting around source quality, not just prompt wording.

Website knowledge makes the pattern feel real

Pick pages that are

• factual
• stable
• easy to summarize

Use a boring but factual page. Avoid marketing-heavy pages because they distract from the grounding lesson.

MCP should feel useful before it feels technical

Morning message

MCP is how agents gain structured access to outside capabilities.

Do not teach implementation here. This is just a bridge to the afternoon build track.

Publishing turns a private demo into a shared tool

Frame publishing as ownership and governance, not just as a final button. That lands better with mixed audiences.

By lunch everyone should feel capable

One agent

Working and testable

One grounding path

File or website

One clear next step

Afternoon build or applied use case

Close the morning with reassurance. The afternoon can go deeper, but the morning should already feel successful on its own.