Skip to content

microsoft/power-platform-skills / plugins/code-apps/skills/list-connections

list-connections

Verified

Lists Power Platform connections in the current environment. Use when you need a connection ID before adding a connector to a code app (required on Power Apps CLI versions before 1.3.0), to choose between several connections, or to troubleshoot a connection.

📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns (Windows CLI compatibility, memory bank, etc.).

List Connections

Lists all Power Platform connections in the current environment using the Power Apps CLI.

On CLI 1.3.0+ (PA_INLINE_CONNECTIONS=yes), connector skills don't need this first: pa app add data-source finds or creates the connection itself (see connector-reference.md). Use this skill there to choose between several connections or to check what exists. On older CLIs it's the required first step before adding a connector.

Workflow

  1. Fetch Connections → 2. Present Results

Step 1: Fetch Connections

Resolve the CLI first (see cli-binary.md): run as $PA connection list (npx --no-install pa …), never a bare pa. On power-apps-only projects, translate to power-apps list-connections.

pa connection list

To show only one connector's connections, add --search '<connector name or ID>'.

If the CLI reports that you're not signed in, run pa auth login (it opens the browser for sign-in), then retry.

Other failures:

  • Non-zero exit for any reason other than auth: Report the exact output. STOP.
  • No output or empty results: Verify the correct environment ID is set in power.config.json, then retry once.

Step 2: Present Results

Show the connection list to the user. The Connection ID is what goes into -c <connection-id> when adding a data source. If the connector has several connections, let the user choose; don't pick one for them.

If the needed connector has no connection:

  1. On CLI 1.3.0+, the connector's /add-* skill usually handles this: the add creates single sign-on connections itself, and otherwise hands creation to the user (see connector-reference.md).
  2. To create one now, confirm with the user, then run pa connection create --connector <connector-id> yourself (power-apps create-connection -a <connector-id> on power-apps-only projects). Connectors whose only sign-in option is the user's Microsoft account are created silently. If the CLI says the connection needs a browser sign-in it can't do here, ask the user to run the same command in their own terminal from the project folder (or npx --no-install pa connection create --connector <connector-id> if pa isn't recognized). As a last resort, share the Connections URL using the active environment ID from context (from power.config.json or a prior step): https://make.powerapps.com/environments/<environment-id>/connections → + New connection.
  3. Re-run /list-connections to get the new connection ID.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall