Examples — end-to-end scenarios
Each scenario is a complete walkthrough: CLI commands, files to create or edit, code, manifest changes, and sideload steps. Pick the closest match and adapt.
| Scenario | What it demonstrates | File |
|---|---|---|
| Echo bot | Minimum viable bot | references/scenarios/echo-bot.md |
| AI quote agent | ChatPrompt + streaming in 1:1 |
references/scenarios/ai-quote-agent.md |
| Adaptive Card form | Card with inputs + card.action.<id> |
references/scenarios/adaptive-card-form.md |
| Message-extension search | message.ext.query + results list |
references/scenarios/message-extension-search.md |
| SSO + Graph bot | OAuth → on-behalf-of → api.graph.me.events.list |
references/scenarios/sso-graph-bot.md |
How to use a scenario
- Read it top-to-bottom once.
- Run the listed
teams project new …(orteams project new + add-featureif extending an existing project). - Apply each diff in order — they are written to compile after every step, not only at the end.
- Run
npm run devand follow the verification block. - Sideload via the Teams Developer Portal.
Scenarios are intentionally short. Cross-link to the deep-dive skills (messaging, adaptive-cards, ai-agents, authentication, graph-integration) when you need more depth on a step.