Add a Teams connector to Power Apps for messaging and channel integration.
The material indicates an open-source, prompt-only skill with no required secrets or declared remote endpoints, so the overall risk is low. Caution is still warranted because it instructs users to add a Teams connector and operate in external Power Apps/Teams environments, which can affect business data and connector permissions.
The material explicitly states there are no required secrets or environment variables; the skill itself does not directly request tokens. It does rely on existing Teams/Power Apps connections managed by external platforms, but there is no clear sign of credential export or misuse in the documentation.
The README points to the Power Apps Connections page and describes sending Teams messages or posting to channels, meaning business content may be transmitted to Microsoft services as part of the stated functionality. No other third-party or unknown endpoints are declared, so this is normal egress for this type of integration.
The README includes commands such as `npx power-apps add-data-source` and `npm run build`, indicating normal local development command execution and build steps. There is no evidence of unusually broad system privileges or suspicious commands unrelated to the stated purpose.
The material references reading `power.config.json`, inspecting `src/generated/services/TeamsService.ts`, and updating `memory-bank.md`, which implies access to project configuration and generated source files. This scope is consistent with a code-app integration workflow, with no indication of unrelated sensitive directories or excessive access.
The source is Microsoft's open-source `power-platform-skills` repository on GitHub, making the content auditable; the system also marks it as open-source and prompt-only, which materially lowers supply-chain risk. Still, the repo has 0 stars and unclear license/maintenance status, so users should verify current upkeep before adoption.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "add-teams" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/code-apps/skills/add-teams/SKILL.md 2. Save it as ~/.claude/skills/add-teams/SKILL.md 3. Reload skills and tell me it's ready
Add the Microsoft Teams connector to my Power Apps code app so it can send Teams messages to specific users, and provide the basic setup steps.
Provides the Teams connector setup details and explains how to send messages to users from the app.
Integrate the Teams connector into my Power Apps code app so it can automatically post notifications to a Teams channel when task status changes.
Returns the Teams integration setup for channel posting and explains how to trigger automatic notifications.
Add the Microsoft Teams connector to this Power Apps code app for Teams chat workflows, such as starting chats from the app or syncing conversation data.
Provides the connector integration result for Teams chat scenarios and describes the available actions.
📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns.
Check for memory-bank.md per shared-instructions.md.
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.
npx power-apps add-data-source -a teams -c <connection-id>
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).
npm run build
Fix TypeScript errors before proceeding. Do NOT deploy yet.
Update memory-bank.md with: connector added, configured operations, build status.
Review and fix Power Pages security headers, CSP, CORS, cookies, and embedding settings.
Run an end-to-end Power Pages security review with a consolidated HTML report.
Test deployed Power Pages sites with browsing, crawling, and API verification.
Add a data source or connector to a Power Apps code app.
Add Azure DevOps to Power Apps for work items, bugs, pipelines, and API calls.
Set up Power Platform Pipelines for automated Power Pages deployments.
Add a Copilot Studio connector to Power Apps code apps for agent integration.
Add any Power Platform connector to a Power Apps code app.
Interact with Microsoft Teams chats and channels in restricted enterprise environments.
Add the Office 365 Outlook connector for email and calendar features.
Connect SharePoint to Power Apps for lists, documents, and site integration.
Add the Excel Online connector to read and write workbook data.