Last PR was corrupted.

 Fixing duplicates and misguidance.

Author: caburk

powerapps-docs/maker/common-data-service/use-solution-explorer.md

@@ -84,25 +84,16 @@ search.app:
 In PowerApps, you can view the classic solution explorer by selecting **Solutions** in the left navigation pane, and then selecting **Switch to classic** in the command bar. Classic solution explorer is the one that was previously available through the **Settings > Advanced customizations** area in PowerApps. 
 
 ## Known limitations
+The following limitations are actively being addressed by the product groups. Please read this list prior to using canvas apps, flows, and custom connectors in solutions. 
 
-- Custom connectors are not available in a solution.
-- Canvas apps must be opened after a solution is imported to update the connections.
-- If a canvas app is packaged in a managed solution, it can still be edited in the target environment.
-- Dependencies are not available for canvas apps.
-- Deleting a managed solution will not rollback to a different canvas app's version. 
--	Canvas app access (CRUD and security) is managed entirely in PowerApps and not the Common Data Service (Common Data Service) database.
--	Common Data Service APIs to call canvas apps are blocked and don't return anything. 
--	Canvas apps created from a solution can't be shared as co-owner to an AAD Security Group.
--	Canvas apps won't display in the classic solution explorer.
-- Flows created from solutions will not be displayed in the "Team Flows" list
-- Button triggered flows are not available in solutions.
 - Canvas app triggered flows are not available in solutions.
+- If a canvas app is packaged in a managed solution, it can't be edited and re-published in the target environment. Use unmanaged solutions if the apps require editing in the target environment. 
+- 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. It can also beneficial to create the connections in the target enviornment prior to importing the solution. 
 -	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.
-- Canvas apps are not currently mastered in Common Data Service. Therefore, the following limitations exist:
-  - Database operations such as backup, restore, and copy are not supported for canvas apps and flows. These operations can corrupt canvas apps and flows.
-  - If a canvas app is packaged in a managed solution, it can't be edited and re-published in the target environment. Use unmanaged solutions if the apps require editing in the target environment. 
-  - Deleting a managed solution will not rollback to a different canvas app's version. Instead all versions of the app will be deleted.
+-	Canvas app access (CRUD and security) is managed entirely in PowerApps and not the Common Data Service (Common Data Service) database.
+- 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 will not rollback to a different canvas app's version. Instead all versions of the app will be 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. 
@@ -111,6 +102,7 @@ In PowerApps, you can view the classic solution explorer by selecting **Solution
 - 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.