Add canvas apps and cloud flows to solution by default (preview)

[This article is pre-release documentation and is subject to change.]

You can create canvas apps from within a solution or create a cloud flow in a solution in the solutions section in Power Apps or Power Automate. However, creating canvas apps and cloud flows inside solutions is optional, and requires manual steps.

Canvas apps and cloud flows can now be created in a solution by default. For more information about solutions, see Solutions overview, and application lifecycle management (ALM) guide.

Canvas apps and cloud flows in a solution are defined in Microsoft Dataverse and are more manageable because of Dataverse capabilities including connection references, environment variables, the Dataverse API, and solution-based application lifecycle management (ALM).


  • This is a preview feature.
  • Preview features aren’t meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.


  • Solutions are stored in Dataverse, so the environment must have a Dataverse database to use this feature. If needed, add a Dataverse database.
  • You must have Write privilege to CanvasApp table to create canvas apps in solutions. To create cloud flows in solutions, the Environment Maker role is recommended because there is a set of table permissions needed. For more information, see security roles and privileges.
  • A canvas app or cloud flow within a solution must be shared with you before you can view or edit.


Ensure you review the considerations before enabling canvas apps in solutions by default.

Supported methods

There are different methods available to get started while creating canvas app. Canvas apps that are created within solution by default using this feature require the use of some of these entry points. Hence, it becomes important to understand how this feature can be utilized.

The following table summarizes which entry points benefit from canvas apps within solution by default.

Method Available for canvas apps within a solution by default?
Canvas apps from Dataverse Yes
Canvas apps from other data sources, such as SharePoint, Excel, Azure Blob Storage, and others Yes
Blank canvas app
NOTE: Power Apps > Apps > New app > Canvas also creates a blank canvas app.
Canvas apps from template No
Canvas apps created by customizing SharePoint forms No
Canvas apps created directly from Azure portal using Azure SQL Database No

Supported entry points for cloud flows

There are different entry points for creating cloud flows. The following table summarizes which entry points are supported by the switch for create in Dataverse solutions by default.

Entry point Available for cloud flows within a solution by default?
Create a cloud flow from blank in portal Private preview
Create a cloud flow from template in portal Private preview
Create a cloud flow from Power Automate Management connector Private preview
Create a cloud flow from PowerShell Private preview
Create a cloud flow from Mobile App No
Create a cloud flow from OneDrive No
Create a cloud flow from SharePoint No
Create a cloud flow from other integration points, such as the Excel add-in No
Create a cloud flow from legacy package import No


Unsupported entry points will fail to create any cloud flow until that support is added to create a solution cloud flow with that entry point. Workaround: create using a supported entry point, such as creating directly in the Power Automate portal.

Enable the feature

This feature is disabled by default and must be enabled manually. To enable this feature, go to Power Platform admin center by going to Environments > select an environment > Settings > Product > Features, and view the Create in Dataverse solutions switches. Toggle on the desired switch: Canvas apps and/or Cloud flows. More information: Manage feature settings


Check canvas apps and cloud flows in solutions

To view canvas app and cloud flow objects inside a solution, use the solution view. Only users that have access to the object added inside a solution can view it in a solution view.

Export and import via solutions

Once this feature is enabled, consider using solutions export and import instead of export and import of canvas app packages.


  • Increase in capacity consumption of Dataverse environment and cost implications due to that increased capacity consumption.

  • Known solution limitations related to canvas apps still apply to canvas apps created within solutions by default.

  • This feature also enables the automatic creation of environment variables when adding data sources for your apps.

  • By default, this feature saves all canvas apps to the default solution named Common Data Services Default Solution published by Microsoft Dataverse Default Publisher. However, we recommend that you use a non-default solution for canvas apps. To learn about adding existing canvas apps to solutions, see Add an existing canvas app to a solution.

  • When you toggle one of the feature switches in the Power Platform admin center, the Dataverse properties enablecanvasappsinsolutionsbydefault or enableFlowsInSolutionByDefault in the organization table are updated. The values can be reviewed using the following sample ODATA snippet: [org URI]/api/data/v9.0/organizations. More information: Organization table reference

  • If you're planning to change the prefix for the default publisher, or solution for your environment, see Solution publisher prefix, Create solution publisher prefix and Change solution publisher prefix.

  • Non-solution canvas apps and non-solution cloud flows can be added into a solution to add them into Dataverse, but there is no way to revert back.

Known issues

  • The Monitor > Cloud flow activity page doesn't currently support solution cloud flows.

  • Audit log events for cloud flow permissions that provide visibility into sharing aren't updated for solution cloud flows.

  • The List Flows as Admin API doesn't return solution cloud flows that haven't previously been turned on (published) since the identifier returned is the Logic Apps ID and unpublished flows don't yet have a Logic Apps ID. This API will be updated later to return all solution cloud flows.

  • The List Flows API doesn't return any solution cloud flows. This will be updated later to return solution cloud flows when the List Flows as Admin API is updated.