Merge branch 'main' into winona-screenshot-updates

w-azure · web-flow · commit 6b9f2ffea4ea · 2024-07-29T16:59:48.000-07:00
diff --git a/powerapps-docs/developer/data-platform/azure-integration.md b/powerapps-docs/developer/data-platform/azure-integration.md
diff --git a/powerapps-docs/developer/data-platform/configure-azure-integration.md b/powerapps-docs/developer/data-platform/configure-azure-integration.md
@@ -1,7 +1,7 @@
 ---
 title: "Configure Azure integration (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about configuring Azure integration with Microsoft Dataverse." # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 03/22/2022
+ms.date: 07/19/2024
 ms.reviewer: "pehecke"
 ms.topic: "article"
 author: "jaredha" # GitHub ID
@@ -18,19 +18,19 @@ You can post the message request data for the current Dataverse core operation t
 
 ## Configure Azure For Dataverse integration
 
-Because you will use SAS for authorization, you need to configure the rules and issuers of your Azure solution to allow a listener application to read the Dataverse message posted to the Azure Service Bus. In addition, you must configure the service bus rules to accept the Dataverse issuer claim. The recommended method to configure Azure is to use the Plug-in Registration tool (PRT).
+Because you'll use SAS for authorization, you need to configure the rules and issuers of your Azure solution to allow a listener application to read the Dataverse message posted to the Azure Service Bus. In addition, you must configure the service bus rules to accept the Dataverse issuer claim. The recommended method to configure Azure is to use the Plug-in Registration tool (PRT).
 
 For instructions on configuring authorization see [Tutorial: Configure Azure (SAS) for integration with Dataverse](walkthrough-configure-azure-sas-integration.md).
 
 ## Test Configuration
 
-After configuring Azure integration, you will need to perform these additional tasks.
+After configuring Azure integration, you'll need to perform these other tasks.
 
-1. Write and register a listener application with a Azure Service Bus solution endpoint. For more information, see the Azure Service Bus [documentation](/azure/service-bus-messaging/service-bus-messaging-overview).
-1. Register an Azure aware plug-in or a Azure-aware custom workflow activity with Dataverse. More information: [Tutorial: Register an Azure-aware plug-in using the Plug-in Registration tool](walkthrough-register-azure-aware-plug-in-using-plug-in-registration-tool.md)
+1. Write and register a listener application with an Azure Service Bus solution endpoint. For more information, see the Azure Service Bus [documentation](/azure/service-bus-messaging/service-bus-messaging-overview).
+1. Register an Azure aware plug-in or an Azure-aware custom workflow activity with Dataverse. More information: [Tutorial: Register an Azure-aware plug-in using the Plug-in Registration tool](walkthrough-register-azure-aware-plug-in-using-plug-in-registration-tool.md)
 1. Perform the necessary Dataverse operation that triggers the plug-in or custom workflow activity to run.
 
-If all of the preceding steps were performed correctly, a message containing the Dataverse data context should be sent to a Azure queue or topic and ultimately received by the listener application. You can navigate to the System Jobs grid in the Dataverse web application and check the status of the related System Job to see if the post to the Azure Service Bus succeeded. In case of errors, the message section of the System Job displays the error details.
+If all of the preceding steps were performed correctly, a message containing the Dataverse data context should be sent to an Azure queue or topic and ultimately received by the listener application. You can navigate to the System Jobs grid in the Power Apps web application, under **Advanced settings**, and check the status of the related system job to see if the post to the Azure Service Bus succeeded. If errors occur, the message section of the system job displays the error details.
 
 ### See also
 
@@ -40,5 +40,4 @@ If all of the preceding steps were performed correctly, a message containing the
 [Write a listener application for a Azure solution](write-listener-application-azure-solution.md)<br />
 [What is Azure Service Bus?](/azure/service-bus-messaging/service-bus-messaging-overview)
 
-
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/data-platform/transaction-currency-currency-entity.md b/powerapps-docs/developer/data-platform/transaction-currency-currency-entity.md
@@ -2,9 +2,8 @@
 title: "Transaction Currency (currency) table (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about transaction table, which is a multicurrency feature enabling users to perform financial transactions in multiple currencies. Multiple records in different transaction currencies can be aggregated, compared, or analyzed with regard to a single currency using the base currency." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 07/19/2021
+ms.date: 07/25/2024
 ms.reviewer: "pehecke"
-
 ms.topic: "article"
 author: "mayadumesh" # GitHub ID
 ms.subservice: dataverse-developer
@@ -32,7 +31,7 @@ Dataverse is a multicurrency system, in which each record can be associated with
   
 - Define product pricelists for each currency.  
   
