Merge branch 'main' into hub-page

Author: tapanm-MSFT

.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

@@ -1,7 +1,7 @@
 ---
 title: "Use optional parameters (Microsoft Dataverse) | Microsoft Docs" 
 description: "Use optional parameters to control operation behaviors" 
-ms.date: 05/27/2023
+ms.date: 06/28/2023
 ms.reviewer: jdaly
 ms.topic: article
 author: divkamath
@@ -222,6 +222,9 @@ More information:
 
 Use the `tag` parameter to include a shared variable value that is accessible within a plug-in. This extra information allows a plug-in to apply logic that depends on the client application.
 
+> [!NOTE]
+> This parameter is intended for client applications to be able to set any value they wish. No Microsoft feature should require that you set a specific value in your client application code to enable different behaviors.
+
 To access the value in a plug-in, use the [IExecutionContext.SharedVariables collection](xref:Microsoft.Xrm.Sdk.IExecutionContext.SharedVariables)
 
 ```csharp

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

@@ -290,7 +290,7 @@ Target = account
 };
 
 //The existing entity is updated.
-var response2 = (UpsertResponse)svc.Execute(request1);
+var response2 = (UpsertResponse)svc.Execute(request2);
 Console.WriteLine("Record Created: {0}", response2.RecordCreated); //false
 ```
 

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

@@ -1,7 +1,7 @@
 ---
 title: "Azure aware custom plug-in (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This sample plug-in can post the pipeline execution context to the Azure Service Bus." # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 04/03/2022
+ms.date: 06/19/2023
 author: jaredha
 ms.author: jaredha
 ms.reviewer: jdaly
@@ -20,10 +20,18 @@ The plug-in demonstrates how to obtain the execution context and the tracing ser
 ## How to run this sample
 
 1. Download or clone the [Samples](https://github.com/Microsoft/PowerApps-Samples) repo so that you have a local copy.
-2. Open the sample solution in Visual Studio and sign the assembly with a key.
-3. Register the plug-in using the **Plugin Registration Tool**.
+1. Open the `Azureplugin.sln` solution file located at `PowerApps-Samples\dataverse\orgsvc\C#\Azureplugin` with Visual Studio.
+1. Sign the assembly with a key.
+1. Register the plug-in using the **Plugin Registration Tool**.
 
 > [!NOTE]
 > This sample requires a service endpoint to be created first, and its ID passed to the plug-in constructor through the unsecure configuration parameter when the plug-in step is registered.
 
+More information:
+
+[Write a custom Azure-aware plug-in](../../write-custom-azure-aware-plugin.md)  
+[Register a plug-in](../../register-plug-in.md)
+
+
+
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]