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

docs/workflows.md

Workflow Scenarios

Message-native workflow patterns for Teams bots. These scenarios demonstrate how collaborative business workflows can be initiated, executed, persisted, queried, and displayed entirely within the message surface — no external tools or navigation required.

Each scenario follows the same five-element lifecycle:

Element	What It Does	Teams API
Trigger	How the workflow starts	Bot commands, message extensions, `node-cron`, Graph change notifications
State	Where records live	SharePoint Lists via Graph API (or Dataverse for enterprise)
Logic	How decisions execute	Bot state machine, `Action.Execute` handlers, escalation timers
Intelligence	How AI is layered over state	Azure OpenAI function calling for NL queries over list data
Visibility	How records stay in-channel	Adaptive Cards with `Action.Execute` → in-place refresh

All scenarios are implementable today with a standard Teams bot. No new platform features required.

Example implementation: examples/message-native-workflow/ — Daily Standup with all five pillars.

Experts: The teams/workflow.* and bridge/workflow.composable-platform-ts.md experts provide implementation guidance for each pillar.

Scenario 1: Daily Standup

Audience: SMB teams, engineering teams, any recurring check-in cadence.

User Flow

Bot posts a standup prompt card at 9 AM (scheduled trigger) or on /standup (command trigger)
Each team member fills in yesterday / today / blockers in the card's input fields
On submit, Action.Execute replaces the prompt with a completed record card in-place
Record persisted to SharePoint List with thread link
Manager types "show blockers" or "summarize last week" — AI queries the list and renders results

Five Elements

Element	Implementation
Trigger	`node-cron` scheduled at `STANDUP_CRON` + `/standup` bot command
State	SharePoint List: Respondent, Date, Yesterday, Today, Blockers, HasBlockers, ThreadActivityId
Logic	Card form submission → record creation. Edit/save state machine via `Action.Execute`
Intelligence	`queryStandups(date?, respondent?)`, `queryBlockers(currentOnly?)`, `summarizeStandups(date)`
Visibility	Prompt card → record card (in-place). Summary card. Blockers card with per-person breakdown

Key Cards

Standup prompt — Input.Text fields for yesterday/today/blockers + Submit button
Record card — FactSet showing the response + Edit button
Summary card — response count, blocker count, respondent list
Blockers card — ColumnSet list of all current blockers by person

Why It Validates the Vision

Exercises structured input (form), durable state (list), in-place updates (Action.Execute), and NL retrieval (AI function calling). This is FHL Option A from the source document.

Scenario 2: Time-Off Requests (PTO)

Audience: SMB, any team with leave management.

User Flow

Employee types /pto 2024-03-15 to 2024-03-22 or uses the "New PTO Request" compose extension
Bot creates a PTO record card in the thread with request details + Approve/Reject buttons
Manager sees the card with refresh.userIds showing action buttons only to them
Manager clicks Approve — card refreshes in-place to show "Approved by [Manager]" (read-only)
Employee receives a proactive notification in the thread
Anyone in the channel can type "show PTO for March" — AI queries and renders results

Five Elements

Element	Implementation
Trigger	Bot command (`/pto START to END`), message extension action (form with date pickers)
State	SharePoint List: Requester, StartDate, EndDate, HoursRequested, Status, ApprovedBy, ThreadActivityId
Logic	Single-approver routing. Manager lookup via `GET /users/{id}/manager`. Escalation timer (48h)
Intelligence	`queryPtoRequests(status?, requester?, month?)` — "Who has PTO next week?", "Show pending requests"
Visibility	Request card (pending, with Approve/Reject) → Approved card (read-only). PTO list card for queries

Approval Routing

Pattern	Behavior
Single	One approver (direct manager), one decision
Sequential	Manager → Director. Director only sees the card after manager approves
Parallel-all	HR + Manager must both approve

Role-Specific Card Views

The refresh property on the Adaptive Card targets refresh.userIds = the current approver's AAD ID. The approver sees Approve/Reject buttons. Everyone else sees a read-only status card. When the approver acts, the card refreshes for all viewers.

Scenario 3: Equipment / Asset Reservation

Audience: SMB operations, facilities, shared resource management.

User Flow

Employee types /book Projector Room-A tomorrow 2pm-4pm
Bot checks for conflicts by querying the list for overlapping reservations
If available, bot creates the booking and posts a confirmation card
If conflict detected, bot posts a card showing the conflict and suggesting alternatives
Late-return alert: if the booking end time passes without a return confirmation, bot sends a reminder
Manager types "show all bookings this week" — AI renders a calendar-style summary

Five Elements

