Power Platform Solution Import Health Check (CMS GCC)

#Purpose

Use this checklist to confirm that a Power Platform solution is ready for UAT or Production and remains operational after import. A successful import alone does not confirm that connections, configuration, flows, applications, permissions, or dependent resources work correctly.

#When to Use

• Before importing a solution into UAT or Production.
• Immediately after every UAT or Production import.
• After changing connections, environment variables, connectors, security roles, or service identities.
• When deploying apps, flows, Dataverse components, or SharePoint integrations.
• When CMS GCC DLP or connector-policy changes may affect a solution.

#Pre-Import Checklist

• Confirm the approved solution name, publisher, version, package type, and release record.
• Verify that required apps, flows, Dataverse components, security roles, connection references, environment variables, and other dependencies are included or documented as prerequisites.
• Confirm that prerequisite solutions and target resources exist, and document the required import order.
• Verify that new components were created inside the intended solution rather than only in the default solution.
• Replace hard-coded URLs, GUIDs, email addresses, site names, paths, and endpoints with environment variables or another approved configuration mechanism.
• Confirm that supported connectors use solution-aware connection references.
• Verify that deployment administrators, flow owners, service identities, teams, and test users have the required licenses and least-privilege access.
• Review connector combinations, HTTP calls, external services, inline Base64, and data: URI patterns against CMS GCC DLP requirements.
• Test critical functionality with production-representative data and resolve delegation, pagination, timeout, and performance risks.
• Complete applicable accessibility and Section 508 validation.
• Document deployment ownership, validation responsibilities, and the rollback or forward-fix plan.

#Import Validation Checklist

• Confirm the target environment and verify the package name, version, and managed or unmanaged type.
• Import prerequisite and dependent solutions in the documented order.
• Map each connection reference to the approved target-environment connection.
• Supply or confirm all required environment variable values.
• Review import warnings and component errors before completing the deployment.
• Confirm that the installed solution version matches the approved package.
• Save the import result and component-level log with the release evidence.
• Do not release the solution based only on a successful import message.

#Post-Import Checklist

• Confirm that each connection reference is mapped, authenticated, warning-free, and authorized for its required resources.
• Verify that Production connections use approved durable identities where required.
• Review environment-variable current values and confirm that no Development URL, endpoint, mailbox, site, path, or identifier remains active.
• Save and publish configuration changes, then reopen or resave dependent components when required.
• Resolve Power Automate connection, authentication, input, and upgrade warnings; confirm that required flows are enabled.
• Generate the expected event for each critical trigger and confirm that the run completes with the correct records, files, links, and notifications.
• Open each Canvas or model-driven app as representative authorized and unauthorized users; verify target data sources, sharing, roles, and security boundaries.
• Complete the applicable app release-readiness checks for delegation, responsive behavior, accessibility, error handling, navigation, forms, views, and commands.
• Verify that required Dataverse tables, columns, relationships, choices, forms, views, and security roles match the approved design.
• Test representative Dataverse create, read, update, delete, associate, and lookup operations, including required Append and Append To privileges.
• Verify required SharePoint sites, lists, libraries, folders, columns, templates, and least-privilege permissions.
• Test the SharePoint, Excel, and other connector operations used by the solution in the CMS GCC target environment.
• Execute each critical business process end to end with production-representative data and confirm that results are complete.
• Record the tester, date, environment, solution version, flow run IDs, results, evidence, and accepted warnings.

#Pass / Warning / Fail Criteria

#Pass

Assign Pass when:

• The import has no unresolved errors or material warnings.
• Required components, dependencies, connections, and environment configuration are correct.
• Critical flows, applications, Dataverse operations, SharePoint operations, and end-to-end processes pass.
• Security, CMS GCC connector behavior, deployment evidence, and recovery procedures are validated.

#Warning

Assign Warning only when:

• Required functionality, security, data integrity, accessibility, and recoverability are unaffected.
• A tested mitigation exists.
• The risk, owner, approval, and resolution or review date are documented.

A warning must not be used to bypass a release-blocking failure.

#Fail

Assign Fail when any of the following remains unresolved:

• Import error, missing dependency, or required component failure.
• Unhealthy connection or incorrect environment configuration.
• Critical flow, application, Dataverse, SharePoint, or end-to-end test failure.
• Unauthorized access or incorrect security behavior.
• CMS GCC policy conflict without an approved workaround or exception.
• Incomplete production-scale results.
• Missing deployment evidence or recovery plan.

Do not release a solution with an overall Fail assessment.

#Related KB Articles

• Environment Variable Values Not Updating After Solution Import — missing, incorrect, or stale environment-variable values.
• Power Automate Flow Trigger Not Firing After Solution Import — disabled flows, trigger failures, connection problems, and post-import permissions.
• Power Automate - CMS GCC DLP & Connector Workarounds — HTTP restrictions, inline content, Excel file readiness, and file-conversion patterns.
• Power Automate - Common Error Fixes — Dataverse Choice errors, formatted values, Filter array expressions, and conditional logic.
• Power Apps - Avoiding Mistakes in Custom Canvas Applications — Canvas App security, delegation, performance, accessibility, error handling, and release readiness.
• Building Canvas Apps with Power Platform at CMS — CMS Canvas App configuration, ALM, accessibility, and access-management guidance.
• Automated Testing for Canvas Apps with Playwright — CMS GCC end-to-end and accessibility test automation.
• Canvas App Excel Export: Power Automate Flow Pattern — Dataverse, Excel Online, SharePoint, connection-reference, and environment-variable validation.