Checklists¶

New project onboarding¶

Publisher & prefix decided and documented.
Environment strategy decided; dev/build/test environments provisioned with Managed Environments enabled.
Deployment approach decided.
Repository created with the layout in Source Control; .gitattributes/.gitignore in place.
CI pipeline scaffolded per Build Pipeline, including the Solution Checker gate.
dgtp profiles created for build/CI (service principal, not a personal account).
Naming conventions communicated to all customizers on the project.

Naming follows Naming Conventions.
New/changed plugin steps use registration attributes, not manual Plugin Registration Tool changes.
No ILMerge/ILRepack introduced — see Plugin Packages.
Server-side changes have corresponding unit tests using Digitall.Dataverse.Testing.
Generated model output (.cs/.ts) is not committed — see Source Control.
Any deviation from this guideline is documented per Scope & Principles, ideally with its rule ID.

Solution version bumped on the build environment, not hand-edited — see Versioning.
Solution Checker passed with no unresolved high-severity findings.
Environment variable values confirmed for the target environment.
Connection references re-confirmed for the target environment.
Config/reference data migration step run, if the release includes changes to non-solution-aware configuration.
Deployment approval obtained, per the project's Power Platform Pipelines or Azure DevOps/GitHub Actions environment gate configuration.

Beyond the regular pre-deployment checklist, a first production go-live needs (see Microsoft's go-live checklist):

UAT signed off; performance test under realistic load passed.
Data migration rehearsed with a dry run, including throughput measurement — factor service protection limits into the cutover window.
Version parity confirmed: production receives exactly the solution/app versions that passed test/UAT.
Manual environment backup taken immediately before cutover; rollback decision point and criteria documented.
Go/no-go decision taken and documented with the customer.
Hypercare plan active: support responsibilities, escalation path, and coverage agreed; knowledge transfer from project team to support done.
First days after go-live: watch API-limit errors, storage consumption, and flow failure rates (see Monitoring).

Smoke-test the registered plugin steps and Custom APIs expected from this release.
Confirm flows using affected connection references run successfully.
Release tagged in Git — see Versioning.
Release documentation / deployment notes updated per Definition of Done.