When working with Logic Apps Standard in Visual Studio Code, it’s important to note that deploying a workflow from one project can overwrite existing workflows in a Logic App. For instance, if you have Project A with a workflow already deployed on the Azure Portal, and then you deploy a workflow from Project B to the same Logic App, the workflow from Project A will be replaced by that from Project B—and not incremented!

The Reason
In Azure Logic Apps, each Logic App is treated as a single entity. When you deploy a workflow, it replaces the entire contents of the Logic App, including existing workflows. This design simplifies deployment and version control but limits flexibility, as it does not support adding individual workflows from different projects without overwriting the existing ones.

To avoid the issue of workflows replacing one another, you can manually copy multiple workflows into the same Logic App folder.


This approach allows you to keep all workflows accessible without overwriting any existing ones. Additionally, organizing workflows within a structured folder hierarchy in your project can help you manage them more effectively.

Since Visual Studio Code doesn’t currently support importing folders directly to your Logic App folder structure, this manual organization is essential for maintaining clarity and functionality across multiple projects.
Caution!
However, it’s crucial to note that when you copy workflows, you will need to realign connections, parameters, and any other related settings for each copied workflow to ensure they function correctly within the Logic App environment. Each workflow may have specific dependencies and configurations that need to be addressed after copying, as they will not automatically align with the existing project setup.

Best Approach
The best practice is to create all related workflows within a single project from the start!

Considerations
In Azure Logic Apps, if you make changes to any workflow within a project that contains multiple workflows, all workflows must be redeployed when you deploy the project. This is because each deployment triggers a host restart, during which all workflows are parsed and initialized. Consequently, even if you modify only one workflow, the deployment process impacts the entire Logic App, leading to downtime for all workflows.

To lazy to read? We’ve got you covered! Check out our video version of this content!
Hope you find this helpful! If you enjoyed the content or found it useful and wish to support our efforts to create more, you can contribute towards purchasing a Star Wars Lego for Sandro’s son!