-To use multiple currencies, the base currency must be defined for an organization during server installation and organization setup. After the base currency is set for an organization, it cannot be changed. This value is stored in the `Organization.BaseCurrencyID` attribute.  
+To use multiple currencies, the base currency must be defined for an organization during server installation and organization setup. This value is stored in the `Organization.BaseCurrencyID` attribute.  
   
 Transaction currencies are defined as a part of the system settings. An unlimited number of transaction currencies can be defined. Transaction currencies are related to the base currency with the definition of a currency exchange rate.  
   
diff --git a/powerapps-docs/developer/data-platform/work-data-azure-solution.md b/powerapps-docs/developer/data-platform/work-data-azure-solution.md
@@ -1,7 +1,7 @@
 ---
 title: "Work with Microsoft Dataverse data in your Azure solution (Microsoft Dataverse) | Microsoft Docs"
 description: "Provides an overview of passing data from Dataverse to an Azure cloud hosted solution."
-ms.date: 08/28/2023
+ms.date: 07/19/2024
 author: swylezol
 ms.author: swylezol
 ms.reviewer: pehecke
@@ -18,22 +18,19 @@ contributors:
 
 [!INCLUDE[cc-terminology](includes/cc-terminology.md)]
 
-An internal plug-in named `ServiceBusPlugin` is provided with Dataverse. The plug-in contains the business logic to post the Dataverse message execution context to the integrated Azure service. To use this plug-in, you need to register an Azure endpoint and a step for the plug-in. The step defines what message and table combination being processed by the core Dataverse operation should trigger the plug-in to execute. For more information, see [Walkthrough: Register an Azure-aware Plug-in using the Plug-in Registration Tool](walkthrough-register-azure-aware-plug-in-using-plug-in-registration-tool.md).  
+A default Azure-aware plug-in is provided with Dataverse. The plug-in contains the business logic to post the Dataverse message execution context to the Azure Service Bus. To use this plug-in, you need to register a service endpoint and a step. The step defines what message and table combination being processed by the core Dataverse operation should trigger the plug-in to execute. For more information, see [Walkthrough: Register an Azure-aware Plug-in using the Plug-in Registration Tool](walkthrough-register-azure-aware-plug-in-using-plug-in-registration-tool.md).  
   
-In addition, you can write a custom plug-in that includes the required lines of code to post to the Azure service. The plug-in is registered in a similar way, except that it must be registered in the sandbox. For more information on writing a custom plug-in that can post to the Azure services, see [Write a Custom Azure-aware Plug-in](write-custom-azure-aware-plugin.md).  
+In addition, you can write a custom plug-in that includes the required lines of code to post to the Azure service. The plug-in is registered in a similar way, except that it must be registered in the sandbox. For more information on writing a custom plug-in that can post to the Azure Service Bus, see [Write a Custom Azure-aware Plug-in](write-custom-azure-aware-plugin.md).  
   
 You can also write a custom workflow activity that can post the execution context to the Azure service and include this activity in your workflows. Sample code for a custom Azure-aware workflow activity is provided in the [Sample: Azure aware custom workflow activity](org-service/samples/azure-aware-custom-workflow-activity.md).
 
 > [!NOTE]
 > Any service endpoint registered for a synchronous step will send the execution context data to the Azure service immediately. If an error occurs after the request was sent, the data operation will rollback but the request sent the the Azure service cannot be recalled.
 
-
-  
 ### See also
 
 [Writing a Plug-in](write-plug-in.md)<br/>