Element	Implementation
Trigger	Bot command (`/book ITEM LOCATION DATE TIME`), message extension search for availability lookup
State	SharePoint List: Item, Location, BookedBy, StartTime, EndTime, Status (Active/Returned/Overdue), ThreadActivityId
Logic	Conflict detection via `$filter` on overlapping date ranges. Return confirmation via `Action.Execute`. Overdue timer → proactive reminder
Intelligence	`queryEquipmentBookings(item?, status?, dateRange?)` — "Is the projector available Friday?", "Show overdue items"
Visibility	Booking confirmation card. Conflict card with alternatives. Overdue alert card. Weekly summary card

Conflict Detection Query

fields/Item eq 'Projector' and fields/Location eq 'Room-A'
  and fields/StartTime lt '2024-03-16T16:00:00Z'
  and fields/EndTime gt '2024-03-16T14:00:00Z'
  and fields/Status eq 'Active'

If results > 0, there's a conflict. The bot renders the conflicting bookings and suggests the next available slot.

Scenario 4: Account Health Monitoring (CRM)

Audience: Sales teams, account managers, customer success.

User Flow

Weekly scheduled prompt posts to the sales channel: "Time for account health check-ins"
Each account owner fills in: Account name, health status (Green/Yellow/Red), notes, next meeting date
Responses aggregate into a durable account health list
Stale accounts flagged: if no update in 30 days, bot sends a dormant account alert
Before a meeting, manager types "summarize Acme Corp" — AI pulls the last 4 check-ins and renders a trend card

Five Elements

Element	Implementation
Trigger	Weekly cron schedule. Dormant-account check (daily timer queries for last-update > 30 days)
State	SharePoint List: AccountName, Owner, HealthStatus (Green/Yellow/Red), Notes, NextMeeting, LastUpdated
Logic	Staleness detection: daily timer queries `fields/LastUpdated lt '{30-days-ago}'`. Proactive alert to owner
Intelligence	`queryAccountHealth(account?, status?, owner?)` — "Show all red accounts", "Summarize Acme Corp history"
Visibility	Check-in prompt card. Account status card (color-coded). Dormant account alert. Trend summary card

Trend Analysis

The AI function returns the last N check-ins for an account. The LLM summarizes:

"Acme Corp: 4 check-ins over the last month. Trend: Yellow → Yellow → Red → Red. Key issue: delayed contract renewal (first flagged March 1). Next meeting: March 15."

This is the "intelligence layered over structured state" pattern — the primary differentiation opportunity called out in the source document.

Scenario 5: Frontline Break Management

Audience: Frontline workers, call centers (e.g., T-Mobile scenario from source document).

User Flow

Agent changes presence to "Away" (auto-detected via Graph presence subscription)
Bot removes agent from call queue and starts break timer
At 15 minutes, bot sends a reminder card to the agent and their manager
At 20 minutes, bot escalates — posts an alert card in the manager channel
Agent changes presence to "Available" — bot re-adds to queue, records break duration
Manager types "who is on break?" or "average break duration today" — AI queries and responds

Five Elements

Element	Implementation
Trigger	Graph change notification subscription on `/communications/presences/{userId}`
State	SharePoint List: EmployeeName, BreakStart, BreakEnd, DurationMinutes, Status (Active/Ended/Escalated)
Logic	Timer-based escalation (15 min reminder, 20 min escalate). Call queue add/remove via Teams admin APIs. Break record created on "Away", updated on "Available"
Intelligence	`queryBreakStatus(currentOnly?)` — "Who is on break right now?", "Average break duration this week"
Visibility	Break started card (in manager channel). Reminder card (to agent). Escalation alert card. Break summary card

Why This Is Teams-Native

This scenario depends on three capabilities Slack cannot replicate:

Capability	Teams	Slack
Presence change subscriptions	Graph `/communications/presences`	Not available
Shift schedule integration	Shifts API	Not available
Call queue management	Teams admin APIs + Graph	Not available

Technical Requirements

Graph subscription for presence requires Presence.Read.All application permission and encrypted rich notifications (public/private key pair for notification decryption)
Presence subscriptions expire in 60 minutes — aggressive renewal required (55-minute interval)
Webhook must respond in 3 seconds — process notifications asynchronously
In-memory timers don't survive restarts — use Azure Durable Functions or a Redis-backed job queue for production

Scenario 6: Incident Response

Audience: IT operations, DevOps, on-call teams.

User Flow

On-call engineer types /incident P1 Production database connection pool exhausted
Bot creates an incident record, posts a structured incident card, and creates a dedicated incident thread
Bot proactively notifies the on-call rotation (looked up from a Shifts schedule or list)
Team members post updates in the thread — bot captures tagged updates (/update Database restarted, monitoring)
Engineer types /resolve — bot closes the incident, calculates MTTR, and posts a resolution summary
Post-incident: manager types "show P1 incidents this month" — AI generates a summary with MTTR trends

