Update export-from-ise-to-standard-logic-app.md

Updating known issues and pre-requisites

Author: wsilveiranz

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.
 
-- 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, 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 a Azure connector have a Service Provider connector available, the export tool will convert from Azure to Service provider connector automatically. There is no configuration to opt-out from this behavior.
 
 ## Exportable operation types
 
@@ -63,13 +56,17 @@ 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 reader subscription-level access to the subscription where the logic apps are currently deployed, not just resource group-level access.
 
-- Azure contributor subscription-level access to the ISE, not just resource group-level access.
+- Azure contributor resource group-level access, if Deploy managed connectors option is selected.
 
-- 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.
+- 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]
+> 
+> VS Code extension version 2.0.16 or higher is required, as some conversion scenarios will require the latest version of logic apps designer, available on this version.
 
 ## Group logic apps for export