Merge branch 'main' of https://github.com/MicrosoftDocs/powerapps-docs-pr into email-changes

Author: gandhamm

powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md

@@ -5,40 +5,46 @@ keywords: Power Apps component framework, code components, Component Framework
 ms.author: noazarur
 author: noazarur-microsoft
 manager: lwelicki
-ms.date: 05/27/2022
+ms.date: 01/27/2023
 ms.reviewer: jdaly
 ms.topic: article
 ms.subservice: pcf
 contributors:
  - JimDaly
+ - kaushikkaul
 ---
 
 # Create and build a code component
 
-This article demonstrates how to create and deploy code components using Microsoft Power Platform CLI. Ensure that you have installed [Microsoft Power Platform CLI](https://aka.ms/PowerAppsCLI).
+This article demonstrates how to create and deploy code components using Microsoft Power Platform CLI.
 
-[!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
+## Prerequisites
 
-## Create a new component
+You need install the following components:
+
+1. [Visual Studio Code (VSCode)](https://code.visualstudio.com/Download) (Ensure the Add to PATH option is select)
+1. [node.js](https://nodejs.org/en/download/) (LTS version is recommended)
+1. [Microsoft Power Platform CLI](/powerapps/developer/data-platform/powerapps-cli#install-power-apps-cli) (Use the Visual Studio Code extension)
 
-To begin, open **Developer Command Prompt for VS 2017 or higher** after installing Microsoft Power Platform CLI.
+## Create a new component
 
-1. In the Developer Command Prompt, create a new folder on your local machine, for example, *C:\Users\your name\Documents\My_code_Component* using the command `mkdir <Specify the folder name>`.
-2. Go to the newly created folder using the command `cd <specify your new folder path>`.
-3. Create a new component project by passing some basic parameters using the [pac pcf init](/power-platform/developer/cli/reference/pcf#pac-pcf-init) command:
+Open Visual Studio code and open a new terminal window by selecting **Terminal** > **New Terminal**.
+1. In the terminal window, create a new folder on your local machine, for example, *C:\projects\My_code_Component* using the command `mkdir <Specify the folder name>`.
+1. Go to the newly created folder using the command `cd <specify your new folder path>`.
+1. Create a new component project by passing some basic parameters using the [pac pcf init](/power-platform/developer/cli/reference/pcf#pac-pcf-init) command:
 
     ```CLI
-    pac pcf init --namespace <specify your namespace here> --name <Name of the code component> --template <component type>
+    pac pcf init --namespace <specify your namespace here> --name <Name of the code component> --template <component type> --run-npm-install
     ```
-4. The above command will also run `npm install` command for you to retrieve all the required project dependencies.
-5. Open your project folder `C:\Users\<your name>\Documents\<My_code_Component>` in any developer environment of your choice and get started with your code component development. The quickest way to get started is by running `code .` from your command prompt once you are in the `C:\Users\<your name>\Documents\<My_code_Component>` directory. This command opens your component project in Visual Studio Code.
-6. Implement the required artifacts for the component like manifest, component logic, and styling and then build the component project. More information: [Create your first code component](implementing-controls-using-typescript.md)
+1. The above command will also run `npm install` command for you to retrieve all the required project dependencies.
+1. Open your project folder `C:\projects\My_code_Component` in any developer environment of your choice and get started with your code component development. The quickest way to get started is by running `code .` from your command prompt once you are in the `C:\projects\My_code_Component` directory. This command opens your component project in Visual Studio Code.
+1. Implement the required artifacts for the component like manifest, component logic, and styling and then build the component project. More information: [Create your first code component](implementing-controls-using-typescript.md)
 
 ## Build your component
 
-To build the component project, open the project folder that contains `package.json` in Visual Studio Code and use the (Ctrl-Shift-B) command, then select the build options. 
+To build the component project, open the project folder that contains `package.json` in Visual Studio Code and use the (Ctrl-Shift-B) command, then select the build options.
 
-Alternatively, you can build the component quickly using the `npm run build` command in the Developer Command Prompt for VS 2017 window for development purposes, or use `npm run build -- --buildMode production` for building a release version.
+Alternatively, you can build the component quickly using the `npm run build` command in the Visual Studio Code terminal window for development purposes, or use `npm run build -- --buildMode production` for building a release version.
 
 > [!TIP]
 > To debug the component during or after the build operation, see [Debug a code component](debugging-custom-controls.md).

powerapps-docs/developer/data-platform/tools/devtools-create-plugin.md

@@ -2,7 +2,7 @@
 title: "Quickstart: Create a plug-in using Power Platform Tools | Microsoft Docs"
 description: "Learn how to create and register a Dataverse plug-in using the Power Platform Tools extension for Visual Studio."
 ms.custom: ""
-ms.date: 06/20/2020
+ms.date: 01/27/2023
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -25,10 +25,9 @@ If you already have an existing Dataverse solution set up, then follow these [in
 
 ## Prerequisites
 
-- Visual Studio 2019
+- Visual Studio 2019 or 2022
 - Power Platform Tools extension for Visual Studio
-- C# language
-- .NET Framework 4.6.2 (only for plug-in or custom workflow activity development)
+- .NET Framework 4.6.2 is required for plug-in or custom workflow activity development
 - Power Apps/Dataverse subscription or a trial environment
 
 ## Connect to your Dataverse environment

powerapps-docs/developer/data-platform/tools/devtools-create-project.md

@@ -2,7 +2,7 @@
 title: "Quickstart: Create a Power Platform Tools project | Microsoft Docs"
 description: "Learn how to start a new Visual Studio project for plug-in or custom workflow assembly development using Power Platform Tools."
 ms.custom: ""
-ms.date: 06/20/2020
+ms.date: 01/27/2023
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -23,10 +23,10 @@ Like any Visual Studio solution, you begin by creating a new project. In the new
 
 ## Prerequisites
 
-- Visual Studio 2019
+- Visual Studio 2019 or 2022
 - Power Platform Tools for Visual Studio
 - C# language
-- .NET Framework 4.6.2 (only for plug-in or custom workflow activity development)
+- .NET Framework 4.6.2 or greater - (plug-in and custom workflow activity development requires v4.6.2)
 - Power Apps/Dataverse subscription or a trial environment
 - Windows Workflow Foundation (only for custom workflow activity development)
 
@@ -61,7 +61,7 @@ The easy way to create a Power Platform solution containing a CrmPackage project
 
 1. In the Visual Studio new project dialog, search for and choose **Power Platform Solution Template** and then select **Next**.
 
-1. Enter the requested project information, choose .NET Framework 4.6.2 or 4.7.2, and select **Create**. <p/>At this point you should see either a Dataverse login dialog or a dialog to reuse your last Dataverse connection. Do whatever is appropriate to connect to your Dataverse development environment. Never develop code in a production environment.
+1. Enter the requested project information, choose a .NET Framework version, and select **Create**. <p/>At this point you should see either a Dataverse login dialog or a dialog to reuse your last Dataverse connection. Do whatever is appropriate to connect to your Dataverse development environment. Never develop code in a production environment.
 
 1. At the **Configure Microsoft Power Platform Solution** dialog, choose either to use an existing Dataverse solution or create a new solution. <p/>Depending on what you have chosen, you will either be prompted to enter information about the new solution or select the existing solution from a drop-down list. **Step #3 Select Solution** is displayed but won't be active until you are logged in and choose **Next** in step #2.
 
@@ -85,7 +85,7 @@ Only projects created with a Power Platform Tools template should be added to a
 
 1. Select one of the installed Power Platform Tools templates and select **Next**.
 
-1. Fill in any required information and select **Create**. For a plug-in or workflow activity library, be sure to choose .NET Framework 4.6.2 (or 4.7.2).
+1. Fill in any required information and select **Create**. For a plug-in or workflow activity library, be sure to choose .NET Framework 4.6.2.
 
 ### Add an existing project to a Power Platform solution
 

powerapps-docs/developer/data-platform/tools/devtools-install.md

@@ -2,7 +2,7 @@
 title: "Install Power Platform Tools | Microsoft Docs"
 description: "Learn how to install the Power Platform Tools extension for Visual Studio."
 ms.custom: ""
-ms.date: 06/20/2022
+ms.date: 01/27/2023
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -30,7 +30,7 @@ Power Platform Tools for Visual Studio supports the rapid creation, debugging, a
 
 Before installing Power Platform Tools into Visual Studio you must have the following applications and frameworks installed on your development computer:
 
-- Microsoft Visual Studio 2019.
+- Microsoft Visual Studio 2019 or 2022.
 
 - .NET Framework 4.6.2 (required only for plug-in and workflow activity development)
 
@@ -82,6 +82,7 @@ You can find a few Power Platform Tools options in Visual Studio by choosing **T
 ### See Also
 
 [Quickstart: Create a Power Platform Tools project](devtools-create-project.md)  
-[Power Platform Tools on the Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatformTools)
+[Power Platform Tools extension for Visual Studio 2019](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatformTools)  
+[Power Platform Tools extension for Visual Studio 2022](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatformToolsVS2022)
 
 [!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/virtual-entities/get-started-ve.md

@@ -64,7 +64,7 @@ Following are the limitations in virtual tables that must be considered.
     - A column on a virtual table cannot be calculated or rollup.  Any desired calculations must be done on the external side, possibly within or directed by the data provider.
     - Although you can add virtual table columns as a lookup on a grid or other UI views, you cannot filter or sort based on this virtual table lookup column.
 - Auditing is not supported.
-- Search functionality is not support for virtual tables as they do not persist data.
+- Search functionality is not supported for virtual tables as they do not persist data.
 - Charts and dashboards are not supported for virtual tables.
 - Virtual tables cannot be enabled for queues.
 - Offline caching of values is not supported for virtual tables.

powerapps-docs/developer/model-driven-apps/best-practices/business-logic/index.md

@@ -1,6 +1,6 @@
 ---
-title: "Developers: Best practices and guidance of client side scripting for model-driven apps | Microsoft Docs"
-description: Best practices and guidance of client side scripting for developers of model-driven apps in Power Apps.
+title: "Developers: Best practices and guidance for client-side scripting for model-driven apps | Microsoft Docs"
+description: Best practices and guidance for client-side scripting for developers of model-driven apps in Power Apps.
 suite: powerapps
 author: adrianorth
 ms.author: aorth
@@ -19,9 +19,9 @@ contributors:
   - caburk
 ---
 
-# Best practices and guidance of client side scripting for model-driven apps
+# Best practices and guidance for client-side scripting for model-driven apps
 
-This list below contains all of the Best practices and guidance of client side scripting for model-driven apps.
+This list below contains all of the Best practices and guidance for client-side scripting for model-driven apps.
 
 [!INCLUDE[cc-terminology](../../../data-platform/includes/cc-terminology.md)]
 
@@ -37,4 +37,4 @@ This list below contains all of the Best practices and guidance of client side s
 [Apply business logic using client scripting](../../client-scripting.md) <br />
 
 
-[!INCLUDE[footer-include](../../../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/model-driven-apps/clientapi/create-app-side-panes.md

@@ -3,8 +3,7 @@ title: "Creating side panes by using a client API in model-driven apps"
 description: Learn how to create side panes in model-driven apps by using a client API.
 author: adrianorth
 ms.author: aorth
-
-ms.date: 04/17/2022
+ms.date: 01/27/2023
 ms.reviewer: jdaly
 ms.subservice: mda-developer
 ms.topic: "article"
@@ -127,6 +126,6 @@ By switching to use `createPane`, both limitations can be avoid by providing an
 
 ### Related topics
 
-[sidePanes (Client API reference)](reference/xrm-app-sidepanes.md)
-
-[loadPanel (Client API Reference)](reference/xrm-panel/loadpanel.md)
+[sidePanes (Client API reference)](reference/xrm-app-sidepanes.md)<br />
+[loadPanel (Client API Reference)](reference/xrm-panel/loadpanel.md)<br />
+[Walkthrough: Write your first client script](walkthrough-write-your-first-client-script.md)

powerapps-docs/maker/TOC.yml

@@ -1665,32 +1665,32 @@
     href: ../developer/model-driven-apps/overview.md
   - name: Glossary of terms
     href: ./model-driven-apps/model-driven-app-glossary.md    
-- name: Power Apps mobile  
+- name: Power Apps mobile app  
   items:
-  - name: Install Power Apps mobile
+  - name: Install the Power Apps mobile app
     href: ../mobile/run-powerapps-on-mobile.md
   - name: Manage your mobile app with Microsoft Intune
     href: ../mobile/intune.md
-  - name: Use model-driven apps on Power Apps mobile
+  - name: Set the appearance of your app to dark or light mode
+    href: ../mobile/display-mode.md
+  - name: Use model-driven apps in the Power Apps mobile app
     href: ../mobile/use-custom-model-driven-app-on-mobile.md
-  - name: Use Dataverse search on Power Apps mobile  
+  - name: Use Dataverse search for model-driven apps in the Power Apps mobile app
     href: ../mobile/relevance-search-mobile.md  
-  - name: Set app display to dark or light mode  
-    href: ../mobile/display-mode.md
-  - name: In-app notifications in Power Apps mobile
+  - name: In-app notifications in the Power Apps mobile app
     href: ../mobile/mobile-notifications.md
-  - name: Create push notifications for Power Apps mobile
+  - name: Create push notifications for the Power Apps mobile app
     href: ../mobile/power-apps-mobile-notification.md
-  - name: Use deep links with Power Apps mobile
+  - name: Use deep links with the Power Apps mobile app
     href: ../mobile/mobile-deep-links.md
-  - name: Open an app in Power Apps mobile by scanning a QR code
+  - name: Open an app in the Power Apps mobile app by scanning a QR code
     href: ../mobile/scan-QR-code.md
-  - name: Switch to a different tenant on Power Apps mobile
+  - name: Switch to a different tenant in the Power Apps mobile app
     href: ../mobile/tenant-switcher.md
-  - name: Troubleshoot issues for Power Apps mobile
+  - name: Troubleshoot issues in the Power Apps mobile app
     href: ../mobile/powerapps-mobile-troubleshoot.md
     items:
-    - name: Prevent canvas app restarts on Power Apps mobile
+    - name: Prevent canvas app restarts in the Power Apps mobile app
       href: ../mobile/power-apps-mobile-canvas-app-restarts.md
   - name: Mobile offline for model-driven apps
     items:
@@ -2118,9 +2118,9 @@
     - name: How-to guides for extending portals
       items:
         - name: Embed portal in another website
-          href: ./portals/embed-portal-website.md
+          href: /power-pages/configure/embed-website
         - name: Set up Azure Front Door with portals
-          href: ./portals/azure-front-door.md
+          href: /power-pages/configure/azure-front-door
     - name: For developers
       items:
         - name: Work with Liquid templates

powerapps-docs/maker/canvas-apps/embed-apps-dev.md

@@ -25,7 +25,8 @@ In this topic, we'll show you how to set parameters for app embedding; then we'l
 ![Power BI dashboard with embedded app.](./media/embed-apps-dev/embed-dashboard.png)
 
 > [!NOTE]
-> Only Power Apps users in the same tenant can access the embedded app.
+> - Only Power Apps users in the same tenant can access the embedded app.
+> - Embedding canvas apps in a native desktop application isn't supported. This excludes first-party integrations such as Power Apps in Teams).
 
 You can also integrate canvas apps into SharePoint Online without using an iframe. More information: [Use the Power Apps web part](https://support.office.com/article/use-the-powerapps-web-part-6285f05e-e441-408a-99d7-aa688195cd1c).
 
@@ -97,4 +98,4 @@ Keep the following points in mind for authenticating users of your app:
 As you can see, embedding apps is simple and powerful. Embedding enables you to bring apps right to the places you and your customers work – websites, Power BI dashboards, SharePoint pages, and more.
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/portals/admin/clear-server-side-cache.md

@@ -47,8 +47,6 @@ The server-side cache is deleted, and data is reloaded from Dataverse.
 
 ![Clear portal cache with capacity-based license.](media/clear-server-side-cache/clear-config-capacity-license.png)
 
-To learn more about the differences between Power Apps portals and portal add-ons, read [Power Apps portals, Dynamics 365 portals and add-on portals](../overview.md#power-apps-portals-dynamics-365-portals-and-add-on-portals).
-
 Portal metadata is stored in tables called *configuration tables*. If you change configuration tables using the *Unified Interface application*, you **must** select **Clear config** to clear the configuration cache for changes to reflect in your Portal.  
 
 ### List of configuration tables refreshed when you clear config
@@ -220,7 +218,7 @@ Clearing the server-side configuration cache for a portal includes refreshing th
 
 Power Apps portals with version 9.2.6.x or later benefit from improved caching functionality to increase consistency and reliability as follows.
 
-- [Capacity-based portals and add-on portals](../overview.md#power-apps-portals-dynamics-365-portals-and-add-on-portals) will use the same caching functionality.
+- Capacity-based portals and add-on portals will use the same caching functionality.
 - Add-on portals with high load will have improved performance and a reliable data cache refresh.
 
 > [!IMPORTANT]