ALM & GovernanceALM Readiness Checklist
Work through this before any go-live or environment promotion — covers solution design, pipelines, security, and testing.
All tools
✦ Free
0%
Reset
All customisations are inside a managed solution (no default solution changes)
Solution layers are defined: Base → Extension → Config
Prevents upgrade conflicts across environments
Publisher prefix agreed and consistently applied
Connection references used for all connectors (no hardcoded connections)
Environment variables used for all config values (URLs, IDs, keys)
Solution unpacked and committed to source control (Azure DevOps / GitHub)
CI pipeline: export → unpack → commit on every change
CD pipeline: pack → import managed → connection reference update
Uses Service Principal, not a user account
Branch strategy defined (feature branches → dev → UAT → prod)
Rollback plan documented — know which managed solution version to re-import
Security roles follow principle of least privilege — no Business Unit Owner for all users
Service account / Service Principal used for integrations (not a named user)
DLP policies reviewed — connectors classified as Business or Non-Business
Audit logging enabled on sensitive tables (Account, Contact, custom financial)
Column-level security applied to PII or sensitive fields
UAT sign-off completed by a business user (not just IT)
Business process flows tested end-to-end including all stages
Power Automate flows tested with failure scenarios (retries, timeout, null data)
Performance tested with realistic data volume (not just dev sample data)
Data migration validated — record count, key field values, relationship integrity
User training completed and quick-reference guides distributed
Hypercare support window defined (who to call Day 1)
Comms sent to users (what's changing, when, how to get help)
