Generated banner for Teams App Developer
Generated logo for Teams App Developer

Teams App Developer

MicrosoftOfficialPublished by Microsoft

  • Skill
  • Tool integration
  • Software development
  • MIT
  • Medium risk

From the author

Builds, tests, and deploys Microsoft 365 apps and agents for Teams and Copilot. Includes sub-skills for project creation, local testing, cloud deployment, troubleshooting, and Slack-to-Teams migration. USE FOR: Teams agent, bot, tab, message extension, Declarative Agents, Custom Engine Agents, local testing, Agents Playground, Azure resource provision, remote deployment, Slack to Teams migration, cross-platform bot development, Block Kit to Adaptive Cards conversion. DO NOT USE FOR: general web development, non-bot/non-Teams projects.
— the description by Microsoft

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

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/teams-app-developer/download
  2. Unzip 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

  1. Testing Strategy: Recommend Agents Playground first (faster, no M365 needed). Use Teams workflow only if user explicitly requests it.

  2. Environment Variables: NEVER hardcode secrets or make up placeholder values. Always ask users for real values.

  3. Error Handling: Read error messages carefully. Check env/.env.local, .localConfigs, and atk auth list. Common pitfalls:

    • AADSTS7000229 → aadApp/create missing generateServicePrincipal: true in YAML — add it and re-provision

    • Missing TENANT_ID in .localConfigs → SDK uses wrong token authority → 401 from Bot Connector

    • 401 persists after auth fix → devtunnel URL may be blacklisted — create a fresh tunnel

    • See troubleshoot/troubleshoot.md for full diagnostic steps

  4. Long-Running Commands — WAIT for completion:

    • atk new, atk provision, atk deploy can take several minutes

    • Always wait for completion before running the next step (timeout 120000ms+)

  5. Local Service Startup — Hangs terminal (expected):

    • npm run dev, npm start, python app.py, devtunnel host, etc. will hang — the process keeps running indefinitely

    • ALWAYS run as a background process (isBackground=true) — NEVER use isBackground=false for these commands

    • Do 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

  6. Monitor App Logs: Periodically check background terminal output for runtime errors. If the app crashes, read the error, fix the root cause, and restart.

  7. Telemetry Tagging: Before running any atk CLI commands, set the session environment variable so all CLI invocations are tagged as skill-initiated:

    export ATK_CLI_SKILL=true

    Run this once at the start of the session. All subsequent atk commands in the same terminal will inherit it.

ATK CLI Setup

atk --version  # Must be > 1.1.5-beta

If ATK is not found or version is too old:

npm i -g @microsoft/m365agentstoolkit-cli@beta

CLI Global Options

OptionMeaningRecommendation
-iInteractive modeAlways use -i false in automation to avoid hanging
-fProject folderDefault 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.
-hCommand helpUse atk <command> -h for quick syntax checks

Sub-Skills

Sub-SkillWhen to UseReference
create-projectScaffold new project from template, choose template, atk newcreate-project/create-project.md
test-playgroundTest locally with Agents Playground, agentsplayground, quick testingtest-playground/test-playground.md
test-teamsRun on Teams, devtunnel, sideload, Teams testing, test in Copilottest-teams/test-teams.md
provision-deployProvision Azure resources, deploy to cloud, atk provision, atk deployprovision-deploy/provision-deploy.md
troubleshootFix errors, 401, port conflicts, YAML errors, stale botstroubleshoot/troubleshoot.md
slack-to-teamsMigrate Slack bot to Teams, cross-platform bridging, Block Kit to Adaptive Cardsslack-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 IntentWorkflow (read in order)
Build new app from scratchcreate-project → test-playground
Test existing project locallytest-playground (recommended) or test-teams
Deploy to Azureprovision-deploy
Fix broken bottroubleshoot → re-test
Migrate Slack bot to Teamsslack-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

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

  1. The @microsoft/teams.botbuilder package provides a backward-compatibility layer between legacy BotBuilder bots (using TeamsActivityHandler from botbuilder) 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 -- botbuilder

  2. For new projects, always use @microsoft/teams.apps directly. The compat layer adds overhead and limits access to newer SDK v2 features (plugin system, streaming, DevTools, MCP, A2A). Only use @microsoft/teams.botbuilder for incremental migration of existing bots. github.com/microsoft/teams.ts

  3. Legacy BotBuilder bots use TeamsActivityHandler with method overrides (onMessage(), onMembersAdded(), onTeamsChannelCreated(), etc.) and the TurnContext object. Teams SDK v2 uses App with app.on() route handlers and a destructured activity context. The compat layer bridges these two models. github.com/microsoft/teams.ts -- botbuilder

  4. The migration path from BotBuilder to SDK v2 follows: (a) install @microsoft/teams.botbuilder alongside existing botbuilder packages, (b) wrap the existing handler with the compat layer, (c) incrementally move handlers from TeamsActivityHandler overrides to app.on() routes, (d) once all handlers are migrated, remove the compat layer and botbuilder dependencies entirely. github.com/microsoft/teams.ts -- botbuilder

  5. Key API differences between BotBuilder and SDK v2: BotBuilder uses TurnContext.sendActivity() while SDK v2 uses ctx.send() / ctx.reply(); BotBuilder uses CardFactory.adaptiveCard() while SDK v2 sends raw attachment objects; BotBuilder uses ActivityHandler.run() in an Express middleware while SDK v2 uses app.start(port). github.com/microsoft/teams.ts

  6. BotBuilder's state management (ConversationState, UserState, MemoryStorage) does not carry over. SDK v2 uses IStorage from @microsoft/teams.common and LocalMemory from @microsoft/teams.ai. Migrate state stores as part of the transition. github.com/microsoft/teams.ts -- common

  7. BotBuilder's dialog system (ComponentDialog, WaterfallDialog) is not available in SDK v2. Replace with SDK v2 dialog.open / dialog.submit invoke routes and Adaptive Card-based task modules, or use AI-driven conversation flows with ChatPrompt. github.com/microsoft/teams.ts

  8. Authentication patterns differ: BotBuilder uses OAuthPrompt and TokenResponseEventHandler, while SDK v2 uses oauth in AppOptions with ctx.isSignedIn, ctx.signin(), and ctx.userGraph. Migrate OAuth configuration to the App constructor. github.com/microsoft/teams.ts -- apps

  9. The @examples/botbuilder example in the Teams SDK v2 repository demonstrates the compat layer usage. Reference it for concrete interop patterns. github.com/microsoft/teams.ts -- examples/botbuilder

  10. Before 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: false
Q2 — 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: false
Q3 — 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: false
defaults table
QuestionDefault
Q1Full rewrite
Q2No dialogs
Q3MemoryStorage

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.apps directly 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 with dialog.open/dialog.submit invoke routes and Adaptive Card forms.

  • Mixing TurnContext and SDK v2 context: During migration, do not pass BotBuilder's TurnContext into SDK v2 handlers or vice versa. They are incompatible objects with different method signatures.

  • Forgetting to migrate state stores: BotBuilder's ConversationState/UserState backed by MemoryStorage does not work in SDK v2. Migrate to IStorage/LocalStorage from @microsoft/teams.common.

  • Keeping botbuilder dependency after full migration: Once all handlers are moved to SDK v2 patterns, remove botbuilder, botbuilder-dialogs, and @microsoft/teams.botbuilder from package.json to reduce bundle size.

  • Expecting identical behavior: SDK v2 handles some activities differently than BotBuilder (e.g., @mention text stripping, conversation update events). Test each migrated handler against real Teams clients.

  • Not referencing the botbuilder example: The @examples/botbuilder directory 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