Skip to content
English - United Kingdom
  • There are no suggestions because the search field is empty.

What Is the Difference Between a Managed and Unmanaged Power Platform Solution?

Understand the packaged ChangePilot solution, your customer configuration and the checks needed when releases change.

Applies to: the Dataverse-based ChangePilot Enterprise managed solution and customer-specific configuration in the same environment.

Who this is for: administrators and people building customer-specific flows or customisations.

The managed ChangePilot solution

ChangePilot is delivered as a packaged, versioned managed solution. It contains the application components maintained by ChangePilot. Updates arrive as a new managed-solution package for import into your environment.

Your unmanaged configuration

Use a dedicated Configuration solution for customer-specific flows, environment-variable Current Values and supported customisations. See Create the Configuration solution.

An unmanaged solution groups customer assets; it is not a separate runtime environment or a backup. Components can also have unmanaged customisations layered over a managed component.

What happens during an update

A managed update changes the packaged components. Unmanaged customisations can remain above them, and may affect which changes users see or how a component behaves. Some component types merge changes, while others use the active top layer.

Keeping customer work in the unmanaged layer supports customisation, but it is not a guarantee that every customer flow or integration will work unchanged with every release. A preserved customisation may also hide a newly delivered change.

Microsoft explains this behaviour in Solution layers and merge behaviour.

Prepare and verify customer changes

  1. Record the custom components and configuration your organisation relies on.
  2. Read the release notes and follow your organisation’s testing and backup process.
  3. Import the managed update using the update guide.
  4. Check connection references, Current Values, flow status, tags and important custom behaviour afterwards.
  5. Confirm that both the new standard features and the required customer customisations work as intended.

If something differs after import

Record the installed version, affected component and expected versus actual behaviour. An administrator can inspect the component’s solution layers and related configuration to understand which layer is active.

Do not remove an unmanaged layer, overwrite customisations or uninstall the managed solution as a trial fix. Those changes can remove customer work or affect data. Agree the remedy with your administrator and ChangePilot support.

Use the troubleshooting checklist when contacting support@changepilot.cloud.

Documented configuration examples include status choices, tag options, the email connection and flow templates. Follow each guide and validate the result in your installed release.

Documentation reviewed: 12 November 2026.

ChangePilot Enterprise Help Centre

For ChangePilot deployed in your organisation’s Microsoft environment.

Looking for help with Free, Plus or Business? Visit the ChangePilot Help Centre.