Teams App Developer
MicrosoftOfficialPublished by Microsoft
- Skill
- Tool integration
- Software development
- MIT
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The teams-app-developer skill provides a structured framework for managing the lifecycle of Microsoft 365 agents and Teams applications. It leverages the ATK CLI to handle project scaffolding, local testing via the Agents Playground, cloud provisioning on Azure, and troubleshooting. The skill includes specialized guidance for migrating Slack bots to Teams, including converting Block Kit UI to Adaptive Cards, and provides access to an extensive library of micro-expert documentation for cross-platform development.
What it does
- Scaffolds new Microsoft 365 agents and Teams applications from templates.
- Facilitates local testing using the Agents Playground or Teams-specific environments.
- Automates Azure resource provisioning and cloud deployment workflows.
- Provides diagnostic procedures for common authentication and configuration errors.
- Supports migration of Slack bots to the Teams platform.
- Manages project configuration and environment variables for ATK-based projects.
When to use it
- When starting a new Teams app, bot, or Declarative Agent project.
- When you need to test an agent locally before deploying to the cloud.
- When migrating existing Slack bots to the Microsoft Teams ecosystem.
- When troubleshooting deployment or authentication issues in a Teams project.
- When you need to provision Azure infrastructure for a Teams application.
Advantages
- Streamlines the development lifecycle with standardized CLI commands.
- Reduces development time by offering a local testing playground.
- Provides expert-level guidance for complex cross-platform migrations.
- Ensures consistent configuration management across development environments.
- Includes robust error-handling protocols for common platform-specific pitfalls.
Usage examples
- “Create a new Teams bot project using the default template.”
- The agent will initialize a new project folder, configure the necessary YAML files, and guide you through the initial setup using the ATK CLI.
- “How do I migrate my Slack bot to Microsoft Teams?”
- The agent will initiate the slack-to-teams workflow, providing access to cross-platform bridging experts and guidance on converting UI components.
- “My Teams bot is returning a 401 error, how do I fix it?”
- The agent will trigger the troubleshooting workflow, checking your environment variables, tunnel status, and authentication configuration.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/teams-app-developer/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip teams-app-developer.zip -d .agents/skills
Documentation by Microsoft
Microsoft 365 Agents Toolkit Skill
Build Microsoft 365 agents and Teams apps using the ATK CLI.
AI Behavior Guidelines
Testing Strategy: Recommend Agents Playground first (faster, no M365 needed). Use Teams workflow only if user explicitly requests it.
Environment Variables: NEVER hardcode secrets or make up placeholder values. Always ask users for real values.
Error Handling: Read error messages carefully. Check
env/.env.local,.localConfigs, andatk auth list. Common pitfalls:AADSTS7000229→aadApp/createmissinggenerateServicePrincipal: truein YAML — add it and re-provisionMissing
TENANT_IDin.localConfigs→ SDK uses wrong token authority → 401 from Bot Connector401 persists after auth fix → devtunnel URL may be blacklisted — create a fresh tunnel
See troubleshoot/troubleshoot.md for full diagnostic steps
Long-Running Commands — WAIT for completion:
atk new,atk provision,atk deploycan take several minutesAlways wait for completion before running the next step (timeout 120000ms+)
Local Service Startup — Hangs terminal (expected):
npm run dev,npm start,python app.py,devtunnel host, etc. will hang — the process keeps running indefinitelyALWAYS run as a background process (
isBackground=true) — NEVER useisBackground=falsefor these commandsDo NOT wait for it to "finish" — verify startup by checking output for "listening on port" or tunnel URL
If errors appear, read logs, diagnose, fix, restart
Use a NEW terminal to launch Agents Playground or open Teams sideloading URL
Monitor App Logs: Periodically check background terminal output for runtime errors. If the app crashes, read the error, fix the root cause, and restart.
Telemetry Tagging: Before running any
atkCLI commands, set the session environment variable so all CLI invocations are tagged as skill-initiated:export ATK_CLI_SKILL=trueRun this once at the start of the session. All subsequent
atkcommands in the same terminal will inherit it.
ATK CLI Setup
atk --version # Must be > 1.1.5-betaIf ATK is not found or version is too old:
npm i -g @microsoft/m365agentstoolkit-cli@betaCLI Global Options
| Option | Meaning | Recommendation |
|---|---|---|
-i | Interactive mode | Always use -i false in automation to avoid hanging |
-f | Project folder | Default to be current directory, used when specifying a custom folder. When scaffolding a new project, this is the parent folder where the project folder will be created under. |
-h | Command help | Use atk <command> -h for quick syntax checks |
Sub-Skills
| Sub-Skill | When to Use | Reference |
|---|---|---|
| create-project | Scaffold new project from template, choose template, atk new | create-project/create-project.md |
| test-playground | Test locally with Agents Playground, agentsplayground, quick testing | test-playground/test-playground.md |
| test-teams | Run on Teams, devtunnel, sideload, Teams testing, test in Copilot | test-teams/test-teams.md |
| provision-deploy | Provision Azure resources, deploy to cloud, atk provision, atk deploy | provision-deploy/provision-deploy.md |
| troubleshoot | Fix errors, 401, port conflicts, YAML errors, stale bots | troubleshoot/troubleshoot.md |
| slack-to-teams | Migrate Slack bot to Teams, cross-platform bridging, Block Kit to Adaptive Cards | slack-to-teams/SKILL.md |
MANDATORY: Before executing any workflow, read the corresponding sub-skill document.
Shared References
manifest-and-yaml.md — Project files, YAML config, env vars, .localConfigs flow
commands.md — ATK CLI commands: package, validate, share, collaborate
templates.md — Complete template catalog with language support
experts/ — 100+ micro-expert files: Teams SDK, Slack SDK, cross-platform bridging, deploy, AI models, security, language conversion
docs/ — Platform comparison guides: UI, messaging, identity, infrastructure, feature gaps
Workflow Chains
Match user intent to the smallest valid workflow.
| User Intent | Workflow (read in order) |
|---|---|
| Build new app from scratch | create-project → test-playground |
| Test existing project locally | test-playground (recommended) or test-teams |
| Deploy to Azure | provision-deploy |
| Fix broken bot | troubleshoot → re-test |
| Migrate Slack bot to Teams | slack-to-teams |
MANDATORY: Before executing any slack-to-teams workflow, read slack-to-teams/SKILL.md first. The sub-skill contains a routed expert system with 100+ micro-expert files for cross-platform bot development.
ATK Project Context Resolution
Resolve config values only when missing. If a value is already known in the session, reuse it.
Step 1: Detect ATK Project
If m365agentstoolkit*.yml exists in the current folder, treat it as an ATK project and parse configuration.
Step 2: Resolve Common Configuration
Resolve variables referenced in m365agentstoolkit*.yml. Common variables:
AZURE_OPENAI_API_KEY
AZURE_OPENAI_ENDPOINT
AZURE_OPENAI_DEPLOYMENT_NAME
Step 3: Collect Missing Values
If required values are missing, ask the user for only the missing ones.
Refer to manifest-and-yaml.md for full config-file details.
Files
- ATTRIBUTION.mdAdded by AutoGineer906 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md7.6 KiB
- create-project/create-project.md8.1 KiB
- docs/README.md2.8 KiB
- docs/advanced-features.md7.0 KiB
- docs/feature-gaps.md46.3 KiB
- docs/files-and-links.md4.2 KiB
- docs/identity-and-auth.md4.3 KiB
- docs/infrastructure.md6.7 KiB
- docs/interactive-responses.md4.4 KiB
- docs/messaging-and-commands.md4.5 KiB
- docs/middleware-and-handlers.md4.4 KiB
- docs/ui-components.md6.9 KiB
- docs/workflows.md14.4 KiB
- experts/README.md8.6 KiB
- experts/_expert-ts.md2.2 KiB
- experts/analyzer.md14.0 KiB
- experts/bridge/app-distribution-packaging-ts.md14.2 KiB
- experts/bridge/channel-ops-graph-ts.md15.4 KiB
- experts/bridge/commands-slash-text-ts.md18.5 KiB
- experts/bridge/cross-platform-advisor-ts.md36.4 KiB
- experts/bridge/cross-platform-architecture-ts.md8.3 KiB
- experts/bridge/events-activities-ts.md22.4 KiB
- experts/bridge/files-upload-download-ts.md17.2 KiB
- experts/bridge/identity-oauth-bridge-ts.md19.8 KiB
- experts/bridge/index.md13.0 KiB
- experts/bridge/infra-compute-ts.md14.6 KiB
- experts/bridge/infra-observability-ts.md14.0 KiB
- experts/bridge/infra-secrets-config-ts.md13.2 KiB
- experts/bridge/infra-storage-ts.md14.3 KiB
- experts/bridge/interactive-responses-ts.md19.6 KiB
- experts/bridge/link-unfurl-preview-ts.md17.1 KiB
- experts/bridge/middleware-handlers-ts.md15.4 KiB
- experts/bridge/python-cross-platform.md9.3 KiB
- experts/bridge/rate-limiting-resilience-ts.md17.6 KiB
- experts/bridge/rest-only-integration-ts.md8.4 KiB
- experts/bridge/scheduling-deferred-send-ts.md17.8 KiB
- experts/bridge/shortcuts-extensions-ts.md17.5 KiB
- experts/bridge/transport-socketmode-https-ts.md14.3 KiB
- experts/bridge/ui-app-home-personal-tab-ts.md14.5 KiB
- experts/bridge/ui-block-kit-adaptive-cards-ts.md21.5 KiB
- experts/bridge/ui-legacy-attachments-cards-ts.md11.2 KiB
- experts/bridge/ui-modals-dialogs-ts.md21.4 KiB
- experts/bridge/workflow.composable-platform-ts.md13.7 KiB
- experts/bridge/workflows-automation-ts.md14.3 KiB
- experts/builder.md11.1 KiB
- experts/convert/bulk-conversion-strategy-ts.md12.8 KiB
- experts/convert/dependency-mapping-ts.md8.3 KiB
- experts/convert/index.md3.5 KiB
- experts/convert/java-to-ts-ts.md20.6 KiB
- experts/convert/js-to-ts-ts.md6.2 KiB
- experts/convert/json-serialization-ts.md11.0 KiB
- experts/convert/kotlin-to-ts-ts.md11.2 KiB
- experts/convert/ruby-to-ts-ts.md9.7 KiB
- experts/convert/type-mapping-ts.md10.1 KiB
- experts/deploy/aws-bot-deploy-ts.md14.6 KiB
- experts/deploy/aws-cli-reference-ts.md52.4 KiB
- experts/deploy/azure-bot-deploy-ts.md15.4 KiB
- experts/deploy/azure-cli-reference-ts.md16.9 KiB
- experts/deploy/index.md4.6 KiB
- experts/fallback.md2.1 KiB
- experts/index.md18.9 KiB
- experts/models/anthropic-ts.md7.8 KiB
- experts/models/bedrock-ts.md9.9 KiB
- experts/models/foundry-cloud-ts.md8.1 KiB
- experts/models/foundry-local-ts.md10.6 KiB
- experts/models/index.md5.8 KiB
- experts/models/openai-azure-openai-ts.md8.3 KiB
- experts/models/oss-openai-compatible-ts.md10.7 KiB
- experts/models/transformers-js-ts.md11.6 KiB
- experts/prompt-engineer.md14.7 KiB
- experts/researcher.md2.8 KiB
- experts/security/index.md1.2 KiB
- experts/security/input-validation-ts.md13.8 KiB
- experts/security/secrets-ts.md13.9 KiB
- experts/slack/bolt-assistant-ts.md9.9 KiB
- experts/slack/bolt-events-ts.md9.3 KiB
- experts/slack/bolt-java.md8.9 KiB
- experts/slack/bolt-oauth-distribution-ts.md10.9 KiB
- experts/slack/bolt-python.md9.5 KiB
- experts/slack/cli.app-management.md7.9 KiB
- experts/slack/cli.datastore-env.md8.6 KiB
- experts/slack/cli.getting-started.md8.0 KiB
- experts/slack/cli.local-dev-deploy.md8.4 KiB
- experts/slack/cli.manifest-triggers.md9.9 KiB
- experts/slack/index.md8.9 KiB
- experts/slack/runtime.ack-rules-ts.md9.8 KiB
- experts/slack/runtime.bolt-foundations-ts.md10.7 KiB
- experts/slack/runtime.shortcuts-ts.md11.0 KiB
- experts/slack/runtime.slash-commands-ts.md11.6 KiB
- experts/slack/runtime.socket-mode-ts.md9.5 KiB
- experts/slack/ui.block-kit-ts.md11.5 KiB
- experts/slack/ui.modals-lifecycle-ts.md13.3 KiB
- experts/slack/web-api-proactive-ts.md11.0 KiB
- experts/slack/workflow.slack-automations-ts.md10.2 KiB
- experts/teams/a2a.client-basics-ts.md9.7 KiB
- experts/teams/a2a.orchestrator-patterns-ts.md12.7 KiB
- experts/teams/a2a.server-basics-ts.md11.4 KiB
- experts/teams/ai.chatprompt-basics-ts.md8.1 KiB
- experts/teams/ai.citations-feedback-ts.md6.9 KiB
- experts/teams/ai.conversational-query-ts.md14.2 KiB
- experts/teams/ai.function-calling-design-ts.md9.0 KiB
- experts/teams/ai.function-calling-implementation-ts.md7.7 KiB
- experts/teams/ai.memory-localmemory-ts.md7.3 KiB
- experts/teams/ai.model-setup-ts.md6.6 KiB
- experts/teams/ai.rag-retrieval-ts.md7.4 KiB
- experts/teams/ai.rag-vectorstores-ts.md8.5 KiB
- experts/teams/ai.streaming-ts.md6.9 KiB
- experts/teams/auth.oauth-sso-ts.md10.1 KiB
- experts/teams/compat.botbuilder-interop-ts.md14.6 KiB
- experts/teams/dev.debug-test-ts.md14.1 KiB
- experts/teams/graph.usergraph-appgraph-ts.md9.0 KiB
- experts/teams/index.md9.8 KiB
- experts/teams/mcp.client-basics-ts.md9.5 KiB
- experts/teams/mcp.expose-chatprompt-tools-ts.md9.5 KiB
- experts/teams/mcp.security-ts.md10.4 KiB
- experts/teams/mcp.server-basics-ts.md9.9 KiB
- experts/teams/project.scaffold-files-ts.md12.2 KiB
- experts/teams/runtime.app-init-ts.md10.9 KiB
- experts/teams/runtime.manifest-ts.md12.3 KiB
- experts/teams/runtime.proactive-messaging-ts.md12.6 KiB
- experts/teams/runtime.routing-handlers-ts.md12.3 KiB
- experts/teams/state.storage-patterns-ts.md9.4 KiB
- experts/teams/teams-dotnet.md8.2 KiB
- experts/teams/teams-python.md8.3 KiB
- experts/teams/ui.adaptive-cards-ts.md12.9 KiB
- experts/teams/ui.dialogs-task-modules-ts.md15.1 KiB
- experts/teams/ui.message-extensions-ts.md15.6 KiB
- experts/teams/workflow.approvals-inline-ts.md12.4 KiB
- experts/teams/workflow.message-native-records-ts.md10.6 KiB
- experts/teams/workflow.sharepoint-lists-ts.md9.0 KiB
- experts/teams/workflow.state-driven-events-ts.md12.2 KiB
- experts/teams/workflow.triggers-compose-ts.md10.3 KiB
- experts/update-experts.md10.0 KiB
- provision-deploy/provision-deploy.md4.3 KiB
- test-playground/playground-cli.md4.6 KiB
- test-playground/playground.md4.5 KiB
- test-playground/test-playground.md1.1 KiB
- test-teams/test-teams.md4.9 KiB
- toolkit/README.md4.2 KiB
- toolkit/commands.md2.6 KiB
- toolkit/environments.md12.6 KiB
- toolkit/lifecycle-cli.md17.6 KiB
- toolkit/manifest-and-yaml.md6.0 KiB
- toolkit/playground.md7.6 KiB
- toolkit/publish.md9.3 KiB
- toolkit/templates.md6.7 KiB
- troubleshoot/troubleshoot.md20.2 KiB
experts/teams/compat.botbuilder-interop-ts.md
compat.botbuilder-interop-ts
purpose
Backward compatibility with legacy BotBuilder/Bot Framework bots using @microsoft/teams.botbuilder, migration patterns, and interop decisions.
rules
The
@microsoft/teams.botbuilderpackage provides a backward-compatibility layer between legacy BotBuilder bots (usingTeamsActivityHandlerfrombotbuilder) and the Teams SDK v2 (@microsoft/teams.apps). Use it only when you have an existing BotBuilder codebase that cannot be fully rewritten immediately. github.com/microsoft/teams.ts -- botbuilderFor new projects, always use
@microsoft/teams.appsdirectly. The compat layer adds overhead and limits access to newer SDK v2 features (plugin system, streaming, DevTools, MCP, A2A). Only use@microsoft/teams.botbuilderfor incremental migration of existing bots. github.com/microsoft/teams.tsLegacy BotBuilder bots use
TeamsActivityHandlerwith method overrides (onMessage(),onMembersAdded(),onTeamsChannelCreated(), etc.) and theTurnContextobject. Teams SDK v2 usesAppwithapp.on()route handlers and a destructured activity context. The compat layer bridges these two models. github.com/microsoft/teams.ts -- botbuilderThe migration path from BotBuilder to SDK v2 follows: (a) install
@microsoft/teams.botbuilderalongside existingbotbuilderpackages, (b) wrap the existing handler with the compat layer, (c) incrementally move handlers fromTeamsActivityHandleroverrides toapp.on()routes, (d) once all handlers are migrated, remove the compat layer andbotbuilderdependencies entirely. github.com/microsoft/teams.ts -- botbuilderKey API differences between BotBuilder and SDK v2: BotBuilder uses
TurnContext.sendActivity()while SDK v2 usesctx.send()/ctx.reply(); BotBuilder usesCardFactory.adaptiveCard()while SDK v2 sends raw attachment objects; BotBuilder usesActivityHandler.run()in an Express middleware while SDK v2 usesapp.start(port). github.com/microsoft/teams.tsBotBuilder's state management (
ConversationState,UserState,MemoryStorage) does not carry over. SDK v2 usesIStoragefrom@microsoft/teams.commonandLocalMemoryfrom@microsoft/teams.ai. Migrate state stores as part of the transition. github.com/microsoft/teams.ts -- commonBotBuilder's dialog system (
ComponentDialog,WaterfallDialog) is not available in SDK v2. Replace with SDK v2dialog.open/dialog.submitinvoke routes and Adaptive Card-based task modules, or use AI-driven conversation flows withChatPrompt. github.com/microsoft/teams.tsAuthentication patterns differ: BotBuilder uses
OAuthPromptandTokenResponseEventHandler, while SDK v2 usesoauthinAppOptionswithctx.isSignedIn,ctx.signin(), andctx.userGraph. Migrate OAuth configuration to the App constructor. github.com/microsoft/teams.ts -- appsThe
@examples/botbuilderexample in the Teams SDK v2 repository demonstrates the compat layer usage. Reference it for concrete interop patterns. github.com/microsoft/teams.ts -- examples/botbuilderBefore starting migration, audit the existing bot's feature set: message handlers, card actions, dialogs, proactive messaging, authentication, and any Bot Framework middleware. Map each feature to its SDK v2 equivalent. Features without direct equivalents (BotBuilder dialogs, custom middleware adapters) require the most rework. github.com/microsoft/teams.ts
interview
Q1 — Migration Strategy
question: "Your project has an existing BotBuilder bot. Do you want to use the compatibility layer for incremental migration, or do a full rewrite to SDK v2?"
header: "Strategy"
options:
- label: "Full rewrite (Recommended)"
description: "Rewrite all handlers directly in Teams SDK v2. Cleaner result, full access to streaming/plugins/MCP/A2A. Best for bots with <15 routes or when starting fresh."
- label: "Compat layer (incremental)"
description: "Use @microsoft/teams.botbuilder to run old and new handlers side by side. Migrate one handler at a time. Best for large bots (15+ routes) or tight timelines."
- label: "You Decide Everything"
description: "Accept recommended defaults for all decisions and skip remaining questions."
multiSelect: falseQ2 — Dialog Migration
question: "Does your existing bot use BotBuilder dialogs (WaterfallDialog, ComponentDialog)?"
header: "Dialogs"
options:
- label: "No dialogs"
description: "Bot uses simple message handlers only. No dialog migration needed."
- label: "Yes — replace with Adaptive Cards (Recommended)"
description: "Replace dialog flows with Adaptive Card forms + dialog.open/submit routes. Modern Teams pattern."
- label: "Yes — replace with AI conversation"
description: "Replace dialog flows with ChatPrompt-driven AI conversation. Best for open-ended inputs."
multiSelect: falseQ3 — State Migration
question: "How is your existing bot managing state (ConversationState, UserState)?"
header: "State"
options:
- label: "MemoryStorage (dev only)"
description: "In-memory storage — no migration needed, just switch to SDK v2 IStorage."
- label: "Azure Blob/Cosmos (Recommended)"
description: "Persistent storage — migrate connection config to SDK v2 IStorage adapter. Data format is compatible."
- label: "Custom storage provider"
description: "Custom IStorage implementation — will need to be adapted to SDK v2's IStorage interface."
multiSelect: falsedefaults table
| Question | Default |
|---|---|
| Q1 | Full rewrite |
| Q2 | No dialogs |
| Q3 | MemoryStorage |
patterns
BotBuilder handler vs SDK v2 equivalent
// --- BEFORE: Legacy BotBuilder pattern ---
// Uses TeamsActivityHandler, TurnContext, and method overrides
import { TeamsActivityHandler, TurnContext, MessageFactory } from 'botbuilder';
class LegacyBot extends TeamsActivityHandler {
async onMessage(context: TurnContext): Promise<void> {
const text = context.activity.text?.trim();
if (text === '/help') {
await context.sendActivity(MessageFactory.text('Here is how I can help...'));
} else {
await context.sendActivity(MessageFactory.text(`You said: "${text}"`));
}
}
async onMembersAdded(context: TurnContext): Promise<void> {
for (const member of context.activity.membersAdded || []) {
if (member.id !== context.activity.recipient.id) {
await context.sendActivity('Welcome!');
}
}
}
}
// --- AFTER: Teams SDK v2 pattern ---
// Uses App, app.on(), app.message(), destructured context
import { App } from '@microsoft/teams.apps';
import { ConsoleLogger } from '@microsoft/teams.common';
import { DevtoolsPlugin } from '@microsoft/teams.dev';
const app = new App({
logger: new ConsoleLogger('migrated-bot', { level: 'debug' }),
plugins: [new DevtoolsPlugin()],
});
app.message('/help', async ({ send }) => {
await send('Here is how I can help...');
});
app.on('message', async ({ send, activity }) => {
await send(`You said: "${activity.text}"`);
});
app.on('install.add', async ({ send }) => {
await send('Welcome!');
});
app.start(3978);Migration decision checklist
// When to use the compat layer (@microsoft/teams.botbuilder):
//
// 1. Existing BotBuilder bot with many handlers that cannot be rewritten at once
// 2. Dependencies on BotBuilder-specific libraries or middleware
// 3. Need to run old and new handlers side by side during transition
// 4. Legacy dialog flows (WaterfallDialog) that need time to redesign
//
// When to do a full rewrite (skip the compat layer):
//
// 1. Small bot with few handlers (< 10 routes)
// 2. Starting a new project (always use @microsoft/teams.apps directly)
// 3. Want access to SDK v2-only features:
// - DevtoolsPlugin for debugging
// - Plugin system (MCP, A2A, custom plugins)
// - Streaming responses with stream.emit()
// - Built-in OAuth with ctx.isSignedIn / ctx.signin()
// - app.send() for proactive messaging
// - ChatPrompt for AI integration
// 4. The existing bot has no complex dialog flows
//
// Feature mapping:
// BotBuilder TeamsActivityHandler.onMessage() -> app.on('message')
// BotBuilder TeamsActivityHandler.onMembersAdded() -> app.on('install.add')
// BotBuilder TurnContext.sendActivity() -> ctx.send() / ctx.reply()
// BotBuilder CardFactory.adaptiveCard() -> raw attachment object
// BotBuilder OAuthPrompt -> oauth in AppOptions + ctx.signin()
// BotBuilder ConversationState / UserState -> IStorage + LocalStorage
// BotBuilder WaterfallDialog -> dialog.open/submit + Adaptive Cards
// BotBuilder ActivityHandler.run() + Express -> app.start(port)
// BotBuilder proactiveMessage via ConversationRef -> app.send(conversationId, message)Incremental migration with compat layer
// Step 1: Install the compat package alongside existing botbuilder
// npm install @microsoft/teams.botbuilder @microsoft/teams.apps
// Step 2: Wrap existing handler with compat layer
// (Specific API depends on @microsoft/teams.botbuilder version --
// refer to the package README for exact usage)
// Step 3: Incrementally move handlers to SDK v2 patterns
// Move one handler at a time from the legacy class to app.on() / app.message()
// Test each migration step independently
// Step 4: Remove compat layer when all handlers are migrated
// Remove @microsoft/teams.botbuilder and botbuilder from package.json
// Your final code should look like a standard SDK v2 app:
import { App } from '@microsoft/teams.apps';
import { ConsoleLogger } from '@microsoft/teams.common';
import { DevtoolsPlugin } from '@microsoft/teams.dev';
const app = new App({
clientId: process.env.CLIENT_ID,
clientSecret: process.env.CLIENT_SECRET,
tenantId: process.env.TENANT_ID,
logger: new ConsoleLogger('fully-migrated-bot', { level: 'debug' }),
plugins: [new DevtoolsPlugin()],
});
// All handlers now use SDK v2 patterns
app.on('message', async ({ send, activity }) => {
await send(`Echo: ${activity.text}`);
});
app.on('install.add', async ({ send }) => {
await send('Welcome! Bot has been installed.');
});
app.on('card.action', async ({ activity, send }) => {
const data = activity.value;
await send(`Action received: ${JSON.stringify(data)}`);
});
app.start(process.env.PORT || 3978).catch(console.error);pitfalls
Using the compat layer for new projects: The compat layer exists solely for migration. New projects should always use
@microsoft/teams.appsdirectly for full SDK v2 feature access.Trying to use BotBuilder dialogs in SDK v2:
WaterfallDialog,ComponentDialog, and the BotBuilder dialog stack do not exist in SDK v2. Replace them withdialog.open/dialog.submitinvoke routes and Adaptive Card forms.Mixing
TurnContextand SDK v2 context: During migration, do not pass BotBuilder'sTurnContextinto SDK v2 handlers or vice versa. They are incompatible objects with different method signatures.Forgetting to migrate state stores: BotBuilder's
ConversationState/UserStatebacked byMemoryStoragedoes not work in SDK v2. Migrate toIStorage/LocalStoragefrom@microsoft/teams.common.Keeping
botbuilderdependency after full migration: Once all handlers are moved to SDK v2 patterns, removebotbuilder,botbuilder-dialogs, and@microsoft/teams.botbuilderfrompackage.jsonto reduce bundle size.Expecting identical behavior: SDK v2 handles some activities differently than BotBuilder (e.g.,
@mentiontext stripping, conversation update events). Test each migrated handler against real Teams clients.Not referencing the botbuilder example: The
@examples/botbuilderdirectory in the teams.ts repository contains a working compat layer demo. Always check it before starting migration.
references
instructions
This expert covers backward compatibility and migration from legacy BotBuilder/Bot Framework bots to Teams SDK v2 using @microsoft/teams.botbuilder. Use it when you need to:
Decide whether to use the compat layer or do a full rewrite
Map BotBuilder concepts to SDK v2 equivalents (TeamsActivityHandler -> App, TurnContext -> ctx, OAuthPrompt -> oauth config, WaterfallDialog -> dialog.open/submit)
Plan an incremental migration strategy (install compat, migrate handlers one by one, remove compat)
Understand which BotBuilder features have no direct SDK v2 equivalent
Migrate state management from ConversationState/UserState to IStorage
Migrate authentication from OAuthPrompt to App oauth config
Pair with runtime.app-init-ts.md for SDK v2 App initialization and runtime.routing-handlers-ts.md for the SDK v2 route handler equivalents of BotBuilder method overrides. Pair with runtime.app-init-ts.md for the target SDK v2 App patterns, and runtime.routing-handlers-ts.md for mapping TeamsActivityHandler methods to SDK v2 routes.
research
Deep Research prompt:
"Write a micro expert on interoperability and migration between legacy BotBuilder (botbuilder npm package, TeamsActivityHandler) and Teams SDK v2 (@microsoft/teams.apps) in TypeScript. Cover the @microsoft/teams.botbuilder compat layer, when to use it vs full rewrite, feature mapping (onMessage -> app.on('message'), onMembersAdded -> install.add, TurnContext.sendActivity -> ctx.send, CardFactory -> raw attachments, OAuthPrompt -> oauth config, ConversationState -> IStorage, WaterfallDialog -> dialog.open/submit), incremental migration steps, the @examples/botbuilder reference, and common pitfalls. Include a side-by-side BotBuilder vs SDK v2 code comparison and a migration decision checklist."
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an API key, Needs Python, Needs Node.js
Security
What our scanner noticed· Medium risk
- Possible data-exfiltration endpoints
- Instructions that use the network
- Downloads piped into a shell
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/skills · .github/plugins/microsoft-365-agents-toolkit/skills/teams-app-developer · commit 0696600
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download teams-app-developer.zip