You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/export-from-ise-to-standard-logic-app.md
+14-20Lines changed: 14 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,33 +9,34 @@ ms.date: 09/14/2022
9
9
#Customer intent: As a developer, I want to export one or more ISE workflows to a Standard workflow.
10
10
---
11
11
12
-
# Export logic app workflows from an ISE to a Standard logic app (Preview)
12
+
# Export ISE workflows to a Standard logic app (Preview)
13
13
14
14
> [!NOTE]
15
15
>
16
16
> This capability is in preview and is subject to the
17
17
> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
18
18
19
-
Standard logic app workflows that run in single-tenant Azure Logic Apps offer many new and improved capabilities. For example, you get compute isolation, virtual network integration, and private endpoints along with local development and debugging using Visual Studio Code, App Services Environment support, low latency with stateless workflows, and more.
19
+
Standard logic app workflows, which run in single-tenant Azure Logic Apps, offer many new and improved capabilities. For example, you get compute isolation, virtual network integration, and private endpoints along with App Services Environment hosting, local development and debugging using Visual Studio Code, low latency with stateless workflows, and more.
20
20
21
-
If you want the benefits from Standard workflows, but your workflows run in an Integration Service Environment (ISE), you can now replace your ISE with single-tenant Azure Logic Apps. This switch makes sense for most scenarios that require some ISE capabilities such as isolation and network integration, but not others, and can help reduce operation costs.
21
+
If you want the benefits from Standard workflows, but your workflows run in an Integration Service Environment (ISE), you can now replace your ISE with single-tenant Azure Logic Apps. This switch makes sense for most scenarios that require some ISE capabilities such as isolation and network integration, and can help lower operation costs.
22
22
23
-
You can now export logic apps from an ISE to Azure Logic Apps (Standard). With Visual Studio Code and the latest Azure Logic Apps (Standard) extension, you can export your logic apps as stateless workflows to a Standard logic app project. You can then locally update, test, and debug your workflows to get them ready for redeployment. When you're ready, you can deploy either directly from Visual Studio Code or through your own DevOps process.
23
+
You can now export logic app workflows from an ISE to a Standard logic app. Using Visual Studio Code and the latest Azure Logic Apps (Standard) extension, you export your logic apps as stateful workflows to a Standard logic app project. You can then locally update, test, and debug your workflows to get them ready for redeployment. When you're ready, you can deploy either directly from Visual Studio Code or through your own DevOps process.
24
24
25
25
> [!NOTE]
26
26
>
27
-
> The export capability doesn't migrate your workflows. Instead, this tool replicates artifacts, such as
28
-
> workflow definitions, connections, integration account artifacts, and others. Your source logic app
29
-
> resources, workflows, trigger history, run history, and other data stay intact.
27
+
> The export capability doesn't migrate your workflows. Instead, this tool replicates artifacts,
28
+
> such as workflow definitions, connections, integration account artifacts, and others. Your source
29
+
> logic app resources, workflows, trigger history, run history, and other data stay intact.
30
30
>
31
-
> You control the export process and your migration journey. You can test and validate your exported workflows
32
-
> on the destination platform to your satisfaction. You choose when to disable or delete your source logic apps.
31
+
> You control the export process and your migration journey. You can test and validate your
32
+
> exported workflows to your satisfaction with the destination environment. You choose when
33
+
> to disable or delete your source logic apps.
33
34
34
-
This article provides information about the export process and shows how to export your logic app workflows from an ISE to a local Standard logic app project.
35
+
This article provides information about the export process and shows how to export your logic app workflows from an ISE to a local Standard logic app project in Visual Studio Code.
35
36
36
37
## Known issues and limitations
37
38
38
-
- To run the export tool, you must be on the same network as your ISE. In other words, 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.
39
+
- 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.
39
40
40
41
- The following logic apps and scenarios are currently ineligible for export:
41
42
@@ -59,26 +60,19 @@ This article provides information about the export process and shows how to expo
- An existing ISE with the logic app workflows that you want to export.
74
68
75
-
- To include managed connections in your deployment, you'll need an existing resource group in Azure as the destination for where to put your exported workflows. This option is recommended only for non-production environments.
69
+
- To include managed connections in your deployment, you'll need an existing Azure resource group to organize your managed connections for deployment. This option is recommended only for non-production environments.
76
70
77
71
- 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).
78
72
79
73
## Group logic apps for export
80
74
81
-
With the Azure Logic Apps (Standard) extension, you can combine multiple ISE-hosted logic apps into a single Standard logic app project. In single-tenant Azure Logic Apps, one Standard logic app resource can have multiple workflows. This way, you can pre-validate your workflows so that you don't miss any dependencies when you select logic apps for export.
75
+
With the Azure Logic Apps (Standard) extension, you can combine multiple ISE-hosted 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.
82
76
83
77
Consider the following recommendations when you select logic apps for export:
0 commit comments