Update solutions-overview.md

Updating known limitations based on recent product updates to support such scenarios.

Author: caburk

powerapps-docs/maker/common-data-service/solutions-overview.md

@@ -130,15 +130,9 @@ With solutions that are unmanaged or the default one, you can use the **New** or
 
 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.