| name | teams-dev |
| description | Use this skill whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring, debugging, or just asking questions. Covers bots, message extensions, embedded web apps, Adaptive Cards, dialogs, SSO, infrastructure, the Teams Developer CLI/SDK, and general Teams platform queries. If the word "Teams" appears, err on the side of invoking this skill. |
| teams_cli_version | 3.0.* |
Teams Bot Development & Infrastructure
This skill helps you create and manage Microsoft Teams bots using the Teams Developer CLI. Covers both bot application development (creating bot code) and infrastructure management (bot registration, SSO, credentials).
IMPORTANT: Use information and guidance provided within this skill and its reference guides. You may also use external public documentation only when it is explicitly linked from this skill or those guides. Do NOT perform arbitrary web searches or rely on unlisted external sources.
Workflow Routing
Based on the user's request, route to the appropriate guide or handle directly:
Complex Workflows (Use References)
Creating bot application code:
- Read and follow the Bot Application Development guide
- This covers: Scaffolding a new bot project with
teams project new (TypeScript/C#/Python, templates, connecting to infrastructure)
Integrating Teams into an existing server:
- Read and follow the Integrate Existing Server guide
- This covers: Adding Teams bot functionality to an existing server using built-in adapters (ExpressAdapter for TypeScript, FastAPIAdapter for Python) or a custom adapter for any framework
Setting up bot infrastructure (Teams-managed bot & credentials):
Setting up SSO authentication:
- Read and follow the SSO Setup guide
- This covers: Bot migration → AAD app configuration → OAuth connection → Manifest update → Verification
- Prerequisites: Existing bot (teamsAppId, botId), az CLI authenticated
Troubleshooting errors:
Simple Operations (Handle Directly)
For simple queries and updates, handle directly using the commands below:
List all apps:
teams app list
View app details:
teams app get <teamsAppId> --json
Check authentication status:
teams status
Update CLI to latest version:
teams self-update
Common Operations
Update Bot Endpoint
Use case: Endpoint URL changed (new ngrok/devtunnels session)
Command:
teams app update <teamsAppId> --endpoint "https://new-endpoint-url/api/messages"
When to use:
- Ngrok URL changed (new session)
- Devtunnels URL changed
- Switching between different local development tunnels
Note: If the endpoint domain changed (not just the path), the CLI automatically updates validDomains in the manifest. This requires the user to reinstall the app in Teams for the change to take effect.
Update Teams Developer CLI
Use case: Update the Teams Developer CLI to the latest version (recommended to stay current with new features and bug fixes)
Command:
teams self-update
When to use:
- Periodically update to get latest features
- After bug reports or known issues
- When new CLI features are announced
Expected: CLI downloads and installs the latest version
View App Details
Command:
teams app get <teamsAppId> --json
Use case: Check current bot configuration, verify settings
List All Apps
Command:
teams app list
Use case: See all Teams apps you've created
Resources
Teams SDK Documentation (llms.txt — optimized for LLM consumption):
Development Tunnels: See the Bot Infrastructure Setup guide for devtunnel setup instructions.
