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/bridge/workflows-automation-ts.md

workflows-automation-ts

purpose

Bridges Slack Workflow Builder and Teams Power Automate / bot-driven orchestration for cross-platform bots targeting Slack, Teams, or both.

rules

Slack Workflow Builder → Power Automate flows (manual rebuild required). There is no automated migration tool. Slack workflows are drag-and-drop automations with triggers and steps. Power Automate flows serve the same purpose but with a completely different builder, trigger system, and step library. Each workflow must be manually recreated. learn.microsoft.com -- Power Automate
Slack workflow triggers → Power Automate triggers. Slack triggers include: webhook, shortcut, new channel message, emoji reaction, user joins channel. Power Automate equivalents: HTTP request (webhook), Teams message trigger, approval trigger, Recurrence (scheduled), and 400+ connectors. Map each trigger individually. learn.microsoft.com -- Triggers
Slack custom steps (workflow_step_execute) → Power Automate custom connectors. Slack bots can register custom workflow steps that appear in the Workflow Builder. In Power Automate, the equivalent is a custom connector wrapping your bot's REST API. The connector defines actions, inputs, and outputs that appear in the flow designer. learn.microsoft.com -- Custom connectors
Slack approval workflows → Power Automate Approvals connector (built-in). Slack workflows that collect approvals via emoji reactions or form submissions map to Power Automate's native Approvals connector. It provides: approval request creation, approval/rejection actions, parallel/sequential approvals, and approval history. No custom code needed. learn.microsoft.com -- Approvals
Teams "Workflows" app provides simple in-Teams automations. For basic workflows (post to channel on schedule, notify on form submission), the Workflows app in Teams provides templates without leaving Teams. It's powered by Power Automate under the hood but has a simplified UI. learn.microsoft.com -- Workflows app
Bot-driven workflow alternative: state machine + Adaptive Card buttons. For workflows that don't fit Power Automate's model (complex branching, dynamic participants, long-running multi-step processes), implement a state machine in the bot. Each step sends an Adaptive Card with action buttons; button clicks advance the state. Store workflow state in Cosmos DB or similar. github.com/microsoft/teams.ts
Slack workflow_step event lifecycle → custom connector action lifecycle. Slack's workflow step has edit (configure step), save (persist config), execute (run step). Power Automate custom connectors define: action schema (inputs/outputs in OpenAPI), and the runtime HTTP call. There is no separate "edit" flow — the connector schema defines the UI. learn.microsoft.com -- Connector actions
Slack workflow variables → Power Automate dynamic content. Slack workflows pass data between steps via variables set in earlier steps. Power Automate uses "dynamic content" — outputs from previous steps that can be referenced in later steps. The data flow model is similar but the syntax is completely different. learn.microsoft.com -- Dynamic content
Power Automate flows can call Bot Framework via HTTP. To integrate your Teams bot into a Power Automate flow, expose REST endpoints on your bot's server and call them from Power Automate's HTTP action. The bot can then send proactive messages based on flow triggers. learn.microsoft.com -- HTTP connector
Slack Workflow Builder is free; Power Automate has licensing tiers. Slack Workflow Builder is included in all plans. Power Automate has a free tier (limited runs) and premium tiers. Custom connectors require a premium license. Factor licensing into migration planning. learn.microsoft.com -- Power Automate licensing
Reverse direction (Teams → Slack): For Teams → Slack, Power Automate flows can be mapped to Slack Workflow Builder steps or custom workflow_step_execute handlers. Power Automate Approvals map to Slack approval workflows using emoji reactions or interactive message buttons. Power Automate custom connectors map to Slack custom workflow steps registered via workflow_step events. Power Automate Recurrence triggers map to Slack Workflow Builder scheduled triggers.

patterns

Approval workflow → Power Automate Approvals

Slack Workflow Builder (before):

The Slack workflow is configured in the GUI:

Trigger: User submits a form (custom step)
Step 1: Send form data to #approvals channel
Step 2: Wait for :white_check_mark: reaction from approver
Step 3: Post result to #completed channel

