The Logic Apps Standard extension in VS Code provides a feature that allow customers to export workflows from Integration Services Environment (ISE) or Consumption SKUs to a Logic Apps Standard VS Code project.

This experience allows customers to group workflows that should be deployed together as Logic Apps Standard application, validates the workflows against the export logic – guaranteeing that workflows, once export, work successfully in the new platform, and generates a local VS Code project, allowing users to test the code locally before packaging them for deployment.

This tool is a core part of the strategy to migrate workflows off ISE, which is retiring on August 31, 2024, providing a way to export ISE workflows into Logic Apps Standard projects, allowing customers to plan their migration on their own terms.

For more details this export features, including a walkthrough and known issues, access the Microsoft Learn documentation for ISE or consumption.

What’s new in the Export Tool

Updated Converter List

The latest version of the Export Tool implemented a series of converters that will automatically replace actions based on Azure Connections to their Service Provider counterparts. The following is the list of converters implemented today:

• Azure API Management
• Azure Automation
• Azure Blob Storage
• Azure File Storage
• Azure Functions
• Azure Queue Storage
• Azure Table Storage
• Batch Operations
• DB2
• Event Grid Publisher
• Event Hubs
• File System
• Flat File
• FTP
• Integration Account
• Key Vault
• Liquid Operations
• MQ
• RosettaNet
• SAP
• Service Bus
• SFTP
• SMTP
• SQL Server
• Workflow Operations
• XML Operations

Custom Connector Export

Logic apps containing Custom Connector actions are now able to be exported. The exported workflow action will be converted to an HTTP action, with the endpoint parameterized. This allows the workflows to be exported and adds flexibility for the user to decide how that action will be configured.

Workflow Operations Export

One of the differences between consumption in standard is related how the workflow operations action works. While in consumption you could refer to any workflow in a subscription, with standard you are restricted to workflows in the same application. This would restrict how workflows with a “call child workflow” action could be exported. The export tool now handles this situation automatically, with the following rules:

• If a child workflow is part of the logic apps workflows selected to export, the tool will export that action as is.
• If a child workflow is not part of the logic apps workflows selected to export, the tool will export that action as an HTTP action, with the endpoint parameterized, so you can point to a different application.