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/deploy/azure-cli-reference-ts.md

azure-cli-reference-ts

purpose

Comprehensive reference of all Azure CLI (az) command groups a developer needs for creating, reading, updating, and deleting resources in a bot or AI agent project on Azure. Use as a lookup companion to azure-bot-deploy-ts.md (step-by-step deployment) — this file maps every relevant CLI surface so you know what commands exist.

rules

  1. This is a reference, not a tutorial. For step-by-step deployment walkthroughs, see azure-bot-deploy-ts.md. This file catalogs every az command group relevant to bot/agent projects.

  2. Always authenticate first. Every command below assumes you have run az login and az account set --subscription <id>. learn.microsoft.com/cli/azure/authenticate-azure-cli

  3. Resource group is required for almost everything. Most commands take --resource-group <rg>. Create one with az group create before provisioning any resources.


1. Bot Service (az bot)

The core resource for registering and managing a bot on Azure.

CommandPurpose
az bot createRegister a new v4 SDK bot (requires --app-type, --appid, --name, --resource-group)
az bot showGet bot details
az bot updateUpdate bot properties (endpoint, description, display name)
az bot deleteDelete a bot registration
az bot downloadDownload bot source code
az bot publishPublish to the bot's associated App Service
az bot prepare-deployAdd deployment config files

Reference: learn.microsoft.com/cli/azure/bot

Bot Channels

Connect a bot to messaging platforms. Each channel group has create, delete, show sub-commands:

Channel GroupPlatform
az bot msteamsMicrosoft Teams
az bot slackSlack
az bot directlineDirectLine (web/custom clients)
az bot webchatWeb Chat embed
az bot facebookFacebook Messenger
az bot telegramTelegram
az bot emailEmail
az bot smsSMS
az bot kikKik
az bot skypeSkype

Reference: learn.microsoft.com/cli/azure/bot/msteams

Bot Auth (az bot authsetting)

Manage OAuth connection settings on a bot:

CommandPurpose
az bot authsetting createCreate an OAuth connection
az bot authsetting showView a connection
az bot authsetting listList all connections
az bot authsetting deleteDelete a connection
az bot authsetting list-providersList available OAuth providers

Reference: learn.microsoft.com/cli/azure/bot/authsetting


2. AI Foundry Agents (az cognitiveservices agent)

For hosted AI agents via Azure AI Foundry:

CommandPurpose
az cognitiveservices agent createCreate hosted agent from container image or source
az cognitiveservices agent showGet agent details
az cognitiveservices agent updateUpdate agent deployment
az cognitiveservices agent deleteDelete agent version(s)
az cognitiveservices agent listList agents
az cognitiveservices agent list-versionsList all versions of an agent
az cognitiveservices agent startStart agent deployment
az cognitiveservices agent stopStop agent deployment
az cognitiveservices agent statusCheck deployment status
az cognitiveservices agent delete-deploymentDelete a deployment
az cognitiveservices agent logsView container logs

Reference: learn.microsoft.com/cli/azure/cognitiveservices/agent


3. Azure OpenAI / Cognitive Services (az cognitiveservices account)

Manage the AI backend your bot/agent calls:

CommandPurpose
az cognitiveservices account createCreate an Azure OpenAI / Cognitive Services account
az cognitiveservices account showView account details
az cognitiveservices account updateUpdate account settings
az cognitiveservices account deleteDelete account
az cognitiveservices account listList all accounts in subscription
az cognitiveservices account keys listGet API keys
az cognitiveservices account keys regenerateRotate keys
az cognitiveservices account deployment createDeploy a model (e.g., GPT-4o)
az cognitiveservices account deployment showView deployment
az cognitiveservices account deployment listList deployments
az cognitiveservices account deployment deleteRemove deployment
az cognitiveservices model listList available models

Reference: learn.microsoft.com/cli/azure/cognitiveservices/account


4. App Registration / Identity (az ad app, az ad sp, az identity)

Every bot needs an app registration for authentication.

App Registration (az ad app)
CommandPurpose
az ad app createCreate Entra ID app registration (gets the appId for bot)
az ad app showView app details
az ad app updateUpdate app properties
az ad app deleteDelete app registration
az ad app listList apps
az ad app credential resetReset password/certificate
az ad app credential listList credentials
az ad app credential deleteRemove a credential
az ad app permissionManage OAuth2 API permissions

Reference: learn.microsoft.com/cli/azure/ad/app

Managed Identity (az identity)
CommandPurpose
az identity createCreate a user-assigned managed identity
az identity showView identity details
az identity listList identities
az identity deleteDelete identity

Reference: learn.microsoft.com/cli/azure/identity

