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

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/teams-app-developer/download

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

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, 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
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+)
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
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 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

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

azure-bot-deploy-ts

purpose

Step-by-step deployment of a Slack bot, Teams bot, or dual bot to Azure. Covers CLI setup, App Registration, Bot Service registration, compute provisioning (App Service / Functions / Container Apps), environment configuration, and verification.

rules

Install prerequisites before anything else. You need: Node.js 20 LTS, Azure CLI (az), and optionally the Agents Toolkit CLI (npm install -g @microsoft/m365agentstoolkit-cli). Verify with az --version and node --version. learn.microsoft.com/cli/azure/install-azure-cli
Authenticate and set the target subscription. Run az login to open browser auth, then az account set --subscription <subscription-id>. All subsequent commands use this subscription. learn.microsoft.com/cli/azure/authenticate-azure-cli
Create a resource group to contain all bot resources. az group create --name <rg-name> --location <region>. Use a region close to your users (e.g., eastus, westeurope). All subsequent resources go in this group. learn.microsoft.com/azure/azure-resource-manager/management/manage-resource-groups-cli
Register an Entra ID App Registration. This is the bot's identity — required for both Teams and Slack bots on Azure. az ad app create --display-name <bot-name> returns an appId (client ID). Then create a secret: az ad app credential reset --id <appId>. Save the password — it's the CLIENT_SECRET and is only shown once. learn.microsoft.com/entra/identity-platform/quickstart-register-app
Create an Azure Bot Service resource (Teams bots). az bot create --resource-group <rg> --name <bot-name> --app-type SingleTenant --appid <appId> --tenant-id <tenantId>. Set the messaging endpoint to https://<app-name>.azurewebsites.net/api/messages. learn.microsoft.com/azure/bot-service/bot-service-quickstart-registration
Connect the Bot Service to Teams. az bot msteams create --resource-group <rg> --name <bot-name>. Without this, Teams cannot reach your bot even if it's deployed and running. learn.microsoft.com/azure/bot-service/channel-connect-teams
For Slack bots on Azure, skip Bot Service. Deploy as a plain web app with the Bolt HTTP receiver. Configure the Slack app's Event Subscriptions Request URL and Interactivity URL to https://<app-name>.azurewebsites.net/slack/events.
Choose your compute target. App Service (recommended — always-on, simple), Azure Functions Premium (serverless with warm instances), or Container Apps (containerized workloads with scale-to-zero). Avoid Functions Consumption plan for bots — cold starts exceed Slack's 3-second ack deadline and Teams' response expectations. learn.microsoft.com/azure/app-service/overview
Provision the compute resource with Node.js 20 LTS. For App Service: az webapp create --resource-group <rg> --plan <plan-name> --name <app-name> --runtime "NODE:20-lts". For Functions: az functionapp create ... --runtime node --runtime-version 20. learn.microsoft.com/azure/app-service/quickstart-nodejs
Configure App Settings with all required environment variables. az webapp config appsettings set --resource-group <rg> --name <app-name> --settings MicrosoftAppId=<appId> MicrosoftAppPassword=<secret> MicrosoftAppTenantId=<tenantId> PORT=3978. For Slack, add SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET, and SLACK_APP_TOKEN. learn.microsoft.com/azure/app-service/configure-common
Build and deploy. Run npm run build locally, then zip deploy: az webapp deploy --resource-group <rg> --name <app-name> --src-path <zip-path> --type zip. For Functions: func azure functionapp publish <app-name>. learn.microsoft.com/azure/app-service/deploy-zip
Enable Always On for App Service. az webapp config set --resource-group <rg> --name <app-name> --always-on true. Without this, the app goes idle after 20 minutes and the next request cold-starts. For Functions Premium, configure Always Ready instances instead. learn.microsoft.com/azure/app-service/configure-common
Verify the deployment. Check the health endpoint: curl https://<app-name>.azurewebsites.net/api/health. Then send a test message in Teams or Slack. Check App Service logs: az webapp log tail --resource-group <rg> --name <app-name>. learn.microsoft.com/azure/app-service/troubleshoot-diagnostic-logs
Agents Toolkit fast path (Teams bots). Instead of steps 3-12, run atk provision (creates App Registration, Bot Service, App Service, and all config) then atk deploy (builds and deploys). Two commands replace the entire manual process. Requires an m365agents.yml in your project. learn.microsoft.com/microsoftteams/platform/toolkit/toolkit-cli

interview

Q1 — Compute Target

