
deploy
✓ Official★ 408by microsoft · part of microsoft/power-platform-skills
Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.
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.
by microsoft
Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.
npx skills add https://github.com/microsoft/power-platform-skills --skill deploy
Download ZIPGitHub408
📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns.
Workflow
- 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
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.
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
environmentIdinpower.config.jsonto the correct value and retry.
Step 4: Update Memory Bank
If memory-bank.md exists, update:
-
Last deployed timestamp
-
App URL (if captured)
npx power-apps pushRun this in your project — your agent picks the skill up automatically.
Deploy
Builds and deploys the app in the current directory to Power Platform.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.