-[Event execution pipeline](event-framework.md#event-execution-pipeline)<br/> 
+[Event execution pipeline](event-framework.md#event-execution-pipeline)<br/>
 [ServiceEndPoint Entity](reference/entities/serviceendpoint.md)<br/>
 
-
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/data-platform/write-custom-azure-aware-plugin.md b/powerapps-docs/developer/data-platform/write-custom-azure-aware-plugin.md
@@ -1,7 +1,7 @@
 ---
 title: "Write a custom Azure-aware plug-in (Microsoft Dataverse) | Microsoft Docs"
 description: "Learn how to write plug-in code that can post a message or the execution context of the current database transaction to the Azure Service Bus."
-ms.date: 06/19/2023
+ms.date: 07/19/2024
 author: divkamath
 ms.author: dikamath
 ms.reviewer: pehecke
@@ -21,17 +21,17 @@ Writing a plug-in that works with Azure is similar to writing any other Datavers
 
 ## Plug-in design considerations
 
-For a plug-in that executes synchronously, the recommended design is for the plug-in to send a message to Azure for the purpose of retrieving information from a listener application or other external service. Use of a two-way or REST contract on the Azure Service Bus endpoint allows a data string to be returned to the plug-in.  
+For a plug-in that executes synchronously, the recommended design is for the plug-in to send a message to Azure for retrieving information from a listener application or other external service. Use of a two-way or REST contract on the Azure Service Bus endpoint allows a data string to be returned to the plug-in.  
   
-It is not recommended that a synchronous plug-in use the Azure Service Bus to update data with an external service. Problems can arise if the external service becomes unavailable or if there is a lot of data to update. Synchronous plug-ins should execute fast and not hold up all logged in users of an organization while a lengthy operation is performed. In addition, if a rollback of the current core operation that invoked the plug-in occurs, any data changes made by the plug-in are undone. This could leave Dynamics 365 and an external service in an un-synchronized state.  
+It isn't recommended that a synchronous plug-in use the Azure Service Bus to update data with an external service. Problems can arise if the external service becomes unavailable or if there's much data to update. Synchronous plug-ins should execute fast and not hold up all logged in users of an organization while a lengthy operation is performed. In addition, if a rollback of the current core operation that invoked the plug-in occurs, any data changes made by the plug-in are undone. This rollback could leave Dataverse and an external service in an unsynchronized state.  
   
-Note that it is possible for synchronous registered plug-ins to post the current transaction's execution context to the Azure Service Bus.  
+It is possible for synchronous registered plug-ins to post the current transaction's execution context to the Azure Service Bus.  
   
 <a name="bkmk_writing"></a>
   
 ## Write the plug-in code
 
-In the following sample plug-in code has been added to obtain the Azure service provider and initiate posting the execution context to the Service Bus by calling <xref:Microsoft.Xrm.Sdk.IServiceEndpointNotificationService.Execute(Microsoft.Xrm.Sdk.EntityReference,Microsoft.Xrm.Sdk.IExecutionContext)>. Tracing code has been added to facilitate debugging of the plug-in because the plug-in must run in the sandbox.  
+In the following sample plug-in, code has been added to obtain the Azure service provider and initiate posting the execution context to the Service Bus by calling <xref:Microsoft.Xrm.Sdk.IServiceEndpointNotificationService.Execute(Microsoft.Xrm.Sdk.EntityReference,Microsoft.Xrm.Sdk.IExecutionContext)>. Tracing code has been added to facilitate debugging of the plug-in because the plug-in must run in the sandbox.  
 
 > [!NOTE]
 > The `serviceEndpointId` passed into the constructor in this code is the one you get from creating a service endpoint as described in [Walkthrough: Configure Azure (SAS) for integration with Dataverse](walkthrough-configure-azure-sas-integration.md)
@@ -115,12 +115,12 @@ In your plug-in code, you can update the writeable data in the context before in
 
 ## Plug-in registration
 
-There are a few restrictions when you register a Azure-aware custom plug-in. The plug-in must be registered to execute in the sandbox. Because of this, the plug-in is limited to calling <xref:Microsoft.Xrm.Sdk.IOrganizationService> methods, Azure solution methods, or accessing a network using a web client. No other external access, such as access to a local file system, is allowed.  
+There are a few restrictions when you register an Azure-aware custom plug-in. The plug-in must be registered to execute in the sandbox. Sandbox registration limits the plug-in to calling <xref:Microsoft.Xrm.Sdk.IOrganizationService> methods, Azure solution methods, or accessing a network using a web client. No other external access, such as access to a local file system, is allowed.  
   
-For a plug-in registered to execute in asynchronous mode, this also means that the order of plug-in execution compared to other asynchronous plug-ins is not guaranteed. In addition, asynchronous plug-ins always execute after the Dynamics 365 core operation.  
+For a plug-in registered to execute in asynchronous mode, the order of plug-in execution compared to other asynchronous plug-ins isn't guaranteed. In addition, asynchronous plug-ins always execute after the Dataverse core operation.  
   
 <a name="bkmk_failure"></a>
- 
+
 ## Handle a failed Service Bus post
 
 The expected behavior from a failed Service Bus post is dependent on whether the plug-in was registered for synchronous or asynchronous execution. For asynchronous plug-ins, the system job that actually posts the execution context to the service bus will retry the post. For a synchronous registered plug-in, an exception is returned. More information [Management and Notification of Run-time Errors](azure-integration.md)  
@@ -132,8 +132,8 @@ For a plug-in registered to execute asynchronously, the <xref:Microsoft.Xrm.Sdk.
   
 ### See also
 
-[Azure extensions for Dynamics 365](azure-integration.md)  
-[Send Dynamics 365 data over the Microsoft Azure Service Bus](work-data-azure-solution.md)  
+[Azure integration](azure-integration.md)  
+[Work with Microsoft Dataverse data in your Azure solution](work-data-azure-solution.md)  
 [Sample: Azure aware custom plug-in](org-service/samples/azure-aware-custom-plugin.md)  
 [Write a plug-In](write-plug-in.md)  
 [Event execution pipeline](event-framework.md)  
diff --git a/powerapps-docs/maker/data-platform/azure-synapse-incremental-updates.md b/powerapps-docs/maker/data-platform/azure-synapse-incremental-updates.md
@@ -2,7 +2,7 @@
 title: "Query and analyze the incremental updates | MicrosoftDocs"
 description: "Learn how to query and analyze the incremental updates made to Microsoft Dataverse data during a user-specified time interval with Power Apps and Azure Synapse Analytics"
 ms.custom: ""
-ms.date: 02/07/2023
+ms.date: 07/29/2024
 ms.reviewer: "matp"
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -51,7 +51,7 @@ Azure Synapse Link for Dataverse. This guide assumes that you have already met t
    :::image type="content" source="media/azure-synapse-add-tables-settings.png" alt-text="Add tables settings":::
 
 > [!NOTE]
-> The minimum time interval is 15 minutes. That means the incremental update folder will be created every 15 minutes and contain the changes that occurred within the time interval. This setting is also configurable after the link creation via **Manage tables**
+> The minimum time interval is five minutes. That means the incremental update folder is created every five minutes and contain the changes that occurred within the time interval. This setting is also configurable after the link creation via **Manage tables**
 >
 > Ensure **Connect to your Azure Synapse workspace Azure Synapse workspace** is not checked in the first page of setup.
 
diff --git a/powerapps-docs/maker/data-platform/azure-synapse-link-delta-lake.md b/powerapps-docs/maker/data-platform/azure-synapse-link-delta-lake.md
@@ -6,7 +6,7 @@ ms.author: jasonhuang
 ms.reviewer: matp
 ms.service: powerapps
 ms.topic: how-to
-ms.date: 06/18/2024
+ms.date: 07/29/2024
 ms.custom: template-how-to
 ---
 # Export Dataverse data in Delta Lake format
@@ -59,7 +59,7 @@ When setting up an Azure Synapse Link for Dataverse, you can enable the **export
 - Dataverse: You must have the Dataverse **system administrator** security role. Additionally, tables you want to export via Azure Synapse Link must have the **Track changes** property enabled. More information: [Advanced options](create-edit-entities-portal.md#advanced-options)
 - Azure Data Lake Storage Gen2: You must have an Azure Data Lake Storage Gen2 account and **Owner** and **Storage Blob Data Contributor** role access. Your storage account must enable **Hierarchical namespace** and **public network access** for both initial setup and delta sync. **Allow storage account key access** is required only for the initial setup.  
 - Synapse workspace: You must have a Synapse workspace and **Owner** role in access control(IAM) and the **Synapse Administrator** role access within the Synapse Studio. The Synapse workspace must be in the same region as your Azure Data Lake Storage Gen2 account. The storage account must be added as a linked service within the Synapse Studio. To create a Synapse workspace, go to [Creating a Synapse workspace](/azure/synapse-analytics/get-started-create-workspace).
-- A Spark Pool in the connected Azure Synapse workspace with **Apache Spark Version 3.3** using this [recommended Spark Pool configuration](#recommended-spark-pool-configuration). For information about how to create a Spark Pool, go to [Create new Apache Spark pool](/azure/synapse-analytics/quickstart-create-apache-spark-pool-portal#create-new-apache-spark-pool).
+- An Apache Spark pool in the connected Azure Synapse workspace with **Apache Spark Version 3.3** using this [recommended Spark Pool configuration](#recommended-spark-pool-configuration). For information about how to create a Spark Pool, go to [Create new Apache Spark pool](/azure/synapse-analytics/quickstart-create-apache-spark-pool-portal#create-new-apache-spark-pool).
 - The Microsoft Dynamics 365 minimum version requirement to use this feature is 9.2.22082. More information: [Opt in to early access updates](/power-platform/admin/opt-in-early-access-updates#how-to-enableearly-access-updates)
 
 ### Recommended Spark Pool configuration
@@ -75,6 +75,9 @@ This configuration can be considered a bootstrap step for average use cases.
 - Dynamically allocate executors: Enabled
 - Default number of executors: 1 to 9
 
+> [!IMPORTANT]
+> Use the Spark pool exclusively for Delta Lake conversation operation with Synapse Link for Dataverse. For optimal reliability and performance, avoid running other Spark jobs using the same Spark pool.
+
 ## Connect Dataverse to Synapse workspace and export data in Delta Lake format
 
 1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select the environment you want.
diff --git a/powerapps-docs/maker/data-platform/data-retention-faq.yml b/powerapps-docs/maker/data-platform/data-retention-faq.yml
diff --git a/powerapps-docs/maker/data-platform/types-of-fields.md b/powerapps-docs/maker/data-platform/types-of-fields.md
