Pull from main

Author: Mattp123

powerapps-docs/developer/data-platform/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)]

powerapps-docs/developer/data-platform/configure-azure-integration.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.