Add Microsoft Teams Connector

VerifiedSafe

Integrates Microsoft Teams with Power Apps code apps to send messages, post to channels, and manage Teams conversations.

Sby Skills Guide Bot
DevelopmentIntermediate
3/9/2026
Claude Code
#microsoft-teams#power-apps#connectors#typescript#pac-cli

Recommended for

Automated summary

Adds the Microsoft Teams connector to a Power Apps code app and then configures message-sending operations and verifies the build.

Strengths

  • Five-step workflow from Memory Bank check to final build
  • Uses `/list-connections` and `pac code add-data-source` with the real connection ID
  • Provides a concrete TypeScript example of `PostMessageToConversation` (recipient UPN, HTML body)
  • Reminds you not to deploy yet and to record the outcome in `memory-bank.md`

Limitations

  • Assumes an existing Power Apps code app with `power.config.json` already set up
  • Covers Teams only, and manual connection creation happens outside the tool when none exists
  • Generated service files can be very large, so it recommends Grep instead of full reads
When to use it

When you need to send Teams messages or post to channels from a Power Apps code app.

When not to use it

When you are integrating Teams into a non-Power Apps project or cannot use the pac CLI.

Security analysis

Safe
Quality score78/100

The skill only instructs running the official Power Platform CLI (`pac code add-data-source`) and `npm run build`, plus reading/editing project files. Although Bash is in the allowed-tools list, every command shown is a fixed, narrowly scoped invocation tied to adding a Teams data source and building the app; there is no piping to shells, no credential/token exfiltration, no destructive filesystem operations, and no obfuscated payloads. The only sensitive item handled is a connection ID, which is used locally as a CLI argument rather than being transmitted anywhere unexpected.

No concerns found

How this analysis is made

Examples

Add Teams messaging
Add the Microsoft Teams connector to my Power Apps code app so I can send chat messages to a user.
Post to a channel
Configure my code app to post a message to a Teams channel using the Flow bot and confirm it builds.
Wire up connections
List my Power Apps connections, find the Teams one, add it as a data source, and update the memory bank.

name: add-teams description: Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat. user-invocable: true allowed-tools: Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill model: sonnet

πŸ“‹ Shared Instructions: shared-instructions.md - Cross-cutting concerns.

Add Teams

Workflow

  1. Check Memory Bank β†’ 2. Add Connector β†’ 3. Configure β†’ 4. Build β†’ 5. Update Memory Bank

Step 1: Check Memory Bank

Check for memory-bank.md per shared-instructions.md.

Step 2: Add Connector

First, find the connection ID (see connector-reference.md):

Run the /list-connections skill. Find the Teams connection in the output. If none exists, direct the user to create one using the environment-specific Connections URL β€” construct it from the active environment ID in context (from power.config.json or a prior step): https://make.powerapps.com/environments/<environment-id>/connections β†’ + New connection β†’ search for the connector β†’ Create.

pwsh -NoProfile -Command "pac code add-data-source -a teams -c <connection-id>"

Step 3: Configure

Ask the user what Teams operations they need (send message, post to channel, etc.).

PostMessageToConversation -- sends a chat message via Flow bot:

await TeamsService.PostMessageToConversation({
  "Post as": "Flow bot",
  "Post in": "Chat with Flow bot",
  "Post message request": {
    recipient: "<recipient-upn-or-id>", // UPN or Entra object ID
    messageBody: "<p>HTML message</p>", // HTML format
    isAlert: false,
    feedbackLoopEnabled: false
  }
});

Use Grep to find specific methods in src/generated/services/TeamsService.ts (generated files can be very large -- see connector-reference.md).

Step 4: Build

npm run build

Fix TypeScript errors before proceeding. Do NOT deploy yet.

Step 5: Update Memory Bank

Update memory-bank.md with: connector added, configured operations, build status.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/add-microsoft-teams-connector-mmio716y/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/add-microsoft-teams-connector-mmio716y' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/add-microsoft-teams-connector-mmio716y/download' --output '.skill-downloads/add-microsoft-teams-connector-mmio716y/SKILL.md.part' && mv '.skill-downloads/add-microsoft-teams-connector-mmio716y/SKILL.md.part' '.skill-downloads/add-microsoft-teams-connector-mmio716y/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/add-microsoft-teams-connector-mmio716y/SKILL.md' && test -s '.skill-downloads/add-microsoft-teams-connector-mmio716y/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/add-teams' && cp -R '.skill-downloads/add-microsoft-teams-connector-mmio716y' '.claude/skills/add-teams'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js β‰₯ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/add-microsoft-teams-connector-mmio716y'

openskills read 'add-microsoft-teams-connector-mmio716y'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/add-microsoft-teams-connector-mmio716y/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills