diagnose-deployment

Diagnoses Power Pages deployment failures by pattern-matching PAC CLI and Dataverse errors against a known catalog.

808|167|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/microsoft/power-platform-skills --skill diagnose-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-deployment
Source: https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-pages/skills/diagnose-deployment
Command: npx skills add https://github.com/microsoft/power-platform-skills --skill diagnose-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Power Pages deployments can fail with opaque PAC CLI upload errors or silent Dataverse solution import failures, leaving developers guessing at root causes. This Skill surfaces those errors, matches them against a catalog of known failure patterns, and offers verified auto-fixes with explicit user consent.

Core Features & Use Cases

  • Error Surfacing and Parsing: Re-runs pac pages upload-code-site in capture mode and queries Dataverse async operations and import jobs to collect fresh failure data.
  • Pattern-Matched Diagnosis: Categorizes findings as Error, Warning, or Info by matching against a known deployment error catalog, grounded in current Microsoft Learn ALM documentation.
  • Consent-Gated Auto-Fixes: Offers per-finding fixes for issues like stale manifests, blocked JavaScript uploads, missing website record IDs, expired auth, and empty builds, each requiring explicit approval.
  • Use Case: Your pac pages upload-code-site run fails with a cryptic message. Invoke this Skill to identify that JavaScript attachments are blocked at the environment level, approve the settings fix, and verify the deployment unblocks.

Quick Start

Ask the agent to diagnose why my Power Pages deployment failed and fix any known issues.

Frequently Asked Questions about diagnose-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot a failed Power Pages deployment?

Run the diagnose-deployment skill, which re-executes pac pages upload-code-site in capture mode, parses the output against a known error catalog, and also checks Dataverse async operations and import jobs for solution-level failures.

Why does pac pages upload-code-site fail with JavaScript upload errors?

The environment's blockedattachments setting may include .js files, blocking script uploads. The skill detects this pattern and, with your approval, updates the setting via pac env update-settings while preserving other blocked file types.

Does the skill apply deployment fixes automatically?

No. Every auto-fix requires explicit per-finding confirmation through a consent prompt. You can approve, decline, or skip all fixes, and each fix is re-verified after application.

Can deployment diagnostics run without Azure CLI authentication?

Yes. Authentication failures are non-blocking. The skill reports them as findings, skips the Dataverse async operation queries, and continues diagnosing PAC CLI upload errors and local artifact issues.

What does a missing websiteRecordId error mean in powerpages.config.json?

It means the project is not linked to a website record in the target environment. The skill can run pac pages list, match the site by name, and update the config file with the correct record ID after your approval.