Live publish

buck1ey · web-flow · commit 6179b3fa92a7 · 2022-11-17T17:00:08.000-08:00
diff --git a/powerapps-docs/cards/card-requirements.md b/powerapps-docs/cards/card-requirements.md
@@ -0,0 +1,52 @@
+---
+title: Requirements for cards
+description: Learn about the requirements for using Cards for Power Apps.
+ms.date: 11/17/2022
+ms.topic: overview
+author: sericks007
+ms.author: sericks
+manager: tapanm-msft
+ms.reviewer: 
+ms.custom: 
+ms.collection: 
+
+---
+
+# Requirements for cards
+
+[!INCLUDE[cards_preview_notice](includes/preview-include.md)]
+
+This article contains information on requirements for cards to show up and work as expected.
+
+## Environment requirements
+
+Cards are available in environments with Dataverse.
+
+The table below shows the environment regions cards are supported in.
+
+| Environment region | Supported in region |
+|--------------|:---:|
+| United States | Yes |
+| Europe | Yes |
+| Asia | Yes |
+| Brazil | Yes |
+| Australia | Yes |
+| Japan | Yes |
+| India | Yes |
+| Canada | Yes |
+| United Kingdom | Yes |
+| Germany | No |
+| Switzerland | No |
+| United Arab Emirates | No |
+| South Africa | No |
+| Korea | No |
+| Norway | No |
+| Sovereign-cloud regions | No |
+
+## Supported platforms for authoring cards
+
+Cards has the same [system requirements as Power Apps](../limits-and-config.md) for authoring cards.
+
+## Supported platforms for sending cards
+
+Cards can be sent to [Microsoft Teams](/send-a-card/send-card-in-teams.md) in desktop, mobile, or web clients.
diff --git a/powerapps-docs/cards/make-a-card/designer-overview.md b/powerapps-docs/cards/make-a-card/designer-overview.md
@@ -1,14 +1,15 @@
 ---
 title: Card designer overview (preview)
 description: Learn about the card designer.
-ms.date: 09/20/2022
+ms.date: 11/17/2022
 ms.topic: overview
-author: iaanw
-ms.author: iawilt
-manager: shellyha
+author: sericks007
+ms.author: sericks
+manager: tapanm-MSFT
 ms.reviewer: 
 ms.custom: 
 ms.collection: 
+
 ---
 
 # Card designer overview (preview)
@@ -83,7 +84,7 @@ You can also enter Power Fx expressions in some properties, creating low-code so
 Use the formula bar to enter a Power Fx expression as a property of the selected control; for example, to calculate a value when a button is clicked. The formula bar even assists you as you're writing an expression. [Learn more about Power FX](../make-a-card/power-fx/intro-to-pfx.md) and the [functions and formulas you can use in an expression](/powerapps/maker/canvas-apps/formula-reference).
 
 > [!NOTE]
-> Some expressions that are supported in Power Apps aren't available for cards. [See details](/make-a-card/power-fx/intro-to-pfx.md).
+> Some expressions that are supported in Power Apps aren't available for cards. For more information, see [Power Fx and cards overview](../make-a-card/power-fx/intro-to-pfx.md).
 
 ### Play button
 
diff --git a/powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md b/powerapps-docs/cards/make-a-card/power-fx/intro-to-pfx.md
@@ -1,14 +1,15 @@
 ---
 title: Power Fx and cards overview (preview)
 description: Learn about Power FX and how it's used to add business logic in cards for Microsoft Power Apps.
-ms.date: 09/20/2022
+ms.date: 11/17/2022
 ms.topic: overview
-author: iaanw
-ms.author: iawilt
-manager: shellyha
+author: sericks007
+ms.author: sericks
+manager: tapanm-MSFT
 ms.reviewer: 
 ms.custom: 
 ms.collection: 
+
 ---
 
 # Power Fx and cards overview (preview)
@@ -28,11 +29,63 @@ The [Power Fx documentation](/power-platform/power-fx/overview) is the main sour
 
 ## Known limitations of using Power Fx in cards
 
-The following Power Fx formulas don't work in cards or work with limitations:
+The following table lists the Power Fx formulas that don't work in cards, or have limitations. All other functions are fully supported.
 