Role Assignments (az role assignment)
CommandPurpose
az role assignment createGrant a role (e.g., "Cognitive Services OpenAI User")
az role assignment listList current assignments
az role assignment deleteRevoke a role

Reference: learn.microsoft.com/cli/azure/role/assignment


5. Hosting / Compute

Web App (az webapp)

Traditional bot hosting on App Service:

CommandPurpose
az webapp createCreate App Service for bot
az webapp show / list / delete / updateStandard CRUD
az webapp start / stop / restartLifecycle management
az webapp deployDeploy artifact (zip, war, jar)
az webapp upCreate + deploy from local workspace
az webapp deployment sourceConfigure source control deployment
az webapp deployment github-actionsConfigure CI/CD via GitHub Actions
az webapp deployment slotManage staging slots
az webapp configApp settings, connection strings, runtime
az webapp identityAssign managed identity to web app
az webapp logView/configure logs

Reference: learn.microsoft.com/cli/azure/webapp

App Service Plan (az appservice plan)
CommandPurpose
az appservice plan createCreate hosting plan (defines SKU/pricing tier)
az appservice plan show / list / update / deleteStandard CRUD

Reference: learn.microsoft.com/cli/azure/appservice/plan

Function App (az functionapp)

Serverless bot hosting:

CommandPurpose
az functionapp createCreate a function app
az functionapp show / list / delete / updateStandard CRUD
az functionapp start / stop / restartLifecycle
az functionapp deployDeploy artifact
az functionapp configApp settings, runtime config
az functionapp identityManaged identity
az functionapp keysManage function keys
az functionapp logView logs

Reference: learn.microsoft.com/cli/azure/functionapp

Container App (az containerapp)

Containerized bot hosting:

CommandPurpose
az containerapp createCreate container app
az containerapp show / list / delete / updateStandard CRUD
az containerapp upCreate + deploy (handles ACR, env, etc.)
az containerapp envManage Container Apps environments
az containerapp secretManage secrets
az containerapp identityManaged identity
az containerapp ingressConfigure ingress / traffic
az containerapp revisionManage revisions
az containerapp logsView logs
az containerapp jobManage background jobs

Reference: learn.microsoft.com/cli/azure/containerapp


6. Infrastructure & Resource Management

Resource Groups (az group)
CommandPurpose
az group createCreate resource group (logical container for all bot resources)
az group show / list / delete / updateStandard CRUD
az group existsCheck existence
az group exportExport as ARM template

Reference: learn.microsoft.com/cli/azure/group

Subscriptions (az account)
CommandPurpose
az account listList subscriptions
az account setSwitch active subscription
az account showShow current subscription

Reference: learn.microsoft.com/cli/azure/account


7. Secrets & Configuration (az keyvault)

CommandPurpose
az keyvault create / show / list / deleteVault CRUD
az keyvault secret setStore a secret (API keys, connection strings)
az keyvault secret showRetrieve a secret
az keyvault secret listList secrets
az keyvault secret deleteDelete a secret
az keyvault set-policyGrant access to the bot's identity

Reference: learn.microsoft.com/cli/azure/keyvault


8. Storage & State

Storage Account (az storage account)

For bot state and blob storage:

CommandPurpose
az storage account createCreate storage account
az storage account show / list / delete / updateStandard CRUD
az storage account show-connection-stringGet connection string
az storage account keys listGet access keys

Reference: learn.microsoft.com/cli/azure/storage/account

Cosmos DB (az cosmosdb)

For bot conversation state:

CommandPurpose
az cosmosdb createCreate Cosmos DB account
az cosmosdb show / list / delete / updateStandard CRUD
az cosmosdb keys listGet access keys
az cosmosdb sql database createCreate a SQL API database
az cosmosdb sql container createCreate a container

Reference: learn.microsoft.com/cli/azure/cosmosdb


9. Monitoring & Diagnostics (az monitor)

CommandPurpose
az monitor log-analytics workspace createCreate Log Analytics workspace
az monitor diagnostic-settings createEnable diagnostics on bot resources
az monitor metrics listView resource metrics
az monitor activity-log listView activity logs
az monitor action-group createSet up alert notifications

Reference: learn.microsoft.com/cli/azure/monitor


patterns

Minimum viable bot/agent CRUD flow

The numbered steps below show the typical order for provisioning a complete bot project from scratch using only az commands:

# 1. Resource group
az group create --name rg-mybot --location eastus

# 2. App registration + secret
APP_ID=$(az ad app create --display-name "MyBot" --query appId -o tsv)
APP_SECRET=$(az ad app credential reset --id $APP_ID --query password -o tsv)
TENANT_ID=$(az account show --query tenantId -o tsv)

