list-connections

Plugin check: Run node "${PLUGIN_ROOT}/scripts/check-version.js" - if it outputs a message, show it to the user before proceeding.

? Shared instructions: shared-instructions.md — read first for cross-cutting concerns (Windows CLI compatibility, memory bank, etc.).

List Connections

App root: before any project read or command, execute app-working-directory.md. Reuse the resolved absolute working_dir for every shell call and file tool, including auth retries and the environment read used for portal URLs. Forwarded owner context is required for child calls; do not fall back to the launch directory. Reapply the guard and arguments in each fresh call.

Finds or creates a Power Platform connection with the Power Apps CLI. Returns the Connection ID or Connection Reference that callers feed into pa app add data-source.

Workflow

1. Get Connection → 2. Present Results

---

Step 1 — Get Connection

Telemetry checkpoint: resolve_power_platform_connection

Use one of the supported paths below.

If the caller already provided a connection ID, validate the connector/API ID from context and return it as-is for --connection-id.

Preserve any supplied connection reference as well; do not create a replacement. Creation requires current approval for the selected environment and connector. For --plan-only or a planning-phase handoff, perform only permitted read-only lookup and return missing access/identity to the owner; never create a connection to unblock discovery. The invocation marker does not grant creation consent.

If the caller provided a connector API ID and needs a new connection, create it from the app root:

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

cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
$PA connection create --connector <api-id> --json

Use the returned connectionId for --connection-id <connectionId>. Optional display names are supported:

cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
$PA connection create --connector <api-id> --display-name '<display-name>' --json

Browser-based connection creation is disabled by default. If the connector is not SSO-eligible and the command reports that browser creation is disabled, tell the user to either set POWERAPPS_CLI_ENABLE_BROWSER_CONNECTION=true and rerun the command, or create the connection in the maker portal.

Step 1b — Fetch Connection References When Solution-Aware

If the caller provided a solution ID and needs a connection reference name, list connection references from the app root:

cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
$PA connection list-references --solution-id <solution-id> --json

If a matching connection reference exists, return its reference name for --connection-ref <connection-ref>.

If pa connection create or pa connection list-references fails because of auth, wrong user, multiple accounts, no output, or timeout, follow shared-instructions command-failure handling and retry once from the same guarded root. A missing app-local CLI is a blocker, not permission to retry without --no-install or install another version.

Other failures:

• Non-zero exit for any reason other than auth: report the exact output. STOP.

Step 2 — Present Results

Show the supported add path. A Connection ID goes into --connection-id <connection-id> when adding a data source. When Step 1b was requested, also show matching connection references; a Connection Reference goes into --connection-ref <connection-ref>.

If the needed connector is missing:

1. Share the direct Connections URL using the active environment ID from context (read from <working_dir>/power.config.json environmentId): https://make.powerapps.com/environments/<environment-id>/connections → + New connection
2. Search for and create the connector, then complete the sign-in / consent flow
3. Rerun /list-connections <api-id> or provide the portal connection ID so the data-source skill can continue