configure-env-variables

Back the site settings with Dataverse environment variables. The skill creates an environment variable definition per setting, links the site setting via an OData PATCH that flips mspp_source to 1, and generates a deployment-settings.json with per-stage values.

Run this skill after setup-solution: it discovers existing site settings, lets you pick which ones to promote, creates the env var definitions in Dataverse, adds them to the solution, and writes deployment-settings.json for pipeline deployments.

Yes. Secret-type environment variables accept a Key Vault Secret Identifier URI or full Azure resource ID, which Dataverse dereferences at runtime. Plain-text secrets and placeholder formats like @KeyVault(...) are rejected by the pre-write validator.

The deploymentsettingsjson import fails when deployment-settings.json contains non-canonical secret values such as @KeyVault(...) placeholders, raw secret text, or malformed URIs. Use a Key Vault Secret Identifier URI, an Azure resource ID, or an empty string to fall back to the definition default.

You need PAC CLI authenticated, an Azure CLI access token, a .solution-manifest.json created by setup-solution, and a deployed Power Pages site with a .powerpages-site folder. The skill also checks for an existing ALM plan from plan-alm before proceeding.