Merge branch 'main' into pnghub-patch-3

Author: JimDaly

.openpublishing.redirection.json

@@ -1,5 +1,15 @@
 {
   "redirections": [
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/enhanced-quick-start.md",
+      "redirect_url": "get-started-dynamics-365-web-api-csharp",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/start-web-api-project-visual-studio-csharp.md",
+      "redirect_url": "get-started-dynamics-365-web-api-csharp",
+      "redirect_document_id": "false"
+   },
    {
       "source_path": "powerapps-docs/developer/data-platform/org-service/azure-storage-partitioning-sdk.md",
       "redirect_url": "../elastic-tables",

powerapps-docs/developer/data-platform/media/disable-step-prt.png

@@ -31,8 +31,6 @@ One of the most fundamental concepts behind many of the challenges faced here is
 A common reason that problems can occur in this area is the lack of awareness of how customizations can affect transactions.
 
 Although the details of how this is done is beyond the scope of this topic, the most simple element to consider is that as Dataverse interacts with data in its database. SQL Server determines the appropriate locks to be taken by transactions on that data such as:
-- When retrieving a particular record, SQL Server takes a read lock on that record.
-- When retrieving a range of records, in some scenarios it can take a read lock on that range of records or the entire table.
 - When creating a record, it generates a write lock against that record.
 - When updating a record, it takes a write lock against the record.
 - When a lock is taken against a table or record, it’s also taken against any corresponding index records.

powerapps-docs/developer/data-platform/media/dv_plugin_registration_tool.png

@@ -12,10 +12,6 @@
       href: quick-start-console-app-csharp.md
     - name: 'Quick Start: Blazor Server sample (C#)'
       href: quick-start-blazor-server-app.md
-    - name: Enhanced quick start (C#)
-      href: enhanced-quick-start.md
-    - name: Start Web API project in Visual Studio
-      href: start-web-api-project-visual-studio-csharp.md
 - name: Web service authentication
   href: authenticate-web-api.md
 - name: Types and operations

powerapps-docs/developer/data-platform/media/enable-step-prt.png

@@ -1,7 +1,7 @@
 ---
-title: "Get started with Microsoft Dataverse Web API (C#) (Dataverse)| Microsoft Docs"
-description: "Learn how to access the Microsoft Dataverse Web API using the Microsoft Visual C# programming language"
-ms.date: 04/06/2022
+title: "Get started with Dataverse Web API (C#) (Dataverse)| Microsoft Docs"
+description: "Learn how to access the Dataverse Web API using the Microsoft Visual C# programming language."
+ms.date: 06/22/2023
 author: divkamath
 ms.author: dikamath
 ms.reviewer: jdaly
@@ -10,21 +10,25 @@ search.audienceType:
 contributors: 
   - JimDaly
 ---
-# Get started with Microsoft Dataverse Web API (C#)
+# Get started with the Dataverse Web API (C#)
 
-This section shows you how to access the Dataverse Web API using the C# programming language. The first topic, [Quick Start: Web API sample (C#)](quick-start-console-app-csharp.md), provides the quickest example of how to accomplish this, as all source code is simplified and provided in one file. The rest of this section shows you how to create and configure Visual Studio projects that use the Dataverse Web API to perform common business data operations.  
-  
-After completing this guide, you will have learned enough to explore the many other business operations that are supported by the Dataverse Web API.   You will also have a better understanding about how the [Web API Samples (C#)](web-api-samples-csharp.md) are structured.  
+This section introduces some simple ways start accessing the Dataverse Web API using the C# programming language.
+
+- [Quick Start: Web API sample (C#)](quick-start-console-app-csharp.md), provides the quickest example of how to access data, as all source code is simplified and provided in one file.
+- [Quickstart: Blazor Server Web API sample (C#)](quick-start-blazor-server-app.md) shows how to create a web application that can connect to Dataverse and retrieve data using the Web API.
+
+
+To learn more, please explore the [Web API Samples (C#)](web-api-samples-csharp.md).
 
 ## In this section
 
-[Quick Start: Web API sample](quick-start-console-app-csharp.md)  (Do this first)  
-[Enhanced quick start](enhanced-quick-start.md)  (Do this next)  
-[Start a Dataverse Web API project in Visual Studio](start-web-api-project-visual-studio-csharp.md)
+[Quick Start: Web API sample](quick-start-console-app-csharp.md)  
+[Quickstart: Blazor Server Web API sample (C#)](quick-start-blazor-server-app.md)
 
 ### See also
 
-[Perform operations using the Web API](perform-operations-web-api.md)<br />
-[Web API Samples (C#)](web-api-samples-csharp.md)
+[Perform operations using the Web API](perform-operations-web-api.md)  
+[Web API Samples (C#)](web-api-samples-csharp.md)  
+[Set up a Postman environment](setup-postman-environment.md)
 
 [!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/register-plug-in.md

@@ -11,93 +11,93 @@ search.audienceType:
 ---
 # Quickstart: Blazor Server Web API sample (C#)
 
-In this quickstart, you'll create a Blazor Server application to connect to your Microsoft Dataverse environment using the Web API.
+In this quickstart, you create a Blazor Server application to connect to your Microsoft Dataverse environment using the Web API.
 
-You'll authenticate and use <xref:System.Net.Http.HttpClient> to send a `GET` request containing the [WhoAmI Function](xref:Microsoft.Dynamics.CRM.WhoAmI). The response will be a [WhoAmIResponse ComplexType ](xref:Microsoft.Dynamics.CRM.WhoAmIResponse). After call completion, the `WhoAmIResponse` properties are displayed.
+You authenticate and use <xref:System.Net.Http.HttpClient> to send a `GET` request containing the [WhoAmI Function](xref:Microsoft.Dynamics.CRM.WhoAmI). The response is a [WhoAmIResponse ComplexType ](xref:Microsoft.Dynamics.CRM.WhoAmIResponse). After call completion, the `WhoAmIResponse` properties are displayed.
 
 > [!NOTE]
 > This is a very simple example to show how to get connected with a minimum of code.
 
 ## Prerequisites
 
 - Visual Studio 2022 with the **ASP.NET and web development** workload.
-- [.NET 7.0 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/7.0)
-- Familiarity with the Microsoft Azure portal
-- Internet connection
-- Valid user account for a Dataverse instance
-- Administrator access to grant application registrations
-- URL to the Dataverse environment you want to connect with
-- Basic understanding of the Visual C# language
+- [.NET 7.0 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/7.0).
+- Familiarity with the Microsoft Azure portal.
+- Internet connection.
+- Valid user account for a Dataverse instance.
+- Administrator access to grant application registrations.
+- URL to the Dataverse environment you want to connect with.
+- Basic understanding of the Visual C# language.
 
 
 > [!NOTE]
 > To authenticate you must have an app registered in Azure Active Directory. The registration will happen automatically as part of the template creation, but will require additional updates in the Azure portal.
 
 ## Create a Visual Studio project
 
-1. Open Visual Studio 2022 and click **Create a new project**.
+1. Open Visual Studio 2022 and select **Create a new project**.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-1.png" alt-text="Open Visual Studio 2022":::
 
-1. In the **Create a new project** dialog, search for *Blazor Server App*. Select the template and click **Next**.
+1. In the **Create a new project** dialog, search for *Blazor Server App*. Select the template and select **Next**.
 
     :::image type="content" source="../media/quick-start-blazor-server-app-csharp-2.png" alt-text="Create a new project":::
 
-1. In the **Configure your new project** dialog, set the **Project name**, and **Location**. Then click **Next**.
+1. In the **Configure your new project** dialog, set the **Project name**, and **Location**. Then select **Next**.
 
     :::image type="content" source="../media/quick-start-blazor-server-app-csharp-2.5.png" alt-text="Enter project name and ___location":::
 
-   In this example we will use **DataverseWebApiBlazorServerQuickStart** as the **Project name**.
+   In this example, we'll use **DataverseWebApiBlazorServerQuickStart** as the **Project name**.
 
-1. In the **Additional information** dialog specify **Framework** and **Authentication type**.
+1. In the **Additional information** dialog, specify **Framework** and **Authentication type**.
 
-   In this example the Framework is **.NET 7.0 (Standard Term Support)**
+   In this example, the Framework is **.NET 7.0 (Standard Term Support)**.
 
    > [!IMPORTANT]
-   > Set the **Authentication type** to **Microsoft identity platform**
+   > Set the **Authentication type** to **Microsoft identity platform**.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-3.png" alt-text="Set the Authentication type to Microsoft identity platform":::
 
-1. Click **Create** to create the project.
-1. The project template opens a **Required components** dialog. Click **Next**.
+1. Select **Create** to create the project.
+1. The project template opens a **Required components** dialog. Select **Next**.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-4.png" alt-text="Required components":::
 
 1. In the **Microsoft identity platform** dialog, make sure that the selected Azure account has permissions to manage applications in Azure AD and the selected tenant is the one associated with your Power Platform environment.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-5.png" alt-text="Microsoft identity platform dialog":::
 
-1. Click **Create new**.
-1. In the **Register an application** dialog, set the **Display name** and click **Register** to close the dialog.
+1. Select **Create new**.
+1. In the **Register an application** dialog, set the **Display name** and select **Register** to close the dialog.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-6.png" alt-text="Register an application":::
 
-   In this example we are using the name *Dataverse Web Api Blazor Server Quick Start*. We will search for the application using this name in a later step.
+   In this example, we're using the name *Dataverse Web Api Blazor Server Quick Start*. We'll search for the application using this name in a later step.
 
-1. Click **Next**.
+1. Select **Next**.
 
     > [!NOTE]
     > You don't need to do anything in this step.
 
-   This step provides capabilities to connect to Microsoft Graph or another API, but this isn't necessary for this quickstart.
+   This step provides capabilities to connect to Microsoft Graph or another API, but connecting to another API isn't necessary for this quickstart.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-6.5.png" alt-text="Additional settings step.":::
 
-1. Click **Next**. This step summarizes the changes that will be made to the project.
+1. Select **Next**. This step summarizes the changes that are made to the project.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-6.6.png" alt-text="Summary of changes":::
 
-1. Click **Finish**.
+1. Select **Finish**.
 
    The **Dependency configuration progress** dialog shows the automated steps performed by the template to register the application.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-7.png" alt-text="Dependency configuration progress":::
 
-1. Click **Close** to close the dialog.
+1. Select **Close** to close the dialog.
 
 ## Configure the application in Active Directory
 
-The Visual Studio template created a registered application using the information you provided. Connecting to Dataverse requires additional permissions.
+The Visual Studio template created a registered application using the information you provided. Connecting to Dataverse requires more permissions.
 
 1. From the [Power Platform admin center](https://admin.powerplatform.microsoft.com/home), select the **Azure Active Directory** admin center.
 
@@ -107,24 +107,24 @@ The Visual Studio template created a registered application using the informatio
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-9.png" alt-text="Search for the application registration":::
 
-1. Open the application and select **API permissions**. Click **Add a permission**.
+1. Open the application and select **API permissions**. Select **Add a permission**.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-10.png" alt-text="API permissions":::
 
 1. In the **Request API permissions** fly-out, select the **APIs my organization uses** tab and search for *Dataverse*.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-11.png" alt-text="search for Dataverse in APIs my organization uses":::
 
-1. Select **Dataverse**, and **Dynamics CRM API** will open.
-1. Select the `user_impersonation` delegated permission and click **Add permissions**.
+1. Select **Dataverse**, and **Dynamics CRM API** opens.
+1. Select the `user_impersonation` delegated permission and select **Add permissions**.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-12.png" alt-text="Add the user_impersonation delegated privilege":::
 
-1. Select **Certificates & secrets** and click **New client secret**.
+1. Select **Certificates & secrets** and select **New client secret**.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-13.png" alt-text="Certificates & secrets":::
 
-1. In the **Add a client secret** fly-out, enter a **Description** and **Expires** duration, then click **Add**.
+1. In the **Add a client secret** fly-out, enter a **Description** and **Expires** duration, then select **Add**.
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-14.png" alt-text="Add a client secret":::
 
@@ -157,17 +157,17 @@ The Visual Studio template created a registered application using the informatio
 
 ## Edit the app
 
-To enable calls to Dataverse you must edit three files in the application:
+To enable calls to Dataverse, you must edit three files in the application:
 
 - appsettings.json
 - Program.cs
 - Pages/FetchData.razor
 
 ### appsettings.json
 
-There are several places in the other files that require a reference to the base uri used to access the Dataverse Web API. Adding this to the `appsettings.json` allows you to set this in one place.
+There are several places in the other files that require a reference to the base uri used to access the Dataverse Web API. Adding this data to the `appsettings.json` allows you to set this data in one place.
 
-Add the following below `"AllowedHosts": "*"` where `<your org>` represents the base url to access the Dataverse Web API. If you are not sure what this is, see [Web API URL and versions](compose-http-requests-handle-errors.md#web-api-url-and-versions).
+Add the following below `"AllowedHosts": "*"` where `<your org>` represents the base url to access the Dataverse Web API. If you aren't sure what this is, see [Web API URL and versions](compose-http-requests-handle-errors.md#web-api-url-and-versions).
 
 ```json
   "AllowedHosts": "*",
@@ -204,14 +204,14 @@ Add the following below `"AllowedHosts": "*"` where `<your org>` represents the
        .EnableTokenAcquisitionToCallDownstreamApi(new string[] { $"{dataverseBaseUri}user_impersonation" })
        .AddInMemoryTokenCaches();
    ```
-   <!-- xref link was causing build errors -->
-   - The [MicrosoftIdentityWebApiAuthenticationBuilder.EnableTokenAcquisitionToCallDownstreamApi Method](/dotnet/api/microsoft.identity.web.microsoftidentitywebapiauthenticationbuilder.enabletokenacquisitiontocalldownstreamapi) adds support for the web app to acquire tokens to call an API. By passing the `user_impersonation` scope, the user is can consent to the capability to use the Dataverse Web API.
+ 
+   - The [MicrosoftIdentityWebApiAuthenticationBuilder.EnableTokenAcquisitionToCallDownstreamApi Method](/dotnet/api/microsoft.identity.web.microsoftidentitywebapiauthenticationbuilder.enabletokenacquisitiontocalldownstreamapi) adds support for the web app to acquire tokens to call an API. By passing the `user_impersonation` scope, the user can consent to the capability to use the Dataverse Web API.
    - [AddInMemoryTokenCaches Method](xref:Microsoft.Identity.Web.MicrosoftIdentityAppCallsWebApiAuthenticationBuilder.AddInMemoryTokenCaches%2A) Enables caching the token issued for requests.
 
 
 ### Pages/FetchData.razor
 
-The default `Pages/FetchData.razor` component retrieves some weather forecast data. We are going to replace this completely.
+The default `Pages/FetchData.razor` component retrieves some weather forecast data. We're going to replace this completely.
 
 Copy the following code and replace all the code in `Pages/FetchData.razor`:
 
@@ -319,14 +319,14 @@ else
 
 ## Run the program
 
-The application is now ready!
+The application is now ready.
 
 1. Press F5 to run the program. The first time the program runs you should see this consent dialog:
 
    :::image type="content" source="../media/quick-start-blazor-server-app-csharp-15.5.png" alt-text="Consent dialog":::
 
-1. Click **Accept**.
-1. Click **Fetch data**.
+1. Select **Accept**.
+1. Select **Fetch data**.
 
    The output should look like this:
 
@@ -336,6 +336,13 @@ The application is now ready!
 
 This quickstart shows a simple approach to create a Blazor Server web application that connects to data in Dataverse.
 
+Learn more about Dataverse Web API capabilities by understanding the service documents.
+
+> [!div class="nextstepaction"]
+> [Web API types and operations](web-api-types-operations.md)
+
+
+
 ### See Also
 
 [Tutorial: Create an ASP.NET Core Blazor WebAssembly App using Dataverse](../walkthrough-blazor-webassembly-single-tenant.md)<br />