Bot code for custom approval step:

import { App } from "@slack/bolt";

const app = new App({
  token: process.env.SLACK_BOT_TOKEN!,
  signingSecret: process.env.SLACK_SIGNING_SECRET!,
});

// Custom workflow step execution
app.event("workflow_step_execute", async ({ event, client }) => {
  const { workflow_step } = event;
  const inputs = workflow_step.inputs;

  // Post approval request
  const msg = await client.chat.postMessage({
    channel: "#approvals",
    text: `Approval needed: ${inputs.request_text.value}`,
    blocks: [
      {
        type: "section",
        text: { type: "mrkdwn", text: `*Approval Request*\n${inputs.request_text.value}` },
      },
      { type: "section", text: { type: "mrkdwn", text: "React with :white_check_mark: to approve or :x: to reject." } },
    ],
  });

  // Watch for reaction (simplified — real implementation uses reaction_added event)
});

Teams (after) — Power Automate flow (described as JSON definition):

{
  "definition": {
    "triggers": {
      "manual": {
        "type": "Request",
        "kind": "Button",
        "inputs": {
          "schema": {
            "type": "object",
            "properties": {
              "requestText": { "type": "string", "title": "Request details" },
              "requesterEmail": { "type": "string", "title": "Requester email" }
            }
          }
        }
      }
    },
    "actions": {
      "Start_approval": {
        "type": "OpenApiConnection",
        "inputs": {
          "host": { "connectionName": "shared_approvals" },
          "operationId": "StartAndWaitForAnApproval",
          "parameters": {
            "approvalType": "Basic",
            "ApprovalCreationInput/title": "Approval: @{triggerBody()?['requestText']}",
            "ApprovalCreationInput/assignedTo": "[email protected]",
            "ApprovalCreationInput/details": "@{triggerBody()?['requestText']}"
          }
        }
      },
      "Post_result_to_Teams": {
        "type": "OpenApiConnection",
        "inputs": {
          "host": { "connectionName": "shared_teams" },
          "operationId": "PostMessageToConversation",
          "parameters": {
            "poster": "Flow bot",
            "location": "Channel",
            "body/recipient": "completed-channel-id",
            "body/messageBody": "Request @{outputs('Start_approval')?['body/title']} was @{outputs('Start_approval')?['body/outcome']}"
          }
        },
        "runAfter": { "Start_approval": ["Succeeded"] }
      }
    }
  }
}

Bot-driven alternative (for complex approval logic):

import { App } from "@microsoft/teams.apps";
import { ConsoleLogger } from "@microsoft/teams.common";

const app = new App({
  logger: new ConsoleLogger("my-bot", { level: "info" }),
});

// Approval state machine
interface ApprovalRequest {
  id: string;
  text: string;
  requester: string;
  status: "pending" | "approved" | "rejected";
  activityId?: string;
}

const approvals = new Map<string, ApprovalRequest>();

// Create approval request
app.message(/^\/?approve (.+)$/i, async ({ send, activity }) => {
  const text = activity.text?.replace(/^\/?approve\s+/i, "") ?? "";
  const id = `apr_${Date.now()}`;
  const approval: ApprovalRequest = {
    id,
    text,
    requester: activity.from?.name ?? "Unknown",
    status: "pending",
  };
  approvals.set(id, approval);

  const response = await send({
    attachments: [{
      contentType: "application/vnd.microsoft.card.adaptive",
      content: {
        type: "AdaptiveCard",
        version: "1.5",
        body: [
          { type: "TextBlock", text: "Approval Request", weight: "Bolder", size: "Medium" },
          { type: "TextBlock", text: `**From:** ${approval.requester}`, wrap: true },
          { type: "TextBlock", text: approval.text, wrap: true },
        ],
        actions: [
          { type: "Action.Execute", title: "Approve", verb: "approveAction", data: { approvalId: id } },
          { type: "Action.Execute", title: "Reject", verb: "rejectAction", data: { approvalId: id } },
        ],
      },
    }],
  });
});