# 3. Hosting plan
az appservice plan create --resource-group rg-mybot --name mybot-plan --sku B1 --is-linux

# 4. Web app (or functionapp / containerapp)
az webapp create --resource-group rg-mybot --plan mybot-plan --name mybot-app --runtime "NODE:20-lts"

# 5. Bot registration
az bot create --resource-group rg-mybot --name mybot-bot \
  --app-type SingleTenant --appid $APP_ID --tenant-id $TENANT_ID

# 6. Connect channels
az bot msteams create --resource-group rg-mybot --name mybot-bot
# az bot slack create --resource-group rg-mybot --name mybot-bot ...

# 7. AI backend (Azure OpenAI)
az cognitiveservices account create --resource-group rg-mybot --name mybot-openai \
  --kind OpenAI --sku S0 --location eastus
az cognitiveservices account deployment create --resource-group rg-mybot \
  --name mybot-openai --deployment-name gpt-4o \
  --model-name gpt-4o --model-version "2024-08-06" --model-format OpenAI \
  --sku-name Standard --sku-capacity 10

# 8. Secrets management
az keyvault create --resource-group rg-mybot --name mybot-kv --location eastus
az keyvault secret set --vault-name mybot-kv --name "AppSecret" --value "$APP_SECRET"

# 9. Wire up permissions (managed identity → OpenAI)
az webapp identity assign --resource-group rg-mybot --name mybot-app
PRINCIPAL_ID=$(az webapp identity show --resource-group rg-mybot --name mybot-app --query principalId -o tsv)
OPENAI_ID=$(az cognitiveservices account show --resource-group rg-mybot --name mybot-openai --query id -o tsv)
az role assignment create --assignee $PRINCIPAL_ID \
  --role "Cognitive Services OpenAI User" --scope $OPENAI_ID

# 10. Observability
az monitor diagnostic-settings create --resource rg-mybot/mybot-app \
  --name mybot-diag --logs '[{"enabled":true,"category":"AppServiceHTTPLogs"}]' \
  --workspace <log-analytics-workspace-id>
Teardown (delete everything)
# Delete the entire resource group and all resources within it
az group delete --name rg-mybot --yes --no-wait

# Delete the app registration separately (it lives in Entra ID, not the resource group)
az ad app delete --id $APP_ID
List all resources in a bot project
# See everything in the resource group
az resource list --resource-group rg-mybot --output table

# Check bot channel connections
az bot show --resource-group rg-mybot --name mybot-bot --query "properties.enabledChannels"

# Check OpenAI deployments
az cognitiveservices account deployment list --resource-group rg-mybot --name mybot-openai --output table

pitfalls

  • App Registration lives outside the resource group. Deleting the resource group does not delete the Entra ID app registration. Always clean up with az ad app delete --id <appId> separately.

  • Key Vault soft-delete. Deleted vaults are retained for 90 days by default. Recreating a vault with the same name fails until you purge it: az keyvault purge --name <vault-name>.

  • Cognitive Services region availability. Not all Azure OpenAI models are available in all regions. Check az cognitiveservices model list --location <region> before creating the account.

  • Role assignment propagation delay. After az role assignment create, it can take up to 5 minutes for the assignment to propagate. If your bot gets 403 errors immediately after setup, wait and retry.

  • Managed identity vs app secret. Prefer managed identity (az webapp identity assign) over storing MicrosoftAppPassword in app settings. Managed identities rotate automatically and never expire.

  • Container Apps require an environment. You must create a Container Apps environment (az containerapp env create) before creating a container app. The environment defines the Log Analytics workspace and networking.

instructions

This expert is a reference catalog of all Azure CLI commands relevant to bot and agent development. Use it when a developer asks "what az commands do I need for X?" or needs to look up the CLI surface for a specific Azure service. For step-by-step deployment instructions, defer to azure-bot-deploy-ts.md.

Pair with: azure-bot-deploy-ts.md (step-by-step deployment), ../security/secrets-ts.md (secrets best practices), ../bridge/infra-compute-ts.md (compute comparisons).

research

Deep Research prompt:

"Catalog all Azure CLI (az) command groups a developer would need for creating, reading, updating, and deleting resources in a bot/agent project on Azure. Include: bot service (az bot), bot channels, bot auth settings, AI Foundry agents (az cognitiveservices agent), Azure OpenAI (az cognitiveservices account), app registration (az ad app), managed identity (az identity), role assignments, hosting (webapp, functionapp, containerapp), resource groups, subscriptions, Key Vault, storage accounts, Cosmos DB, and monitoring. For each group, list the key CRUD commands and their purpose."

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