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-dotnet.md

teams-dotnet

purpose

Microsoft Teams SDK for .NET (C#) patterns — app initialization, activity handling, AI integration, and Adaptive Cards for Tier 3 C# projects.

rules

  1. Add the NuGet packages: Microsoft.Teams.Apps, Microsoft.Teams.AI, Microsoft.Teams.AI.Models.OpenAI, and Microsoft.Teams.Plugins.AspNetCore. The SDK targets .NET 8+ and uses the modern minimal API pattern. [teams.net source: Libraries/]

  2. Initialize with ASP.NET Core dependency injection: builder.AddTeams() registers core Teams services, then app.UseTeams() returns the App instance for handler registration. When no ClientId is configured, pass skipAuth: true to disable auth validation: builder.AddTeams(skipAuth: true). This replaces the TS Application.create() pattern. [teams.net source: HostApplicationBuilder.cs]

  3. Register activity handlers using fluent methods: teams.OnMessage(async (context, ct) => { ... }). Supports pattern matching: teams.OnMessage(@"^hi$", async (context, ct) => { ... }). Handlers are checked in registration order — first match wins. [teams.net source: App.cs]

  4. All handlers receive IContext<TActivity> and CancellationToken. Access the activity via context.Activity, the API client via context.Api, storage via context.Storage, and logger via context.Log. This replaces the TS TurnContext pattern. [teams.net source: Context.cs]

  5. Send messages with await context.Send("text", ct) or await context.Reply("reply", ct). The Send method accepts strings, ActivityParams, or AdaptiveCard objects. For typing indicators, use await context.Typing(cancellationToken: ct). [teams.net source: Context.cs]

  6. Handle Adaptive Card actions with teams.OnAdaptiveCardAction(async (context, ct) => { ... }). Return ActionResponse.Message("text") from the handler. Access submitted data via context.Activity.Value?.Action?.Data. [teams.net source: App.cs]

  7. For AI integration, create an OpenAIChatModel (from Microsoft.Teams.AI.Models.OpenAI) with Azure OpenAI or OpenAI credentials. Create a prompt with new OpenAIChatPrompt(model) and call await prompt.Send(input, ct). [teams.net source: OpenAIChatPrompt.cs]

  8. Define AI functions using C# attributes: decorate a class with [Prompt] and methods with [Function]. Parameters use [Param]. Or use the fluent API: prompt.Function("name", "desc", async (string param) => result). This replaces TS function-calling with type-safe C# patterns. [teams.net source: Annotations/]

  9. Use IContext tuple deconstruction for concise handler code: var (log, api, activity) = context;. This is idiomatic C# that has no TS equivalent. [teams.net source: Context.cs]

  10. For OAuth/SSO, call await context.SignIn(new OAuthOptions { ConnectionName = "name" }, ct). Check context.IsSignedIn and access context.UserGraphToken for Microsoft Graph calls. Access Graph via context.UserGraph (user) or context.AppGraph (app-only). [teams.net source: activity_context.py]

  11. The SDK uses a plugin architecture. AspNetCorePlugin handles HTTP ingestion (registered by AddTeams()). Add DevToolsPlugin for development. Custom plugins implement IPlugin with lifecycle hooks (OnInit, OnStart, OnActivity). [teams.net source: IPlugin.cs]

  12. Default endpoint is POST /api/messages on port 5000 (ASP.NET default) or the PORT/ASPNETCORE_URLS environment variable. This replaces the TS Express endpoint pattern. [teams.net source: AspNetCorePlugin]

patterns

Basic echo bot with ASP.NET Core
using Microsoft.Teams.Apps.Activities;
using Microsoft.Teams.Apps.Extensions;
using Microsoft.Teams.Plugins.AspNetCore.Extensions;

var builder = WebApplication.CreateBuilder(args);
builder.AddTeams(skipAuth: true);

var app = builder.Build();
var teams = app.UseTeams();

teams.OnMessage(async (context, ct) =>
{
    await context.Send($"Echo: {context.Activity.Text}", ct);
});

app.Run();
AI bot with function calling
using Azure.AI.OpenAI;
using System.ClientModel;
using Microsoft.Teams.AI.Models.OpenAI;
using Microsoft.Teams.Apps.Activities;
using Microsoft.Teams.Apps.Extensions;
using Microsoft.Teams.Plugins.AspNetCore.Extensions;

var builder = WebApplication.CreateBuilder(args);
builder.AddTeams(skipAuth: true);

var azureClient = new AzureOpenAIClient(
    new Uri(builder.Configuration["AzureOpenAIEndpoint"]!),
    new ApiKeyCredential(builder.Configuration["AzureOpenAIKey"]!)
);
var model = new OpenAIChatModel("gpt-4", azureClient);

var app = builder.Build();
var teams = app.UseTeams();

teams.OnMessage(async (context, ct) =>
{
    await context.Typing(cancellationToken: ct);

    var prompt = new OpenAIChatPrompt(model);
    prompt.Function("get_weather", "Get weather for a location",
        async (string location) => $"Sunny, 72F in {location}");

    var result = await prompt.Send(context.Activity.Text, ct);
    if (result.Content != null)
    {
        await context.Send(result.Content, ct);
    }
});

app.Run();
Attribute-based prompt class
using Microsoft.Teams.AI.Annotations;

[Prompt]
[Prompt.Instructions("You are a helpful assistant that can search and summarize.")]
public class AssistantPrompt(IContext<IActivity> context)
{
    [Function]
    [Function.Description("Search the knowledge base")]
    public async Task<string> Search([Param] string query)
    {
        // Call your search API
        return $"Found 3 results for: {query}";
    }

    [Function]
    [Function.Description("Get the current user's name")]
    public string GetUserName()
    {
        return context.Activity.From?.Name ?? "Unknown";
    }
}

// Usage in handler:
teams.OnMessage(async (context, ct) =>
{
    var prompt = OpenAIChatPrompt.From(model, new AssistantPrompt(context));
    var result = await prompt.Send(context.Activity.Text, ct);
    if (result.Content != null)
        await context.Send(result.Content, ct);
});

pitfalls

  • .NET 8+ required: The SDK uses modern C# features (primary constructors, collection expressions) that require .NET 8 or later.

  • No Slack SDK for C#: No official Slack SDK exists for .NET. For the Slack side in Tier 3 C# projects, use REST API patterns from experts/bridge/rest-only-integration-ts.md.

  • CancellationToken everywhere: All async methods require passing CancellationToken. Forgetting it compiles but prevents graceful shutdown.

  • AddTeams() before Build(): The builder.AddTeams() call must happen before builder.Build(). Calling UseTeams() without AddTeams() throws at startup.

  • Handler registration order matters: Handlers are checked in order. Put specific patterns (OnMessage(@"^help$")) before generic handlers (OnMessage(...)) or the generic handler catches everything.

  • ActionResponse return type: OnAdaptiveCardAction handlers must return an ActionResponse, not just call Send. Returning null causes a 500 error.

references

  • teams.net source: Libraries/Microsoft.Teams.Apps/App.cs

  • teams.net source: Libraries/Microsoft.Teams.AI.Models.OpenAI/OpenAIChatPrompt.cs

  • teams.net source: Samples/Samples.AI/Program.cs

  • teams.net source: Samples/Samples.Echo/Program.cs

instructions

This expert covers the Microsoft Teams SDK for .NET — the C# equivalent of @microsoft/teams-ai. Use it for Tier 3 C# projects that need Teams SDK patterns. C# projects have SDK support for Teams but not Slack. For the Slack side, pair with experts/bridge/rest-only-integration-ts.md to implement REST-based Slack integration.

Pair with: bridge/rest-only-integration-ts.md for REST-based Slack integration (the unsupported side). TS Teams experts for conceptual architecture reference.

research

Deep Research prompt:

"Write a micro expert on Microsoft Teams SDK for .NET (C#). Cover ASP.NET Core setup (AddTeams, UseTeams, minimal API), activity handler registration (OnMessage with regex, OnAdaptiveCardAction, OnConversationUpdate), IContext<TActivity> (Send, Reply, Typing, Activity, Api, Storage, Log, SignIn, IsSignedIn), OpenAIChatModel/OpenAIChatPrompt for AI, function calling (attribute-based [Prompt][Function][Param] and fluent API), Adaptive Cards (creating and handling actions), plugin architecture (IPlugin lifecycle), state management (IStorage), and context tuple deconstruction. Source from teams.net Libraries source code and Samples."

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