// Handle approval/rejection buttons
app.on("card.action" as any, async ({ activity }) => {
  const data = activity.value?.action?.data ?? activity.value;
  const approval = approvals.get(data?.approvalId);

  if (!approval) return { status: 200, body: {} };

  const isApprove = data?.verb === "approveAction";
  approval.status = isApprove ? "approved" : "rejected";
  const reviewer = activity.from?.name ?? "Someone";

  // Return updated card (replaces original)
  return {
    status: 200,
    body: {
      type: "AdaptiveCard",
      version: "1.5",
      body: [
        { type: "TextBlock", text: "Approval Request", weight: "Bolder", size: "Medium" },
        { type: "TextBlock", text: approval.text, wrap: true },
        {
          type: "TextBlock",
          text: `**${approval.status.toUpperCase()}** by ${reviewer}`,
          color: isApprove ? "Good" : "Attention",
          weight: "Bolder",
        },
      ],
      // No actions — card is now read-only
    },
  };
});

app.start(3978);

Migration approach comparison

Slack Workflow Feature	Power Automate	Bot-Driven	Teams Workflows App
Visual builder	Yes (full designer)	No (code)	Yes (simplified)
Custom steps	Custom connectors	Handler code	No
Approval flows	Built-in Approvals	Card buttons + state	No
Scheduled triggers	Recurrence trigger	Timer + proactive	Yes (basic)
Complex branching	Yes (conditions, loops)	State machine	No
License cost	Free tier + Premium	Bot hosting cost	Free
Developer skill needed	Low-code	TypeScript	None

pitfalls

No automated migration: Every Slack workflow must be manually recreated in Power Automate or bot code. There is no import/export compatibility. Plan for significant manual effort on large workflow portfolios.
Reaction-based approvals break completely: Slack workflows commonly use emoji reactions as approval signals. Teams has no equivalent pattern in Power Automate. Use the built-in Approvals connector or Action.Execute card buttons.
Custom connector licensing: Power Automate custom connectors (needed to replace Slack custom workflow steps) require a Premium license. The free tier does not support custom connectors.
Slack workflow variables vs Power Automate dynamic content: The data passing model is similar in concept but completely different in syntax. Slack uses {{variable_name}}; Power Automate uses @{outputs('step_name')?['property']}. This is a manual translation.
Bot-driven workflows require state persistence: Unlike Power Automate which manages state internally, bot-driven approval workflows need external state storage (Cosmos DB, SQL). Without it, workflow state is lost on bot restart.
Power Automate flow limits: Free tier is limited to 750 runs/month. Standard is 10,000/month. High-volume workflows (processing hundreds of requests daily) may require premium plans.

references

instructions

Use this expert when adding cross-platform support in either direction for workflow automation. It covers: Slack Workflow Builder bridged to Power Automate flows, custom workflow steps bridged to Power Automate custom connectors, approval workflows bridged to the Approvals connector, the Teams Workflows app for simple automations, bot-driven workflow alternatives using state machines + Adaptive Cards, and reverse mapping from Power Automate flows back to Slack Workflow Builder steps and custom workflow_step_execute handlers. Pair with ../teams/ui.adaptive-cards-ts.md for card construction in bot-driven workflows, ../teams/runtime.proactive-messaging-ts.md for flow-triggered bot messages, and slack-interactive-responses-to-teams-ts.md for card replacement patterns in approval flows.

research

Deep Research prompt:

"Write a micro expert for bridging Slack Workflow Builder and Microsoft Teams Power Automate / bot-driven orchestration in either direction. Cover: Power Automate as the Teams-side replacement, custom connector creation for Slack custom workflow steps, the built-in Approvals connector for approval flows, the Teams Workflows app for simple automations, bot-driven state machine alternative with Adaptive Card buttons, workflow trigger mapping, variable/dynamic content translation, licensing considerations, and reverse mapping from Power Automate flows back to Slack Workflow Builder steps. Include code examples for bot-driven approvals and a comparison table."

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