Merge pull request #235774 from ecfan/assemblies

Azure Logic Apps: Updates about .NET assembly support

Author: prmerger-automator[bot]

articles/logic-apps/logic-apps-enterprise-integration-maps.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 04/18/2023
+ms.date: 04/25/2023
 ---
 
 # Add maps for transformations in workflows with Azure Logic Apps
@@ -62,7 +62,7 @@ This article shows how to add a map to your integration account. If you're worki
 
   * Standard workflows
 
-    * References to external assemblies from maps are currently in preview. To configure support for external assemblies, see [.NET Framework assembly support for XSLT transformations added to Azure Logic Apps (Standard)](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/net-framework-assembly-support-added-to-azure-logic-apps/ba-p/3669120).
+    * To configure support for external assemblies, see [.NET Framework assembly support for XSLT transformations added to Azure Logic Apps (Standard)](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/net-framework-assembly-support-added-to-azure-logic-apps/ba-p/3669120).
 
     * No limits apply to map file sizes.
 

articles/logic-apps/logic-apps-enterprise-integration-transform.md

@@ -7,7 +7,7 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/23/2022
+ms.date: 04/25/2023
 ---
 
 # Transform XML in workflows with Azure Logic Apps
@@ -30,37 +30,33 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
 
   * Exists in the same location or Azure region as your logic app resource where you plan to use the **Transform XML** action.
 
-  * If you're using the [**Logic App (Consumption)** resource type](logic-apps-overview.md#resource-environment-differences), your integration account requires the following items:
+  * If you're working on a [Consumption logic app resource and workflow](logic-apps-overview.md#resource-environment-differences), your integration account requires the following items:
 
     * The [map](logic-apps-enterprise-integration-maps.md) to use for transforming XML content.
 
     * A [link to your logic app resource](logic-apps-enterprise-integration-create-integration-account.md#link-account).
 
-  * If you're using the [**Logic App (Standard)** resource type](logic-apps-overview.md#resource-environment-differences), you don't store maps in your integration account. Instead, you can [directly add maps to your logic app resource](logic-apps-enterprise-integration-maps.md) using either the Azure portal or Visual Studio Code. Only XSLT 1.0 is currently supported. You can then use these maps across multiple workflows within the *same logic app resource*.
+  * If you're working on a [Standard logic app resource and workflow](logic-apps-overview.md#resource-environment-differences), you don't store maps in your integration account. Instead, you can [directly add maps to your logic app resource](logic-apps-enterprise-integration-maps.md) using either the Azure portal or Visual Studio Code. Only XSLT 1.0 is currently supported. You can then use these maps across multiple workflows within the *same logic app resource*.
 
     You still need an integration account to store other artifacts, such as partners, agreements, and certificates, along with using the [AS2](logic-apps-enterprise-integration-as2.md), [X12](logic-apps-enterprise-integration-x12.md), and [EDIFACT](logic-apps-enterprise-integration-edifact.md) operations. However, you don't need to link your logic app resource to your integration account, so the linking capability doesn't exist. Your integration account still has to meet other requirements, such as using the same Azure subscription and existing in the same location as your logic app resource.
 
-    > [!NOTE]
-    > Currently, only the **Logic App (Consumption)** resource type supports [RosettaNet](logic-apps-enterprise-integration-rosettanet.md) operations. 
-    > The **Logic App (Standard)** resource type doesn't include [RosettaNet](logic-apps-enterprise-integration-rosettanet.md) operations.
-
 ## Add Transform XML action
 
-1. In the [Azure portal](https://portal.azure.com), open your logic app and workflow in designer view.
+1. In the [Azure portal](https://portal.azure.com), open your logic app resource and workflow in designer view.
 
-1. If you have a blank logic app that doesn't have a trigger, add any trigger you want. This example uses the Request trigger. Otherwise, continue to the next step.
+1. If you have a blank workflow that doesn't have a trigger, add any trigger you want. This example uses the Request trigger. Otherwise, continue to the next step.
 
    To add the Request trigger, in the designer search box, enter `HTTP request`, and select the Request trigger named **When an HTTP request is received**.
 
 1. Under the step in your workflow where you want to add the **Transform XML** action, choose one of the following steps:
 
-   For a Consumption or ISE plan-based logic app, choose a step:
+   For a Consumption or ISE-based logic app workflow, choose a step:
 
    * To add the **Transform XML** action at the end of your workflow, select **New step**.
 
    * To add the **Transform XML** action between existing steps, move your pointer over the arrow that connects those steps so that the plus sign (**+**) appears. Select that plus sign, and then select **Add an action**.
 
-   For a Standard plan-based logic app, choose a step:
+   For a Standard-based logic app workflow, choose a step:
 
    * To add the **Transform XML** action at the end of your workflow, select the plus sign (**+**), and then select **Add an action**.
 
@@ -72,11 +68,11 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
 
    The dynamic content list shows property tokens that represent the outputs from the previous steps in the workflow. If the list doesn't show an expected property, check the trigger or action heading in the list and whether you can select **See more**.
 
-   For a Consumption or ISE plan-based logic app, the designer looks like this example:
+   For a Consumption or ISE-based logic app workflow, the designer looks like this example:
 
    ![Screenshot showing multi-tenant designer with opened dynamic content list, cursor in "Content" box, and opened dynamic content list.](./media/logic-apps-enterprise-integration-transform/open-dynamic-content-list-multi-tenant.png)
 
-   For a Standard plan-based logic app, the designer looks like this example:
+   For a Standard logic app workflow, the designer looks like this example:
 
    ![Screenshot showing single-tenant designer with opened dynamic content list, cursor in "Content" box, and opened dynamic content list](./media/logic-apps-enterprise-integration-transform/open-dynamic-content-list-single-tenant.png)
 
@@ -103,7 +99,7 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
 
 ### Reference assembly or custom code from maps
 
-In **Logic App (Consumption)** workflows, the **Transform XML** action supports maps that reference an external assembly. For more information, review [Add XSLT maps for workflows in Azure Logic Apps](logic-apps-enterprise-integration-maps.md#add-assembly).
+The **Transform XML** action supports maps that reference an external assembly. For more information, review [Add XSLT maps for workflows in Azure Logic Apps](logic-apps-enterprise-integration-maps.md#add-assembly).
 
 ### Byte order mark