-- Device sensor formulas (**Acceleration**, **App**, **Compass**, **Connection**, and **Location**) don't work.
-- **SaveData**, **LoadData**, and **ClearData** don't work.
-- Form-related formulas (**EditForm**, **NewForm**, **SubmitForm**, **ResetForm**, and **ViewForm**) don't work.
-- **Update** and **UpdateIf** don't work.
-- **Collect**, **Patch**, and **Remove** work with variables and Dataverse tables only.
-- **Set** requires the variable to exist and the variable type to match what you're trying to set it to.
+| Power Fx formula | Supported in cards | 
+|---------|:---:|
+| [Set](/power-platform/power-fx/reference/function-set) | Yes<br><br>Requires the variable to exist and the variable type to match what you're trying to set it to.|
+| [Collect](/power-platform/power-fx/reference/function-clear-collect-clearcollect#collect) | Yes<br><br>Requires the variable to exist and the variable type to match what you're trying to set it to. |
+| [Defaults](/power-platform/power-fx/reference/function-defaults) | No <br><br> Use [Collect](/power-platform/power-fx/reference/function-clear-collect-clearcollect#collect) instead, for example, instead of `Patch(account, Defaults(account), {"Account Name": "Example Account"})` use `Collect(account, {"Account Name": "Example Account"})`. |
+| [User()](/power-platform/power-fx/reference/function-user) | No <br><br>Instead use **Viewer**, which has a subset of information about the user viewing the card. |
+| [Clear](/power-platform/power-fx/reference/function-clear-collect-clearcollect#clear) | No |  
+| [ClearCollect](/power-platform/power-fx/reference/function-clear-collect-clearcollect#clearcollect) | No | 
+| [Update](/power-platform/power-fx/reference/function-update-updateif#update-function) | No | 
+| [UpdateIf](/power-platform/power-fx/reference/function-update-updateif#updateif-function) | No | 
+| Device sensor formulas ([Acceleration, App, Compass, Connection, and Location](/power-platform/power-fx/reference/signals)) | No | 
+| [SaveData, LoadData, and ClearData](/power-platform/power-fx/reference/function-savedata-loaddata) | No | 
+| Form-related formulas ([EditForm, NewForm, SubmitForm, ResetForm, and ViewForm](/power-platform/power-fx/reference/function-form)) | No | 
+| AddColumns | No |  
+| Concurrent | No | 
+| DropColumns | No | 
+| EncodeUrl | No | 
+| IsEmpty | No | 
+| IsMatch | No | 
+| IsType | No | 
+| JSON | No | 
+| Match | No | 
+| PlainText | No | 
+| RemoveIf | No | 
+| SortByColumns | No | 
+| Update | No | 
+| UpdateIf | No | 
+| AsType | No | 
+| Distinct | No | 
+| exactin | No | 
+| GroupBy | No | 
+| in | No | 
+| RenameColumns | No | 
+| Search | No | 
+| ShowColumns | No | 
+| UTCNow | No | 
+| UTCToday | No | 
+| Validate | No | 
+| Weekday | No | 
+| As | No | 
+| Calendar | No | 
+| Choices | No | 
+| Clock | No | 
+| ColorFade | No | 
+| ColorValue | No | 
+| Errors | No | 
+| HashTags | No | 
+| ISOWeekNum | No | 
+| Language | No | 
+| MatchAll | No | 
+| Refresh | No | 
+| RGBA | No | 
+| WeekNum | No | 
+| Notify | No | 
+| Select | No | 
+| SetProperty | No | 
+| Download | No | 
+| SetFocus | No | 
diff --git a/powerapps-docs/cards/make-a-card/variables/variables.md b/powerapps-docs/cards/make-a-card/variables/variables.md
@@ -1,14 +1,15 @@
 ---
 title: Add variables to a card (preview)
 description: Learn how to add variables to your cards for Microsoft Power Apps.
-ms.date: 09/20/2022
+ms.date: 11/17/2022
 ms.topic: how-to
-author: iaanw
-ms.author: iawilt
-manager: shellyha
+author: sericks007
+ms.author: sericks
+manager: tapanm-MSFT
 ms.reviewer: 
 ms.custom: 
 ms.collection: 
+
 ---
 
 # Add variables to a card (preview)
@@ -46,6 +47,23 @@ As an example, you've created a card that counts how many times the user presses
 
 1. Select **Save**.
 
+### Using the default value for tables and records
+
+The default value is used to set the structure for table and record variables. There are two ways to set the default value of a record or table variable:
+
+- Using a Power Fx expression
+- Using JSON
+
+You can toggle between whether you are using Power Fx or JSON using the icon on the right.
+
+:::image type="content" source="../../media/variables/default-value.png" alt-text="Screenshot of the how to toggle between JSON and Power Fx for setting the variable default value.":::
+
+Using a Power Fx expression is helpful when you want the variable to store data from a data source, like Dataverse. For example, if you wanted a record that held a specific row from the **Account** table, you could set the default value to `First(account)`.
+
+Using JSON is helpful when you are using the variable to store custom data. For example, if you wanted to collect a list of people's names, you could set the default value to `[{"First Name": "John", "Last Name": "Doe"}]`.
+
+Variables are strongly typed and so setting the default value locks the variable into those types.
+
 ### Edit and delete variables
 
 To edit or delete a variable, select the ellipsis (**...**) to the right of the variable, and then select **Edit** or **Delete**.
@@ -54,8 +72,12 @@ To edit or delete a variable, select the ellipsis (**...**) to the right of the
 
 ## Use variables in cards
 
-There are various ways to use variables in cards. [Learn about working with variables in Power Apps](/powerapps-docs/maker/canvas-apps/working-with-variables.md).
+There are various ways to use variables in cards. [Learn about working with variables in Power Apps](../../../maker/canvas-apps/working-with-variables.md).
 
 A common use for variables is in Power Fx expressions. Refer to the variable by name in your formula. For an example, go to the [simple card tutorial](../../tutorials/hello-world-card.md). Your variables are recognized in the formula bar as well.
 
 :::image type="content" source="../../media/variables/formula-bar-example.png" alt-text="Screenshot of an automatically filled variable name in the card designer formula bar.":::
+
+### Updating the value of a variable
+
+Variables can be updated using the [**Set**](/power-platform/power-fx/reference/function-set) function, excluding table variables which are added to using the [**Collect**](/power-platform/power-fx/reference/function-clear-collect-clearcollect) function.
diff --git a/powerapps-docs/cards/manage-cards/manage-cards.md b/powerapps-docs/cards/manage-cards/manage-cards.md
@@ -0,0 +1,60 @@
+---
+title: Manage cards
+description: This article will help you use security roles to manage cards and explains how to delete a record.
+ms.date: 11/17/2022
+ms.topic: overview
+author: sericks007
+ms.author: sericks
+manager: tapanm-MSFT
+ms.reviewer: 
+ms.custom: 
+ms.collection: 
+
+---
+
+# Manage cards
+
+[!INCLUDE[cards_preview_notice](../includes/preview-include.md)]
+
+This article will help you use security roles to manage cards and explains how to delete a record.
+
+## Manage cards with security roles
+
+This section shows you how to manage cards using security roles.
+
+### Change who can create cards
+
+Cards are stored as rows in Dataverse within the **Card** table. Administrators can use [security roles to control who can create, read, and update cards](/power-platform/admin/wp-security-cds#tablerecord-ownership).
+
+For example, if the user is only assigned to a security role that does not have permission to create rows in the **Card** table, then the user will not be able to create cards.
+
+Note that a user will still be able to receive and use cards sent in Teams, regardless of the security role assigned to the user, as those cards are accessed by the Cards for Power Apps service.
+
+### Disable cards for an environment
+
+The Cards for Power Apps service uses the security role called **Cards Role** to communicate with Dataverse. By removing permissions for the **Cards Role** in an environment to create, read, or update the **Card** table, no one will be able to use cards within that environment.
+
+### Cards security roles
+
+- **Cards Basic Role** can be used to grant a user access to view, create, and use cards in that environment. 
+
+   Other security roles can be modified to view, create, and use cards by changing security role access to the **Card** table in Dataverse.
+
+- **Cards Role** is used internally by the Cards for Power Apps service to communicate with Dataverse.
+
+## Delete a card
+
+This section shows you how to delete a card.
+
+### Delete a card as the owner
+
+1. Sign in to Power Apps.
+1. Select **Cards** from the left pane.
+1. Select the card to be deleted.
+1. Select **Delete** in the command bar.
+
+   :::image type="content" source="../media/manage-cards/delete-a-card.PNG" alt-text="Screenshot of how to delete a card.":::
+
+### Delete a card as the administrator
+
+If the owner of an app is unavailable, it is currently not possible for an administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We are working on enabling this capability.
diff --git a/powerapps-docs/cards/media/manage-cards/delete-a-card.PNG b/powerapps-docs/cards/media/manage-cards/delete-a-card.PNG
diff --git a/powerapps-docs/cards/media/variables/default-value.png b/powerapps-docs/cards/media/variables/default-value.png
diff --git a/powerapps-docs/maker/TOC.yml b/powerapps-docs/maker/TOC.yml
@@ -2914,6 +2914,8 @@
   items:
     - name: What are cards?
       href: ../cards/overview.md
+    - name: Requirements for cards
+      href: ../cards/card-requirements.md
     - name: Design cards
       items: 
         - name: Card Designer overview
@@ -2936,6 +2938,8 @@
       href: ../cards/make-a-card/testing/debugging-cards.md
     - name: Send a card in Teams
       href: ../cards/send-a-card/send-card-in-teams.md
+    - name: Manage cards
+      href: ../cards/manage-cards/manage-cards.md
     - name: Tutorials
       items:
         - name: Create a simple card
diff --git a/powerapps-docs/maker/common/wrap/faq.yml b/powerapps-docs/maker/common/wrap/faq.yml
@@ -21,7 +21,7 @@ sections:
       - question: |
           Can single tenant customers use wrap with Power Apps? 
         answer: |
-          Yes. Both single tenant and multitenant customers can use wrap. However, it is important to assign a correct account type for your app on Azure portal during new app registration. See [App registraion](how-to.md#app-registration) for directions on how to select a correct account type to prepare your app for wrap.
+          Yes. Both single tenant and multitenant customers can use wrap. However, it is important to assign a correct account type for your app on Azure portal during new app registration. See [App registration](how-to.md#app-registration) for directions on how to select a correct account type to prepare your app for wrap.
 
       - question: |
           Does the wrap feature in Power Apps support Customer Managed Keys (CMK) or Lockbox capabilities?
@@ -46,18 +46,28 @@ sections:
       - question: |
           How do I distribute my mobile app?
         answer: |
-          It depends on your business scenario. You can use [Microsoft Intune](/mem/intune/fundamentals/what-is-intune), [Managed Google Play](https://support.google.com/googleplay/work/answer/6138458) or [Apple Business Manager](https://developer.apple.com/custom-apps/). 
+          It depends on your business scenario. You can use [Microsoft Intune](/mem/intune/fundamentals/what-is-intune), [Microsoft App Center](https://visualstudio.microsoft.com/app-center/), [Google Play](https://support.google.com/googleplay/work/answer/6138458) or [Apple Business Manager](https://developer.apple.com/custom-apps/). 
 
       - question: |
-          Do I need to rewrap my mobile app frequently?
+          Do I need to rewrap and redistribute my mobile app frequently?
         answer: |
           Power Apps Mobile is [updated periodically](/power-platform/released-versions/powerapps#all-power-apps-studio-and-power-apps-mobile-versions). Hence, to ensure compatibility with the latest Power Apps release versions, benefit from bug-fixes and new platform features, we recommend that you rewrap and redistribute your mobile app to your end users at least on a monthly basis.
 
       - question: |
-          Do I need to rewrap my mobile app after making changes to the canvas app(s) included in the package?
+          Do I need to rewrap and redistribute my mobile app after making changes to the canvas app(s) included in the package?
         answer: |
-          No. Published changes to the included canvas app(s) are downloaded automatically by existing, released versions of your mobile app. However, we recommend that you rewrap and redistribute your mobile app on a [monthly basis](faq.yml#do-i-need-to-rewrap-my-mobile-app-frequently-) to benefit from platform bug fixes, updates and new features.
-
+          No. Published changes to the included canvas app(s) are downloaded automatically by existing, released versions of your mobile app. However, we recommend that you rewrap and redistribute your mobile app on a [monthly basis](faq.yml#do-i-need-to-rewrap-and-redistribute-my-mobile-app-frequently-) to benefit from platform bug fixes, updates and new features.
+          
+      - question: |
+         How do I update the icons and colors in my mobile app?
+        answer: |
+         You can update icons and colors in your mobile app by rewraping your apps with new icons and colors and redistributing the updated mobile app pacakge.
+         
+      - question: |
+         How do I add or remove canvas apps in my wrapped mobile app?
+        answer: |
+         You can add or remove canvas apps by rewraping your mobile app package with a new set of included apps and redistributing your mobile package.
+          
       - question: |
           What are Primary and Secondary apps in the context of wrap?
         answer: |
diff --git a/powerapps-docs/maker/common/wrap/how-to.md b/powerapps-docs/maker/common/wrap/how-to.md
@@ -39,7 +39,9 @@ Create a new registration for your app in the organizational directory using the
 > [!NOTE]
 > Both single tenant and multitenant customers can use wrap to create native mobile apps based on their Power Apps canvas apps.
 
-When creating a new app registration, ensure to use the supported account type that includes accounts in an organizational directory. Whether you are a single or multitenant maker, select any of the options containing **Any Azure AD directory - Multitenant** when choosing the supported account type for your app to enable it for wrap:
+Whether you are a single or multitenant maker, you must select any of the options containing **Any Azure AD directory - Multitenant** when choosing the supported account type for your app to enable it for wrap. Choose one of the following account types:
+ - Accounts in any organzational directory (Any Azure AD directory - Multitenant)
+ - Accounts in any orgnizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)
 
 :::image type="content" source="media/wrap-intro/AppResgistration_AccountTypes.png" alt-text="App registration - supported account types for wrap.":::
 
diff --git a/powerapps-docs/maker/common/wrap/overview.md b/powerapps-docs/maker/common/wrap/overview.md
