Merge pull request #7624 from MicrosoftDocs/main

updating

Author: mduelae

.openpublishing.redirection.json

@@ -7240,16 +7240,6 @@
       "redirect_url": "powerapps-docs/maker/portals/admin/update-dynamics365-instance.md",
       "redirect_document_id": "false"
     },
-    {
-      "source_path": "powerapps-docs/user/cs-email-template-builder.md",
-      "redirect_url": "/dynamics365/customer-service/cs-email-template-builder",
-      "redirect_document_id": false
-    },
-    {
-      "source_path": "powerapps-docs/user/customize-insert-email-template.md",
-      "redirect_url": "/dynamics365/customer-service/customize-insert-email-template",
-      "redirect_document_id": "false"
-    },
     {
       "source_path": "powerapps-docs/teams/boards-architecture.md",
       "redirect_url": "https://github.com/microsoft/teams-powerapps-app-templates",

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/authenticate-office365-deprecation.md

@@ -2,7 +2,7 @@
 title: "Use of Office365 authentication with Microsoft Dataverse (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Describes deprecation of the WS-Trust security protocol and the code changes required in applications that use Office365 authentication."
 ms.custom: ""
-ms.date: 01/06/2022
+ms.date: 01/23/2023
 ms.reviewer: "pehecke"
 
 ms.topic: "article"
@@ -23,10 +23,7 @@ search.app:
 > Use of the WS-Trust (Office365) authentication security protocol when connecting to Microsoft Dataverse is no longer recommended and has been deprecated; see the [announcement](/power-platform/important-changes-coming#deprecation-of-office365-authentication-type-and-organizationserviceproxy-class-for-connecting-to-dataverse).<p/>
 > Additionally, the WS-Trust protocol does not support modern forms of multi-factor authentication and Azure AD Conditional Access controls to customer data.
 
-This document describes the impact to and required authentication code changes for custom client applications that use “Office365” authentication and the
-[Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy](/dotnet/api/microsoft.xrm.sdk.client.organizationserviceproxy) or
-[Microsoft.Xrm.Tooling.Connector.CrmServiceClient](/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient)
-classes. If your applications use this type of authentication protocol and API,
+This document describes the impact to and required authentication code changes for custom client applications that use “Office365” authentication and the <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy>, <xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient>, or <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient> classes. If your applications use this type of authentication protocol and API,
 continue reading below to learn more about the recommended authentication changes to be made to your application’s code.
 
 ## How do I know if my code or application is using WS-Trust?
@@ -37,11 +34,11 @@ workflow activities, or on-premises/IFD service connections.
 
 - If your code employs user account and password credentials for authentication with Dataverse or an application, you are likely using the WS-Trust security protocol. Some examples are shown below, though this list is not fully inclusive.
 
-  - When using the [CrmServiceClient](/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient) class with a connection string:
+  - When using the `CrmServiceClient` or `ServiceClient` class with a connection string:
 
     `connectionString="AuthType=Office365; Username=jsmith\@contoso.onmicrosoft.com;Password=passcode;Url=https://contoso.crm.dynamics.com"`
 
-  - When using [OrganizationServiceProxy](/dotnet/api/microsoft.xrm.sdk.client.organizationserviceproxy) class constructors:
+  - When using the `OrganizationServiceProxy` class constructors:
 
 ```csharp
 using (OrganizationServiceProxy organizationServiceProxy =
@@ -51,7 +48,7 @@ using (OrganizationServiceProxy organizationServiceProxy =
 
 - If your code uses the `OrganizationServiceProxy` class at all, you are using WS-Trust.
 
-- If your code is using [CrmServiceClient](/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient).`OrganizationServiceProxy`, you are using WS-Trust.
+- If your code is using <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient>.`OrganizationServiceProxy`, you are using WS-Trust.
 
 ## What should I do to fix my application code if affected?
 
@@ -61,19 +58,19 @@ the recommended connection interface for authentication with Dataverse.
 > [!IMPORTANT]
 > Keep your applications up to date with our latest client SDK API changes by downloading and using the latest available NuGet packages whenever possible.
 
-- If your code uses an [Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy](/dotnet/api/microsoft.xrm.sdk.client.organizationserviceproxy) instance:
+- If your code uses an <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy> instance:
 
-  If you are passing the `OrganizationServiceProxy` instance around to various methods, or returning the instance from a method, replace all occurrences of the type `OrganizationServiceProxy` with the [IOrganizationService](/dotnet/api/microsoft.xrm.sdk.iorganizationservice) interface. This interface exposes all the core methods used to communicate with Dataverse.
+  If you are passing the `OrganizationServiceProxy` instance around to various methods, or returning the instance from a method, replace all occurrences of the type `OrganizationServiceProxy` with the <xref:Microsoft.Xrm.Sdk.IOrganizationService> interface. This interface exposes all the core methods used to communicate with Dataverse.
 
-  When invoking the constructor, it is recommend you add the NuGet package [Microsoft.CrmSdk.XrmTooling.CoreAssembly](https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.CoreAssembly/) to your project and replace all use of `OrganizationServiceProxy` class constructors with [CrmServiceClient](/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient) class constructors. You will need to alter your coding pattern here, however, for simplicity `CrmServiceClient` supports connection strings in addition to complex constructors and the ability to provide external authentication handlers. `CrmServiceClient` implements `IOrganizationService`, therefore your new authentication code will be portable to the rest of your application code. You can find examples on the use of `CrmServiceClient` in the [PowerApps-Samples](https://github.com/microsoft/PowerApps-Samples/tree/master/dataverse/orgsvc/C%23) repository.
+  When invoking the constructor, it is recommend to replace all use of `OrganizationServiceProxy` class constructors with `CrmServiceClient` or `ServiceClient` class constructors. You will need to alter your coding pattern here, however, for simplicity `CrmServiceClient` and `ServiceClient` support connection strings in addition to complex constructors and the ability to provide external authentication handlers. The service client classes implements `IOrganizationService`, therefore your new authentication code will be portable to the rest of your application code. You can find examples on the use of service client calsses in the [PowerApps-Samples](https://github.com/microsoft/PowerApps-Samples/tree/master/dataverse/orgsvc/C%23) repository.
 
-- If your code is using [CrmServiceClient](/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient) with the “Office365” authentication type:
+- If your code is using <xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient>, or <xref:Microsoft.Xrm.Tooling.Connector.CrmServiceClient> classes with the “Office365” authentication type:
 
   An example of this is a connections string that looks like this:
 
   `connectionString = "AuthType=Office365;[email protected];Password=passcode;Url=https://contoso.crm.dynamics.com"`
 
-  Similarly, you could also be using a `CrmServiceClient` constructor and pass in `AuthType.Office365`.
+  Similarly, you could also be using a `CrmServiceClient` or `ServiceClient` constructor and pass in `AuthType.Office365`.
 
   - Switch over to using an OAuth based connection string. Such connection string looks like this:
 
@@ -89,7 +86,7 @@ the recommended connection interface for authentication with Dataverse.
 
 - If you are accessing the [CrmServiceClient](/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient).`OrganizationServiceProxy` property:
 
-  Remove all use of that property in your code. `CrmServiceClient` implements `IOrganizationService` and exposes everything that is settable for the organization service proxy.
+  Remove all use of that property in your code. `CrmServiceClient` and `ServiceClient` classes implement `IOrganizationService` and exposes everything that is settable for the organization service proxy.
 
 > [!IMPORTANT]
 > Regarding not being able to login using User ID/Password even if using OAuth: if your tenant and user is configured in Azure Active Directory for conditional access and/or Multi-Factor Authentication is required, you will not be able to use user ID/password flows in a non-interactive form at all. For those situations, you must use a Service Principal user to authenticate with Dataverse.<p/>

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)]