PowerPreFlight

Scan a Dynamics 365 or Power Platform environment and mark every step to safely deploy a workload or roll out Copilot Studio, against Microsoft’s Success by Design practices. It runs on your machine, not ours.

Origin

Before every flight, pilots run a preflight checklist — a systematic verification that everything is ready before committing to takeoff. PowerPreFlight does the same for Dynamics 365 and Power Platform deployments: it scans the environment against Microsoft’s Success by Design practices and produces the checklist before you commit the workload.

What it does

PowerPreFlight scans Dynamics 365 and Power Platform environments and identifies every step required to safely deploy a workload or roll out Copilot Studio, benchmarked against Microsoft’s Success by Design practices. It cuts the manual labor that consultants normally do by hand in DLP policy configuration, connector management, and pipeline setup. It runs locally through npx, with no install and no persistent footprint. It signs in with Microsoft’s own pre-authorised public client, so no app registration or admin consent is needed, and it only ever has the access the signed-in user already has.

Your environment

A Dynamics 365 or Power Platform environment your account can already reach.

PowerPreFlight scans it

Reads DLP, connectors, pipelines and workload config against Success by Design.

Scored checklist

An ordered, scored set of steps to close the gap before go-live.

Why use it

Fewer manual DLP, connector, and pipeline steps to track by hand during a deployment.
A consistent, repeatable deployment checklist scored against Microsoft’s own framework instead of ad hoc review.
Faster environment readiness assessment before a Copilot Studio or workload go-live.
Nothing to deploy, host, or maintain, and safe to run in a client tenant because it carries zero elevated privilege.

Run it, and what it can touch

Run it

npx powerpreflight

There is nothing to install permanently and nothing to configure to get started. npx fetches the current build each time you run it, so you are always on the latest version and there is no update step. The one prerequisite is Node.js 22 or later (winget install OpenJS.NodeJS.LTS, or brew install node, or nodejs.org).

On first run it will:

start a local server bound to 127.0.0.1 and open your browser;
sign you in to Microsoft interactively;
list the environments your account can reach, so you can pick one and scan it.

Trust and access

Your client does not have to approve anything. Sign-in uses the Microsoft first-party Dataverse public client, which is pre-authorised in every tenant.

No app registration

No registration in the client tenant, no consent prompt, and no Global Administrator to involve.

Only your own access

Every token carries exactly your access, so you still need your own account and security role in the environment. It grants no privilege of its own.

Tokens stay on your machine

Held in memory behind a per-run session token on a 127.0.0.1 listener, not on disk unless you opt in.

Nothing to host

No hosted service holds a credential for your tenant. This origin serves content only, and carries zero elevated privilege.

Where your data goes

Access tokens stay in memory on your machine and are never written to disk unless you pass --persist-cache.
The local server binds 127.0.0.1 only, never your network interface, and every request carries a session token generated fresh for that run.
No Dataverse data is sent to this site. This origin serves the application and its content, the steps and solution library the tool reads, and nothing else.

Configuration

All optional, and the content ones are editable inside the app. These are for scripting a machine, not the normal path.

`PREFLIGHT_CONTENT_URL`	Origin publishing steps and solutions. Defaults to `https://powerpreflight.app/api/content`. You only set this to publish your own, and it is editable inside the app too. `off` runs on bundled content alone.
`PREFLIGHT_CONTENT_TOKEN`	Read token for that content origin, if it needs one. Also settable in the app.
`PREFLIGHT_CLIENT_ID`	Your own public-client registration, for tenants whose conditional access blocks first-party clients.
`PREFLIGHT_REDIRECT_URI`	Override the loopback redirect when a registration requires a specific one.
`PREFLIGHT_OUT`	Output directory for exported scorecards and profiles. Defaults to `./preflight-output`.

There is no web app to sign in to

A hosted console used to run here, and it is gone. Environment preparation, solution deployment and the governance checks all run in the command above, against the environments your sign-in can already reach. This site holds no credential for anyone’s tenant, and there is nothing here to log into.