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/teams-python.md

teams-python

purpose

Microsoft Teams SDK for Python patterns — translating TypeScript Teams AI concepts to Python equivalents using microsoft_teams.

rules

  1. Install the Teams Python SDK packages: pip install microsoft-teams-apps microsoft-teams-ai microsoft-teams-openai. The SDK is modular — microsoft_teams.apps for the App framework, microsoft_teams.ai for AI/prompts, microsoft_teams.openai for OpenAI model integration. github.com/nicekid1/Microsoft-Teams.ts

  2. Initialize the App with App(client_id=..., client_secret=...) or let it read from CLIENT_ID and CLIENT_SECRET environment variables. The App class is in microsoft_teams.apps. This replaces the TS Application class setup. [teams.py source: app.py]

  3. Register activity handlers using Python decorators: @app.on_message, @app.on_message_pattern(r"regex"), @app.on_conversation_update, @app.on_adaptive_card_action, @app.on_typing, @app.on_message_reaction. This replaces the TS app.message(), app.activity() method-call patterns. [teams.py source: activity_handlers.py]

  4. All handlers are async def and receive an ActivityContext[T] parameter, where T is the specific activity type (e.g., MessageActivity, ConversationUpdateActivity). This replaces the TS TurnContext pattern. [teams.py source: activity_context.py]

  5. Use await ctx.send(message) to send a message and await ctx.reply(message) to reply in a thread. The send method accepts strings, ActivityParams, or AdaptiveCard objects. This replaces the TS context.sendActivity() pattern. [teams.py source: activity_context.py]

  6. The App uses FastAPI internally (via HttpPlugin) with uvicorn as the ASGI server. Start with asyncio.run(app.start(port=3978)). Default endpoint is POST /api/messages. This replaces the TS Express-based setup. [teams.py source: http_plugin.py]

  7. For AI integration, create a ChatPrompt with an AI model and call await prompt.send(input, instructions=...). The model is typically OpenAICompletionsAIModel or OpenAIResponsesAIModel from microsoft_teams.openai. This replaces the TS ChatPrompt / OpenAIModel classes. [teams.py source: chat_prompt.py]

  8. Define AI functions using Function[ParamsType] with Pydantic models for parameter schemas. The handler can be sync or async and returns a string. This replaces the TS function-calling pattern with its TypeScript interfaces. [teams.py source: function.py]

  9. Access Microsoft Graph via ctx.user_graph (user-delegated) or ctx.app_graph (app-only). Check ctx.is_signed_in before using user Graph. Initiate sign-in with await ctx.sign_in(SignInOptions(...)). This replaces the TS context.graph patterns. [teams.py source: activity_context.py]

  10. Use ListMemory from microsoft_teams.ai for conversation history in AI prompts. Pass it to ChatPrompt(model=model, memory=memory). Supports push, get_all, and set_all operations. This replaces the TS MemoryStorage pattern. [teams.py source: memory.py]

  11. Add custom HTTP routes using @app.http.get("/path") or @app.http.post("/path") — these are FastAPI route decorators exposed through the HttpPlugin. This replaces TS custom Express routes. [teams.py source: http_plugin.py]

  12. Use Pydantic BaseModel subclasses for typed data throughout (function parameters, API models, card data). This replaces TypeScript interfaces and type definitions. [teams.py patterns]

  13. The SDK requires Python 3.12+ and uses modern Python features (type hints, dataclasses, protocols, async/await). [teams.py pyproject.toml]

patterns

Basic echo bot
import asyncio
from microsoft_teams.apps import App, ActivityContext
from microsoft_teams.api import MessageActivity

app = App()

@app.on_message
async def handle_message(ctx: ActivityContext[MessageActivity]):
    await ctx.reply(f"Echo: {ctx.activity.text}")

if __name__ == "__main__":
    asyncio.run(app.start(port=3978))
AI bot with function calling
import asyncio
from microsoft_teams.apps import App, ActivityContext
from microsoft_teams.api import MessageActivity
from microsoft_teams.ai import ChatPrompt, Function, ListMemory
from microsoft_teams.openai import OpenAICompletionsAIModel
from pydantic import BaseModel

