Merge pull request #233095 from wsilveiranz/wsilveiranz-batch-action-changes

Azure Logic Apps: Doc updates for latest export tool version

Author: denrea

articles/logic-apps/export-from-consumption-to-standard-logic-app.md

@@ -36,21 +36,17 @@ This article provides information about the export process and shows how to expo
 
 ## Known issues and limitations
 
-- The following logic apps and scenarios are currently ineligible for export:
-
-  - Logic apps that use custom connectors
-  - Logic apps that use the Azure API Management connector
-
 - The export tool doesn't export any infrastructure information, such as integration account settings.
 
 - The export tool can export logic app workflows with triggers that have concurrency settings. However, single-tenant Azure Logic Apps ignores these settings.
 
 - Logic apps must exist in the same region if you want to export them within the same Standard logic app project.
 
-- For now, connectors deploy as their *managed* versions, which appear in the designer under the **Azure** tab. The export tool will have the capability to export connectors that have a built-in, service provider counterpart, when the latter gain parity with their Azure versions. The export tool automatically makes the conversion when Azure connector is available to export as a built-in, service provider connector.
-
 - By default, connection credentials aren't cloned from source logic app workflows. Before your logic app workflows can run, you'll have to reauthenticate these connections after export.
 
+- By default, if an Azure connector has a built-in connector version, the export tool automatically converts the Azure connector to the built-in connector. No option exists to opt out from this behavior.
+
+
 ## Exportable operation types
 
 | Operation | JSON type |
@@ -62,10 +58,18 @@ This article provides information about the export process and shows how to expo
 
 - One or more logic apps to deploy to the same subscription and Azure region, for example, East US 2.
 
-- Azure contributor subscription-level access to the subscription where the logic apps are currently deployed, not just resource group-level access.
+- Azure reader subscription-level access to the subscription where the logic apps are currently deployed.
+
+- Azure contributor resource group-level access, if you select the option for **Deploy managed connectors**.
+
 
 - Review and meet the requirements for [how to set up Visual Studio Code with the Azure Logic Apps (Standard) extension](create-single-tenant-workflows-visual-studio-code.md#prerequisites).
 
+> [!NOTE]
+> 
+  > Make sure to install version 2.0.16 or higher for the Azure Logic Apps (Standard) extension for Visual Studio Code. 
+  > Some conversion scenarios require the latest workflow designer, which is available starting with this version.
+
 ## Group logic apps for export
 
 With the Azure Logic Apps (Standard) extension, you can combine multiple Consumption logic app workflows into a single Standard logic app project. In single-tenant Azure Logic Apps, one Standard logic app resource can have multiple workflows. With this approach, you can pre-validate your workflows so that you don't miss any dependencies when you select logic apps for export.
@@ -167,6 +171,11 @@ Some exported logic app workflows require post-export remediation steps to run o
 
 If you export actions that depend on an integration account, you have to manually set up your Standard logic app with a reference link to the integration account that contains the required artifacts. For more information, review [Link integration account to a Standard logic app](logic-apps-enterprise-integration-create-integration-account.md#link-account).
 
+### Batch actions and settings
+
+If you export actions that use Batch actions with multiple configurations stored in an integration account, you have to manually configure your Batch actions with the correct values after export. For more information, review [Send, receive, and batch process messages in Azure Logic Apps](logic-apps-batch-process-send-receive-messages.md#create-batch-receiver).
+
+
 ## Project folder structure
 
 After the export process finishes, your Standard logic app project contains new folders and files alongside most others in a [typical Standard logic app project](create-single-tenant-workflows-visual-studio-code.md).

articles/logic-apps/export-from-ise-to-standard-logic-app.md

@@ -37,22 +37,15 @@ This article provides information about the export process and shows how to expo
 
 ## Known issues and limitations
 
-- To run the export tool, you must be on the same network as your ISE. So, if your ISE is internal, you have to run the export tool from a Visual Studio Code instance that can access your ISE through the internal network. Otherwise, you can't download the exported package or files.
-
-- The following logic apps and scenarios are currently ineligible for export:
-
-  - Consumption workflows in multi-tenant Azure Logic Apps
-  - Logic apps that use custom connectors
-  - Logic apps that use the Azure API Management connector
-  - Logic apps that use the Azure Functions connector
-
-- The export tool doesn't export any infrastructure information, such as virtual network dependencies or integration account settings.
+- The export tool doesn't export any infrastructure information, such as integration account settings.
 
 - The export tool can export logic app workflows with triggers that have concurrency settings. However, single-tenant Azure Logic Apps ignores these settings.
 
-- For now, connectors with the **ISE** label deploy as their *managed* versions, which appear in the designer under the **Azure** tab. The export tool will have the capability to export **ISE** connectors as built-in, service provider connectors when the latter gain parity with their ISE versions. The export tool automatically makes the conversion when an **ISE** connector is available to export as a built-in, service provider connector.
+- Logic apps must exist in the same region if you want to export them within the same Standard logic app project.
+
+- By default, connection credentials aren't cloned from source logic app workflows. Before your logic app workflows can run, you'll have to reauthenticate these connections after export.
 
-- Currently, connection credentials aren't cloned from source logic app workflows. Before your logic app workflows can run, you'll have to reauthenticate these connections after export.
+- By default, if an Azure connector has a built-in connector version, the export tool automatically converts the Azure connector to the built-in connector. No option exists to opt out from this behavior.
 
 ## Exportable operation types
 
@@ -63,13 +56,18 @@ This article provides information about the export process and shows how to expo
 
 ## Prerequisites
 
-- An existing ISE with the logic app workflows that you want to export.
+- One or more logic apps to deploy to the same subscription and Azure region, for example, East US 2.
 
-- Azure contributor subscription-level access to the ISE, not just resource group-level access.
+- Azure reader subscription-level access to the subscription where the logic apps are currently deployed.
 
-- To include and deploy managed connections in your workflows, you'll need an existing Azure resource group for deploying these connections. This option is recommended only for non-production environments.
+- Azure contributor resource group-level access, if Deploy managed connectors option is selected.
 
-- Review and meet the requirements for [how to set up Visual Studio Code with the Azure Logic Apps (Standard) extension](create-single-tenant-workflows-visual-studio-code.md#prerequisites).
+- Review and meet the requirements for [how to set up Visual Studio Code with the Azure Logic Apps (Standard) extension](create-single-tenant-workflows-visual-studio-code.md#prerequisites). 
+
+> [!NOTE]
+> 
+  > Make sure to install version 2.0.16 or higher for the Azure Logic Apps (Standard) extension for Visual Studio Code. 
+  > Some conversion scenarios require the latest workflow designer, which is available starting with this version.
 
 ## Group logic apps for export
 
@@ -171,6 +169,10 @@ Some exported logic app workflows require post-export remediation steps to run o
 
 If you export actions that depend on an integration account, you have to manually set up your Standard logic app with a reference link to the integration account that contains the required artifacts. For more information, review [Link integration account to a Standard logic app](logic-apps-enterprise-integration-create-integration-account.md#link-account).
 
+### Batch actions and settings
+
+If you export actions that use Batch actions with multiple configurations stored in an integration account, you have to manually configure your Batch actions with the correct values after export. For more information, review [Send, receive, and batch process messages in Azure Logic Apps](logic-apps-batch-process-send-receive-messages.md#create-batch-receiver).
+
 ## Project folder structure
 
 After the export process finishes, your Standard logic app project contains new folders and files alongside most others in a [typical Standard logic app project](create-single-tenant-workflows-visual-studio-code.md).