Solutions overview

Solutions are used to transport apps and components from one environment to another or to apply a set of customizations to existing apps. A solution can contain one or more apps as well as other components such as site maps, entities, processes, web resources, option sets, flows, and more.

Solutions are the mechanism for implementing application lifecycle management (ALM) in Power Apps and other Power Platform products, such as Power Automate. For detailed information about the solution concepts and how solutions are used for application lifecycle management, see Overview of ALM with Microsoft Power Platform in the Power Platform ALM guide.

This section will focus on the manual tasks that app makers need to perform while working with solutions in Power Apps.

Get started: solution concepts

Before you work with solutions, it's important that you get acquainted with the following solution concepts:

  • Two types of solutions (managed and unmanaged)
  • Solution components
  • Lifecycle of a solution (create, update, upgrade, and patch a solution)
  • Solution publisher
  • Solution and solution component dependencies

For detailed information, see Solution concepts in the Power Platform ALM guide.

Default solutions

Power Apps provides you the following default unmanaged solutions:

  • Common Data Service Default Solution. This solution is available for makers to use by default for their customizations in an environment. The Common Data Service Default Solution is useful when you want to evaluate or learn Power Apps. However, we recommend that app makers work in their own unmanaged solutions.
  • Default Solution. This is a special solution that contains all components in the system. The default solution is useful for discovering all the components and configurations in your system.

However, we recommend that you create a solution to manage your customizations. More information: Use a solution to customize in the Power Platform ALM guide.

Managed properties

You can control which of your managed solution components are customizable by using managed properties. We recommend that you set managed properties so that your managed components can’t be modified. This helps protect your solution from modifications that may cause it to break after it's imported into another environment, such as test or production.

More information: Managed properties in the Power Platform

Work with solutions in Power Apps

Within Power Apps, you can view a list of solutions by selecting Solutions in the left navigation. You can perform these solution tasks:

  • New solution: To locate and work with just the components you’ve customized, create a solution and do all your customization there. Then, you can easily distribute your solution to other environments. More information: Create a solution

  • Import: Import a solution into your environment. More information: Import solutions

  • Open AppSource: Microsoft AppSource is where you can go to get solutions tailored to your industry that work with the products you already use.

  • Publish all customizations: Publish all active customizations in your environment.

  • Switch to classic: Open the classic solution explorer.

  • See history: View details about solution operations over time, such as import, export, and uninstall. More information: View the history of a solution

    Solutions area

From the Solutions area, select a solution to view all of its components.

Demo solution with all components

You can browse through all the components in a solution by scrolling through the items. If there are more then 100 items in the list you can select Load the next 100 items to see more.

Load more components

Search and filter in a solution

You can also search for a specific component by its name.

Search component

Or filter all items in the list by the component type.

Filter component by type

Contextual commands

As you select each component, the actions available in the command bar will change depending on the type of the component you have selected and if the solution is the default or a managed one.

Component specific commands

When you don't select any component, the command bar will show actions applied to the solution itself.

Solution specific commands

With solutions that are unmanaged or the default one, you can use the New or Add Existing command to create or add different types of components. More information: Add solution components


You can't add components to a managed solution. When you try to, you’ll see the following message:
"You cannot directly edit the components within a managed solution. You’ll need to add it to another unmanaged solution that you’ve created to customize the component. The component might not be customizable."

Known limitations

The following limitations apply to the use of canvas apps, flows, and custom connectors in solutions.

  • Connections require authentication and consent, which requires an interactive user session and therefore cannot be transported via solutions. After importing your solution, play the app to authenticate connections. You can also create the connections in the target environment prior to importing the solution.
  • Canvas app button triggered flows must be created from an app already in a solution. Adding this type of flow from outside solutions is blocked.
    • The app and flow will not currently be connected in the target environment post deployment. First associate valid connections with the flow and activate the flow. Then edit the app and re-associate the flow to the button.
  • Canvas apps shared as co-owner to an Azure Active Directory (AAD) security group can't be added to solutions. Unshare the app before adding it to a solution.
  • Canvas apps won't display in the classic solution explorer. Use the modern experience. There are no plans for them to be added to classic solution explorer.
  • Database operations such as backup, restore, and copy are not supported for canvas apps and flows. These operations can corrupt canvas apps and flows.
  • Deleting a managed solution does not rollback to a different canvas app version. Instead, all versions of the app are deleted.
  • Importing a solution containing a flow will not automatically create or associate required connections. The flow must be edited to fix the connections.
    • If using managed solutions, this creates an active customization in the unmanaged layer. Therefore subsequent solution updates to the flow will not be reflected.
  • Flows created from solutions will not be displayed in the "Team Flows" list. They must be accessed through a solution.
  • Button triggered flows are not available in solutions.
  • Flows triggered from Microsoft 365 applications such as Excel are not available in solutions.
  • Flows that connect to SharePoint are not available in solutions.
  • Flows in solutions don't support delegated authentication. For example, access to a flow is not automatically granted based on having access to the SharePoint list the flow was created from.
  • Custom connectors created outside solutions cannot be added to solutions at this time.

For details about customizing the individual components in a solution, see the following topics:

  • For entity, entity relationships, field and message customizations, see Metadata.

  • For entity forms, see Forms.

  • For processes, see Processes.

  • For business rules, see Business Rules.

Next steps

Create a solution