
list-connections
โ Officialโ 413by microsoft ยท part of microsoft/power-platform-skills
Use when the user asks to find, create, or look up a Power Platform connection ID or connection reference for the current environment.
This is the playbook your agent receives when the skill activates โ you don't need to read it to use the skill, but it's here to audit before installing.
๐ Shared instructions: shared-instructions.md โ cross-cutting concerns (Windows CLI compatibility, memory bank, etc.).
List Connections
Finds or creates a Power Platform connection with the Power Apps CLI. Returns the Connection ID or Connection Reference that callers feed into npx power-apps add-data-source.
Workflow
- 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.
If the caller provided a connector API ID and needs a new connection, create it from the app root:
npx power-apps create-connection --api-id <api-id> --jsonUse the returned connectionId for --connection-id <connectionId>. Optional display names are supported:
npx power-apps create-connection --api-id <api-id> --display-name '<display-name>' --jsonBrowser-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:
npx power-apps list-connection-references --solution-id <solution-id> --jsonIf a matching connection reference exists, return its reference name for --connection-ref <connection-ref>.
If npx power-apps create-connection or list-connection-references fails because of auth, wrong user, multiple accounts, no output, or timeout, follow shared-instructions command-failure handling and retry once.
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:
- Share the direct Connections URL using the active environment ID from context (read from
power.config.jsonenvironmentId):https://make.powerapps.com/environments/<environment-id>/connectionsโ + New connection - Search for and create the connector, then complete the sign-in / consent flow
- Rerun
/list-connections <api-id>or provide the portal connection ID so the data-source skill can continue
npx skills add microsoft/power-platform-skills --skill "list-connections" --full-depthRun this in your project โ your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under MITโ you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub โ