question: "Which Azure compute target do you want to deploy to?"
header: "Compute"
options:
  - label: "App Service (Recommended)"
    description: "Always-on web app. Simplest deployment, good for most bots. ~$13/month for B1 plan."
  - label: "Azure Functions Premium"
    description: "Serverless with warm instances. Auto-scales, pay-per-execution + base cost. Good for variable traffic."
  - label: "Container Apps"
    description: "Containerized deployment with Dapr support. Scale-to-zero. Good for microservice architectures."
  - label: "You Decide Everything"
    description: "Use App Service (recommended default) and skip remaining questions."
multiSelect: false

Q2 — Deployment Method

question: "How do you want to deploy?"
header: "Method"
options:
  - label: "Agents Toolkit CLI (Recommended)"
    description: "atk provision + atk deploy — automates App Registration, Bot Service, App Service, and manifest sideloading in two commands."
  - label: "Manual az CLI"
    description: "Full control, step-by-step. Learn exactly what resources are created and how they connect."
  - label: "You Decide Everything"
    description: "Use Agents Toolkit CLI (recommended default) and skip remaining questions."
multiSelect: false

defaults table

Question	Default
Q1	App Service
Q2	Agents Toolkit CLI

patterns

End-to-end manual Azure deployment (Teams bot)

# 1. Prerequisites
az --version          # Verify Azure CLI installed
node --version        # Verify Node.js 20+

# 2. Authenticate
az login
az account set --subscription "My Subscription"

# 3. Create resource group
az group create --name rg-mybot --location eastus

# 4. App Registration (bot identity)
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)

echo "Save these values:"
echo "  APP_ID=$APP_ID"
echo "  APP_SECRET=$APP_SECRET"
echo "  TENANT_ID=$TENANT_ID"

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

# 6. Connect Teams channel
az bot msteams create --resource-group rg-mybot --name mybot-bot

# 7. Create App Service plan + web app
az appservice plan create \
  --resource-group rg-mybot \
  --name mybot-plan \
  --sku B1 \
  --is-linux

az webapp create \
  --resource-group rg-mybot \
  --plan mybot-plan \
  --name mybot-app \
  --runtime "NODE:20-lts"

# 8. Configure environment variables
az webapp config appsettings set \
  --resource-group rg-mybot \
  --name mybot-app \
  --settings \
    MicrosoftAppId=$APP_ID \
    MicrosoftAppPassword=$APP_SECRET \
    MicrosoftAppTenantId=$TENANT_ID \
    PORT=3978

# 9. Enable Always On
az webapp config set --resource-group rg-mybot --name mybot-app --always-on true

# 10. Update Bot Service messaging endpoint
az bot update \
  --resource-group rg-mybot \
  --name mybot-bot \
  --endpoint "https://mybot-app.azurewebsites.net/api/messages"

# 11. Build and deploy
npm run build
cd dist && zip -r ../deploy.zip . && cd ..
az webapp deploy --resource-group rg-mybot --name mybot-app --src-path deploy.zip --type zip

# 12. Verify
curl https://mybot-app.azurewebsites.net/api/health
az webapp log tail --resource-group rg-mybot --name mybot-app

Agents Toolkit fast path (Teams bot)

# 1. Install Agents Toolkit CLI
npm install -g @microsoft/m365agentstoolkit-cli@beta

# 2. Provision all Azure resources (App Registration, Bot Service, App Service)
atk provision --env dev --resource-group <rg> --region <region> -i false

# 3. Build and deploy
atk deploy --env dev -i false

# 4. Sideload to Teams for testing
# Get TEAMS_APP_ID from env/.env.dev, open:
# https://teams.microsoft.com/l/app/$TEAMS_APP_ID?installAppPackage=true&webjoin=true

# That's it — two commands from zero to running bot in Teams.
# m365agents.yml in your project defines the resource topology.

Slack bot on Azure App Service

# 1. Create resource group + App Service (no Bot Service needed)
az group create --name rg-slackbot --location eastus

az appservice plan create \
  --resource-group rg-slackbot \
  --name slackbot-plan \
  --sku B1 \
  --is-linux

az webapp create \
  --resource-group rg-slackbot \
  --plan slackbot-plan \
  --name slackbot-app \
  --runtime "NODE:20-lts"

# 2. Configure Slack credentials
az webapp config appsettings set \
  --resource-group rg-slackbot \
  --name slackbot-app \
  --settings \
    SLACK_BOT_TOKEN=xoxb-your-token \
    SLACK_SIGNING_SECRET=your-signing-secret \
    SLACK_APP_TOKEN=xapp-your-app-token \
    PORT=3000

