Azure Logic Apps now supports cloning existing Consumption Logic Apps into Standard workflows
Azure Logic Apps now supports cloning existing Consumption Logic Apps into Standard workflows. This feature simplifies migration by allowing you to reuse your existing workflows without starting from scratch. It’s designed to help organizations transition to the Standard model, which offers improved performance, flexibility, and advanced capabilities.
Why Does It Matter?
Migrating from Consumption to Standard has been a common challenge for teams looking to modernize their integration solutions. Standard workflows provide:
- Better performance through single-tenant architecture.
- Enhanced developer experience with local development and VS Code integration.
- Advanced features like built-in connectors, stateful/stateless workflows, and integration with Azure Functions.
This new cloning capability reduces friction, accelerates adoption, and ensures continuity for existing business processes. And with the announcement of Agent Loop Support in Logic Apps Consumption, the ability to clone agentic workflows to a Logic Apps Standard application allow you to have a graduation strategy for your agents.
Key Highlights
- Direct cloning: Convert an existing Consumption Logic App into a Standard workflow with minimal manual effort.
- Preserves workflow design: Your triggers, actions, and configurations are carried over.
- Supports modernization: Enables migration to a model that supports advanced features like custom connectors and private endpoints.
- Improved governance: Standard workflows allow better control over deployment and scaling.
How to Get Started
- Navigate to your Consumption Logic App in the Azure portal.
- Select Clone to Standard from the available options.
- Choose the target Logic App (Standard) environment and configure settings.
- Validate and deploy the cloned workflow.
Limitations
- Infrastructure settings aren’t cloned (e.g., integration account configurations).
- Connections and credentials must be reconfigured after cloning.
- Secure parameters aren’t copied; placeholders are created and need updating from Key Vault.
- Connectors default to shared even if built-in versions exist.
- Unsupported items include:
- Integration account references
- XML/Flat file transformations
- EDIFACT and X12 actions
- Nested workflows
- Azure Function calls
Learn more
To learn more about this new feature, check the official documentation on Microsoft Docs.
Microsoft