Five Elements

Element	Implementation
Trigger	`/incident PRIORITY DESCRIPTION` bot command
State	SharePoint List: IncidentId, Priority (P1-P4), Description, Status (Open/Investigating/Resolved), AssignedTo, CreatedAt, ResolvedAt, MTTR, Updates[]
Logic	Auto-assign from on-call rotation. Status transitions: Open → Investigating → Resolved. MTTR calculation on resolve. Thread-based update capture
Intelligence	`queryIncidents(priority?, status?, dateRange?)` — "Show open incidents", "MTTR trend for P1s this quarter"
Visibility	Incident card (color-coded by priority). Update timeline in thread. Resolution summary card with MTTR

Composable Platform Pattern

All six scenarios follow the same lifecycle. The composable platform approach (see bridge/workflow.composable-platform-ts.md) defines workflows as configuration:

interface WorkflowDefinition {
  id: string;                   // "pto", "standup", "equipment"
  commandPrefix: string;        // "/pto", "/standup", "/book"
  columns: ColumnDefinition[];  // SharePoint List schema
  statusField: string;          // Which column tracks lifecycle
  routing?: RoutingConfig;      // Approval chain config
  cards: CardTemplates;         // Active, completed, list, form
  queryDescription: string;     // AI function calling description
  filterableColumns: string[];  // Columns exposed to NL queries
}

A single workflow engine registers handlers from definitions. New workflows require a new WorkflowDefinition object, not new handler code. Template workflows (standup, PTO, equipment) serve as reference implementations.

Scenario Comparison

Scenario	Trigger Types	Approval	State-Driven	NL Queries	Competitive Edge
Daily Standup	Scheduled, command	No	No	Blockers, summaries	Structured check-ins as durable records
PTO Requests	Command, extension	Yes (single/chain)	No	Status, date range, person	Approval routing + NL retrieval
Equipment Booking	Command, search	No	No	Availability, overdue	Conflict detection + alternatives
Account Health	Scheduled	No	Timer (staleness)	Trends, status, owner	Trend analysis over time
Break Management	Presence change	No	Yes (presence)	Current status, averages	Teams-only: presence + Shifts + call queues
Incident Response	Command	No	No	Priority, MTTR, status	Thread-based update capture + MTTR

Platform Comparison: Teams vs Slack

Capability	Slack	Teams	Gap
In-channel workflow creation	Workflow Builder GUI	Power Automate (external)	Teams gap: no in-channel builder
Structured input forms	`OpenForm` built-in function	Adaptive Card forms (bot) or task modules	Parity
State persistence	Datastores (50K limit, Slack-hosted)	SharePoint Lists (30M limit, tenant-owned)	Teams advantage
Card interactivity	Block Kit (new message on action)	Action.Execute (in-place refresh)	Teams advantage
NL querying over state	Not built-in	AI function calling + structured data	Teams advantage
Presence/Shifts triggers	Not available	Graph subscriptions	Teams advantage
Call queue integration	Not available	Teams admin APIs	Teams advantage
No-code authoring	Workflow Builder	Power Automate	Slack advantage (simpler UX)
Hosting model	Slack-hosted (Deno)	Self-hosted or Azure	Trade-off

The core thesis: if Teams unifies its existing primitives at the message layer (which a bot can do today), it moves beyond parity — especially for operational and frontline workflows where Slack lacks system-level integration.

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

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by Microsoft

Microsoft 365 Agents Toolkit Skill

AI Behavior Guidelines

ATK CLI Setup

CLI Global Options

Sub-Skills

Shared References

Workflow Chains

ATK Project Context Resolution

Step 1: Detect ATK Project

Step 2: Resolve Common Configuration

Step 3: Collect Missing Values

Files

docs/workflows.md

Workflow Scenarios

Scenario 1: Daily Standup

User Flow

Five Elements

Key Cards

Why It Validates the Vision

Scenario 2: Time-Off Requests (PTO)

User Flow

Five Elements

Approval Routing

Role-Specific Card Views

Scenario 3: Equipment / Asset Reservation

User Flow

Five Elements

Conflict Detection Query

Scenario 4: Account Health Monitoring (CRM)

User Flow

Five Elements

Trend Analysis

Scenario 5: Frontline Break Management

User Flow

Five Elements

Why This Is Teams-Native

Technical Requirements

Scenario 6: Incident Response

User Flow

Five Elements

Composable Platform Pattern

Scenario Comparison

Platform Comparison: Teams vs Slack

Requirements and compatibility

Security

Attribution and licence

Related skills

Implement Spec

MCP Builder

Schema

Postgresql Table Design

SQL Optimization Patterns

API Scaffolding Fastapi Pro

Download ZIP