# 3. Enable Always On + deploy
az webapp config set --resource-group rg-slackbot --name slackbot-app --always-on true
npm run build && cd dist && zip -r ../deploy.zip . && cd ..
az webapp deploy --resource-group rg-slackbot --name slackbot-app --src-path deploy.zip --type zip

# 4. Configure Slack app URLs at api.slack.com:
#    Event Subscriptions Request URL: https://slackbot-app.azurewebsites.net/slack/events
#    Interactivity Request URL:       https://slackbot-app.azurewebsites.net/slack/events
#    Slash Command Request URL:       https://slackbot-app.azurewebsites.net/slack/events

Dual bot on Azure (Slack + Teams on shared Express)

# Follow the Teams bot manual deployment (pattern 1), then add Slack config:
az webapp config appsettings set \
  --resource-group rg-mybot \
  --name mybot-app \
  --settings \
    SLACK_BOT_TOKEN=xoxb-your-token \
    SLACK_SIGNING_SECRET=your-signing-secret \
    SLACK_APP_TOKEN=xapp-your-app-token

# The shared Express server mounts:
#   Teams: POST /api/messages
#   Slack: POST /slack/events
# Both work on the same App Service instance.

# Configure Slack app URLs at api.slack.com:
#   Event Subscriptions: https://mybot-app.azurewebsites.net/slack/events
#   Interactivity:       https://mybot-app.azurewebsites.net/slack/events

pitfalls

Forgetting to set the Bot Service messaging endpoint. After creating the App Service, you must update the Bot Service with az bot update --endpoint. Without this, Teams messages never reach your code. The endpoint format is https://<app-name>.azurewebsites.net/api/messages.
Using Consumption plan for bots. Azure Functions Consumption plan has cold starts of 5-15 seconds. This exceeds Slack's 3-second ack deadline and causes Teams timeout errors. Use App Service (Always On) or Functions Premium (Always Ready) instead.
CLIENT_SECRET expiration. Entra ID app secrets expire by default after 6 months. Set a calendar reminder. Rotate by creating a new secret (az ad app credential reset) and updating the App Setting before the old one expires.
Port mismatch. App Service injects the PORT environment variable (usually 8080). Your bot code must listen on process.env.PORT. If you hardcode port 3978, the app starts but App Service can't route traffic to it.
Deploying without building. az webapp deploy --type zip deploys whatever is in the zip. If you skip npm run build, you're deploying source TypeScript, not compiled JavaScript. The app crashes with syntax errors.
Forgetting Always On. Without --always-on true, App Service idles after 20 minutes. The first request after idle takes 10-30 seconds to cold-start, causing timeout errors in both Slack and Teams.
Missing Teams channel on Bot Service. Running az bot create creates the Bot Service but doesn't connect it to Teams. You must also run az bot msteams create. Without it, Teams shows "This app is not responding."
Slack Request URL verification failure. When you enter the Request URL in the Slack app dashboard, Slack immediately sends a verification challenge. Your app must already be deployed and running. Configure the URL after deployment, not before.

references

instructions

This expert walks through deploying a bot to Azure from scratch — from installing the CLI to verifying a test message. Use it when a developer says "deploy my bot to Azure", "set up Azure hosting", or "get my bot running in production on Azure". Covers Teams bots (with Bot Service + App Registration), Slack bots (plain App Service), and dual bots (shared Express).

Pair with: ../teams/project.scaffold-files-ts.md (project structure before deployment), ../teams/runtime.manifest-ts.md (Teams manifest for sideloading after deployment), ../security/secrets-ts.md (secrets best practices), ../bridge/infra-compute-ts.md (if comparing Azure compute options with AWS equivalents).

research

Deep Research prompt:

"Write a micro expert on deploying a Slack Bolt.js or Microsoft Teams bot to Azure. Cover: Azure CLI installation, az login, resource group creation, Entra ID App Registration (client ID + secret), Azure Bot Service creation and Teams channel connection, App Service provisioning with Node.js 20 LTS, environment variable configuration via App Settings, zip deployment, Always On configuration, Agents Toolkit CLI (atk provision + atk deploy) as a fast path, Slack-on-Azure configuration (Event Subscriptions URL), dual bot deployment on shared Express, and common deployment verification steps. Provide 3-4 canonical bash script examples and 6-8 common pitfalls."

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

2026-11-08

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