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

[This article is prerelease documentation and is subject to change.]

You can create a canvas app in a solution in Power Apps or create a cloud flow in a solution in Power Automate. Creating a canvas app or a cloud flow in a solution previously required manual steps. Now you can create them in a solution by default.

Because canvas apps and cloud flows in a solution are defined in Microsoft Dataverse, you can use Dataverse capabilities to manage them, including connection references, environment variables, the Dataverse API, role-based security, and solution-based application lifecycle management (ALM).

Important

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.

Prerequisites

• Solutions are stored in Dataverse, so the environment must have a Dataverse database to use this feature. If yours doesn't, add a Dataverse database.
• To create canvas apps in solutions, you must have Write privileges to the CanvasApp table. To create cloud flows in solutions, you should have the Environment Maker role. For more information, see security roles and privileges.
• A canvas app or cloud flow in a solution must be shared with you before you can view or edit it.

Important

Before you enable the creation of canvas apps and cloud flows in solutions by default, review the considerations.

Supported creation methods and entry points

Several methods and entry points are available for creating canvas apps and cloud flows.

Canvas apps creation methods and entry points

The following table summarizes the methods that allow you to create canvas apps in a solution by default.

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

Cloud flows creation methods and entry points

The following table summarizes the methods that allow you to create cloud flows in a solution by default.

Method	Available for cloud flows in a solution by default?
Create a cloud flow from blank in a portal	Yes
Create a cloud flow from a template in a portal	Yes
Create a cloud flow from Power Automate Management connector	Yes
Create a cloud flow from PowerShell	Yes
Create a cloud flow from Power Apps	Yes
Create a cloud flow from Teams	Yes
Create a cloud flow from OneDrive	Yes
Create a cloud flow from Dynamics 365	Yes
Create a cloud flow from the Excel add-in	Yes
Create a cloud flow from the Power Automate mobile app	Yes
Create a cloud flow from SharePoint	Yes
Create a cloud flow from Project Roadmap	Yes

Important

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. You must first create a cloud flow in a solution using a supported method.

Enable the feature

This feature is disabled by default. You must enable it before you can use it.

1. Sign in to the Power Platform admin center and select an environment.
2. Go to Settings > Product > Features.
3. Under Create new canvas apps and cloud flows in Dataverse solutions (Preview`), turn on Canvas apps and Cloud flows as desired.

Learn more about managing feature settings.

View canvas apps and cloud flows in solutions

To view canvas app and cloud flow objects in a solution, use the solution view. You must have access to the object added inside a solution to view it in a solution view.

Export and import using solutions

Once the feature is enabled, use solutions export and import instead of exporting and importing legacy packages of canvas apps and flows. Legacy packages can be imported in environments with the environment setting turned off.

Considerations

Take the following considerations into account before you decide to create canvas apps and cloud flows in a solution by default.

• Your Dataverse environment capacity consumption and related cost might increase.

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

• This feature automatically creates environment variables when you add data sources for your apps.

• By default, this feature saves all canvas apps to the default solution, Common Data Services Default Solution, published by Microsoft Dataverse Default Publisher. However, we recommend that you save your canvas apps to a different solution. Learn more about adding existing canvas apps to solutions.

• When you turn the feature on or off for canvas apps and cloud flows in the Power Platform admin center, the Dataverse properties enablecanvasappsinsolutionsbydefault and enableFlowsInSolutionByDefault in the organization table are updated. You can view the value of these properties using the following sample ODATA snippet: [org URI]/api/data/v9.0/organizations. For more information, see 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's no way to revert back.

Improvements

The following scenarios were improved to support cloud flows and canvas apps defined in Dataverse:

• The Monitor > Cloud flow activity page now supports solution cloud flows.
• The List My Flows API doesn't return any solution cloud flows.

Known issues

• 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). This API is updated to return all solution cloud flows.
• Flows with delegated authentication to Roadmap can't be added into a solution and migrated to Dataverse.
• You can't add flows with delegated authentication to SharePoint into a solution and migrate them into Dataverse directly. However, you can remove the delegated authentication to allow migration and then add it back after migration.

See also

Solutions overview
Application lifecycle management (ALM) guide