app = App()
model = OpenAICompletionsAIModel(model="gpt-4")
memory = ListMemory()

class SearchParams(BaseModel):
    query: str
    """The search query"""

async def search_handler(params: SearchParams) -> str:
    return f"Results for: {params.query}"

@app.on_message
async def handle_message(ctx: ActivityContext[MessageActivity]):
    prompt = ChatPrompt(model=model, memory=memory)
    prompt.with_function(Function[SearchParams](
        name="search",
        description="Search for information",
        parameter_schema=SearchParams,
        handler=search_handler,
    ))

    result = await prompt.send(
        input=ctx.activity.text,
        instructions="You are a helpful assistant.",
    )

    if result.response.content:
        await ctx.send(result.response.content)

if __name__ == "__main__":
    asyncio.run(app.start(port=3978))
Adaptive Card handling
import asyncio
from microsoft_teams.apps import App, ActivityContext
from microsoft_teams.api import MessageActivity, MessageSubmitActionInvokeActivity

app = App()

@app.on_message_pattern(r"^card$")
async def send_card(ctx: ActivityContext[MessageActivity]):
    from microsoft_teams.cards import AdaptiveCard
    card = AdaptiveCard()
    card.add_text_block("Feedback Form")
    card.add_text_input("feedback", placeholder="Your feedback")
    card.add_submit_action("Submit")
    await ctx.send(card)

@app.on_message_submit_action
async def handle_card_action(ctx: ActivityContext[MessageSubmitActionInvokeActivity]):
    data = ctx.activity.value
    await ctx.reply(f"Got feedback: {data}")

if __name__ == "__main__":
    asyncio.run(app.start(port=3978))

pitfalls

  • Python 3.12+ required: The Teams Python SDK uses modern Python features that require 3.12 or later. Earlier versions will fail at import time.

  • All handlers are async: Unlike Slack Bolt Python which supports sync handlers, Teams Python SDK handlers must all be async def. Forgetting async or await causes runtime errors.

  • Package naming: Import from microsoft_teams.apps, microsoft_teams.ai, etc. — not teams_ai or botbuilder. The namespace is microsoft_teams.

  • Port 3978 vs 3000: Teams SDK defaults to port 3978 (Teams convention), not 3000 (Slack convention). When running both in one process, configure different ports.

  • No sync adapter: Unlike Slack Bolt which has both sync and async paths, Teams Python SDK is async-only with FastAPI. No Flask adapter exists.

references

  • https://github.com/nicekid1/Microsoft-Teams.ts (Python SDK repo)

  • teams.py source: packages/apps/src/microsoft_teams/apps/

  • teams.py source: packages/ai/src/microsoft_teams/ai/

  • teams.py source: packages/openai/src/microsoft_teams/openai/

instructions

This expert covers the Microsoft Teams SDK for Python — the Python equivalent of @microsoft/teams-ai. Use it when building Teams bots in Python (Tier 2 or standalone), translating TypeScript Teams AI patterns to Python, or setting up the FastAPI-based Teams bot server. All TS Teams experts provide the architectural patterns — this expert provides the Python API mappings.

Pair with: Teams TS experts (conceptual architecture — translate to Python). bridge/python-cross-platform.md for unified Python server with both Slack and Teams. slack/bolt-python.md for the Slack side of a Python dual-platform bot.

research

Deep Research prompt:

"Write a micro expert mapping Microsoft Teams AI TypeScript patterns to Python equivalents using the microsoft_teams SDK. Cover App initialization (client_id, client_secret, env vars), decorator-based activity routing (@app.on_message, @app.on_message_pattern, @app.on_adaptive_card_action), ActivityContext[T] parameter (send, reply, stream, sign_in, is_signed_in, user_graph), ChatPrompt with OpenAICompletionsAIModel, Function[Params] with Pydantic BaseModel schemas, ListMemory for conversation history, FastAPI/uvicorn web framework, Adaptive Cards (AdaptiveCard class), custom HTTP routes via app.http, and key differences from TS (async-only, Pydantic vs interfaces, Python 3.12+). Source from teams.py packages source code."

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