Merging changes synced from https://github.com/MicrosoftDocs/powerapps-docs-pr (branch live)

Author: Learn Build Service GitHub App

powerapps-docs/cards/make-a-card/designer-overview.md

@@ -24,7 +24,7 @@ The Power Apps card designer is the drag-and-drop interface in which you build c
 
 1. To open the card designer, select **Create**, and then select **+ Create a card**.
 
-   :::image type="content" source="../media/designer-overview/create-new-card.png" alt-text="Screenshot showing card creation screen.":::
+   :::image type="content" source="../media/overview/create-card-screen.png" alt-text="Screenshot showing card creation screen.":::
 
 ## The card designer interface
 

powerapps-docs/cards/media/overview/create-card-screen.png

@@ -27,7 +27,7 @@ You can create cards with just a few clicks. There are no complex systems or ser
 
 To get started, sign in to [Power Apps](https://make.powerapps.com). Select **Cards (preview)**, and then select **+ Create a card**.
 
-:::image type="content" source="media/overview/cards-get-started.png" alt-text="Screenshot of the card create page in Power Apps.":::
+:::image type="content" source="media/overview/create-card-screen.png" alt-text="Screenshot of the card create page in Power Apps.":::
 
 There are two key components of a card:
 

powerapps-docs/cards/overview.md

@@ -37,9 +37,6 @@ The **Cards for Power Apps** connector is used to get or create instances of car
 - **Get the card instance** - Returns a card instance when given a user-specified card and a card instance id as `card` dynamic content.
 - **Get the card description** - Returns information about a user-specified card, including the id, environmentId, name, description, author, etc.
 
-> [!NOTE]
-> The **Cards for Power Apps** connector is temporarily marked as premium but the license requirements of people sending and receiving cards in Teams is dependent on the card - only cards with premium connectors or controls require users to have premium licenses. The connector will be updated to standard before general availability to reflect this licensing model.
-
    :::image type="content" source="../media/send-a-card/cards-connector.png" alt-text="Screenshot of the cards for Power Apps connector.":::
 
 ## Send card in Teams using the Teams connector

powerapps-docs/cards/send-a-card/send-card-with-flow.md

@@ -55,7 +55,7 @@ More information: [Data types (Transact-SQL)](/sql/t-sql/data-types/data-types-t
 - owner
 - state
 - status
-- multiselectpicklist
+
 
 ### [Not supported](#tab/not-supported)
 
@@ -70,6 +70,7 @@ More information: [Data types (Transact-SQL)](/sql/t-sql/data-types/data-types-t
 - managedproperty
 - file
 - xml
+- multiselectpicklist
 
 ---
 

powerapps-docs/developer/data-platform/how-dataverse-sql-differs-from-transact-sql.md

@@ -3,7 +3,6 @@ title: "Ribbon types schema (model-driven apps) | Microsoft Docs" # Intent and p
 description: "The following is the schema definition for the ribbon types portion of an import/export customization file. It is included from the Ribbon Core Schema." # 115-145 characters including spaces. This abstract displays in the search result.
 author: HemantGaur
 ms.author: hemantg
-
 ms.date: 04/01/2022
 ms.reviewer: jdaly
 ms.topic: reference
@@ -22,7 +21,7 @@ The following is the schema definition for the ribbon types portion of an import
 
 Download the [Schemas](https://download.microsoft.com/download/B/9/7/B97655A4-4E46-4E51-BA0A-C669106D563F/Schemas.zip).
 
-For more information, see [Package and distribute Eetensions with solutions](../data-platform/introduction-solutions.md).
+For more information, see [Package and distribute extensions with solutions](../data-platform/introduction-solutions.md).
 
 [!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
 
@@ -866,4 +865,4 @@ For more information, see [Package and distribute Eetensions with solutions](../
  [Customization XML reference](customization-xml-reference.md)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/model-driven-apps/ribbon-types-schema.md

@@ -40,7 +40,7 @@ We'll use **keytool.exe** (available after installing Android Studio, from the f
 
 To generate a key, open a command prompt and run the following command:
 
-`keytool -genkey -alias SIGNATURE_ALIAS -keyalg RSA -keystore PATH_TO_KEYSTORE -keysize 2048 -validity 100`
+`keytool -genkey -alias SIGNATURE_ALIAS -keyalg RSA -keystore PATH_TO_KEYSTORE -keysize 2048 -validity 10000`
 
 
 Parameters:

powerapps-docs/maker/common/wrap/code-sign-android.md

@@ -28,9 +28,33 @@ Earlier, you learned about the capabilities of wrap feature, how it works, and i
 - You'll need one or more canvas apps (saved in a solution) that you can package for mobile user distribution.
 - To use Android platform, ensure you [generate keys](code-sign-android.md#generate-keys), and then [generate signature hash](code-sign-android.md#generate-signature-hash) before you [register the app](#app-registration). You'll need the generated signature hash to configure the **Redirect URI**.
 
+## Install wrap for Power Apps in your environment
+Go to [Dynamics 365 apps](https://admin.powerplatform.microsoft.com/resources/applications) section on [Power Platform admin center](https://admin.powerplatform.microsoft.com), select **Wrap for Power Apps** and click on **Install** option.
+
+ :::image type="content" source="media/wrap-canvas-app/install-wrap-for-power-apps.png" alt-text="Install wrap for Power Apps.":::
+ 
+ Select your environment from the list and click **Install** button.
+ 
+ :::image type="content" source="media/wrap-canvas-app/install-wrap-for-power-apps-1.png" alt-text="Select environment and begin installation.":::
+
+> [!NOTE]
+> You need to have admin rights to the environment to install wrap for Power Apps.
+
 ## Add canvas app to solution
 
-This feature requires the apps to be part of a solution. If your canvas apps aren't part of a solution already, add them to an existing or a new solution. More information: [Add an app to a solution](../../canvas-apps/add-app-solution.md#add-an-existing-canvas-app-to-a-solution)
+This feature requires the apps to be part of a solution. If your canvas apps aren't part of a solution already, add them to an existing or a new solution. Go to **Solutions** section, select a solution and press **Edit** button.
+
+:::image type="content" source="media/wrap-canvas-app/select-solution.png" alt-text="Select a solution.":::
+
+Chooose **+ Add existing** option from the top menu and select **App > Canvas app** in the dropdown list.
+
+:::image type="content" source="media/wrap-canvas-app/select-add-existing.png" alt-text="Select Add existing from the menu.":::
+
+Select **Oustide Dataverse** tab and choose your app from the list. Press **Add** button to add this app to a solution.
+
+:::image type="content" source="media/wrap-canvas-app/add-app.png" alt-text="Select Add app to a solution.":::
+
+More information: [Add an app to a solution](../../canvas-apps/add-app-solution.md#add-an-existing-canvas-app-to-a-solution)
 
 ## App registration
 
@@ -90,7 +114,7 @@ Add-AdminAllowedThirdPartyApps -ApplicationId <App ID>
     - *Azure API Connections*
     - *PowerApps Service*
     - *Power BI* (only required if your canvas app(s) use Power BI data)
-    - *Mobile Application Management* (only required if you want to use [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) for mobile app distribution)
+    - *Microsoft Mobile Application Management* (only required if you want to use [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) for mobile app distribution)
 
 > [!NOTE]
 > If you don't find the permissions under **APIs my organization uses**, run the following PowerShell commands as appropriate, and try again: