Formatters & Code
Power Platform Deployment Settings Validator & Connection Fixer
Validate Power Platform deployment settings JSON locally. Compare solution customizations.xml against settings, fix missing connections and variables.
Solution package & deployment settings
or click to browse (all inspection is done locally in your browser)
Results
What the result means
Power Platform automated ALM pipelines require a deploymentSettings.json configuration file (commonly created with pac solution create-settings) to supply target environment connection IDs and environment variable values during solution import. This client-side validator inspects your exported Power Platform solution ZIP package, traverses customizations.xml to detect every declared connection reference and environment variable definition, and cross-references them against your target deployment settings JSON. The scanner immediately flags missing connection references, blank or placeholder ConnectionId values, and connector ID mismatches before automated pipelines fail in Azure DevOps or GitHub Actions, and generates a corrected deployment settings template ready for import.
Related tools
Guides
Questions
Why does pac solution import or ALM deployment fail with connection reference errors?
This failure occurs when a solution component (like a cloud flow or canvas app) expects a connection reference that is either missing from deploymentSettings.json or has an empty ConnectionId parameter.
Does this tool upload my solution package or secrets to a server?
No. All ZIP unpacking, XML parsing, and JSON comparisons occur entirely in your browser using local JavaScript. Your solution code and environment variables remain private on your computer.
How does this validator handle environment variable default values?
If an environment variable has a default value declared in the solution but is omitted in your settings file, the validator flags it as a warning and includes the default value in the corrected template.