deploy
The deploy skill builds and deploys a Power Apps code application from the current directory to Power Platform, following a structured workflow that checks project configuration, runs the build process, requests user confirmation, executes the deployment via the Power Apps CLI, and updates project memory with deployment details and app URLs. Use this skill when pushing code changes to a live Power Platform environment, redeploying an existing application, or updating a previously deployed app.
git clone --depth 1 https://github.com/microsoft/power-platform-skills /tmp/deploy && cp -r /tmp/deploy/plugins/code-apps/skills/deploy ~/.claude/skills/deploySKILL.md
**📋 Shared Instructions: [shared-instructions.md](${CLAUDE_PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns.
# Deploy
Builds and deploys the app in the current directory to Power Platform.
## Workflow
1. Check Memory Bank → 2. Build → 3. Deploy → 4. Update Memory Bank
---
### Step 1: Check Memory Bank
Check for `memory-bank.md` in the project root. If found, read it for the project name and environment. If not found, proceed — the project may have been created without the plugin.
### Step 2: Build
```bash
npm run build
```
If the build fails:
- **TS6133 (unused import)**: Remove the unused import and retry.
- **Other TypeScript errors**: Report the error with the file and line number and stop. Do not deploy a broken build.
Verify `dist/` exists with `index.html` before continuing.
### Step 3: Deploy
Ask the user: _"Ready to deploy to [environment name]? This will update the live app."_ Wait for explicit confirmation before proceeding.
```bash
npx power-apps push
```
Capture the app URL from the output if present.
If deploy fails, report the error and stop — do not retry silently. Common fixes:
- Auth error / token expired → `npx power-apps logout`, then retry — the CLI will re-prompt browser login.
- Environment mismatch → update `environmentId` in `power.config.json` to the correct value and retry.
### Step 4: Update Memory Bank
If `memory-bank.md` exists, update:
- Last deployed timestamp
- App URL (if captured)Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to add a data source, add a connection, add an API, add a connector, connect to SharePoint / Dataverse / SQL / Excel / OneDrive / Teams / Office 365, or any similar request to make new data available to the app. DO NOT USE WHEN the user is asking to list or describe existing data sources — call list_data_sources or list_apis directly instead.
Creates or edits a Power Apps Canvas App through the Canvas Authoring MCP coauthoring session. Handles new app generation from requirements, simple inline edits, and complex multi-screen changes with parallel screen builders. Triggers on requests to create, build, generate, modify, update, change, or edit a Canvas App or .pa.yaml files.
Configure the Canvas Authoring MCP server for the current coauthoring session. USE WHEN "configure MCP", "set up MCP server", "MCP not working", "connect Canvas Apps MCP", "canvas-authoring not available", "MCP not configured", "set up canvas apps". DO NOT USE WHEN prerequisites are missing — direct the user to install .NET 10 SDK first.
[DEPRECATED — use canvas-app instead] Generate a complete Power Apps canvas app.
>
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.
Adds a data source or connector to a Power Apps code app. Asks what the user wants to accomplish and routes to the appropriate specialized skill.