Which approach incur less cost in the Azure Logic Apps (Standard Tier) - Azure Landing Zone Subscription.

Question

Earlier, we have 4 Logic Apps in Consumption Model which incurs minimal cost for hundreds of executions and connectors count per logic app might around 25 to 30.

Now, We are migrating to Azure Landing Zones Subscriptions (Private Network / Virtual Network).

Currently, the developers created 4 Logic Apps in Standard tier (Consumption model is not supported for Virtual Network). Each Logic App will have one workflow and that workflow may contains 20 (minimum) to 35 (maximum) connectors (combination of in-app and shared).

All these 4 Logic Apps are linked with Single App Service Plan i.e., WS1 vCPU - 3.5 GB Memory - 250 GB Remote Storage.

I'm unable to understand the cost calculation here:

Approach 1: Deployment of 4 separate logic apps

Approach 2: Deployment of multiple workflows in the single logic app

Here the logic apps tier is standard, deployed to be in virtual network, any workflow will run once in an hour i.e., 24 times a day for the duration of maximum 10 minutes/run ; no ISE or integration accounts used.

So, my doubt is

1. which approach is better?
2. which one to choose based on what factors?
3. which approach incur more cost?

Answer 1

Hi @Rajoli Hari Krishna Greetings! Thank you for posting this question here.

which approach incur more cost?

The cost of the hosting the Logics apps will be the same in both scenarios since they end up using a single App Service Plan (WS1) and sharing it. However, please see the below to see what factors to consider.

which one to choose based on what factors?

1. Performance and Resource Utilization: In approach 1, Each Logic App will consume resources independently. Whereas in the second approach, all the workflows share the same resources of the Single Logic App.
   • If you expect high resource utilization, you might benefit from isolating workflows across multiple Logic Apps (Approach 1).
   • If resource utilization is manageable within a single Logic App instance, consolidating workflows (Approach 2) could be more efficient.
2. Management and Maintenance:
   • Managing fewer Logic Apps (Approach 2) can simplify deployment, monitoring, and maintenance.
   • However, if you require clear separation and isolation between workflows for organizational or security reasons, Approach 1 might be more suitable.

Scalability:

• Approach 2 (multiple workflows in a single Logic App) might be easier to scale vertically by increasing the App Service Plan tier.
  • Approach 1 (separate Logic Apps) might offer better horizontal scalability by distributing the load across multiple Logic Apps.

If your workflows are complex and take longer run times, or if the frequency of the execution of the workflows is high, it may be better to deploy them in separate Logic Apps to avoid potential issues with concurrency and performance. You should also factor in the additional storage costs incurred by Logic app to store operation data. Considering the number of transactions is less, the difference in cost saved might not be substantial, but in general, is it advised to use Single Logic app to save on storage costs.

Considering that you have only 4 workflows that take 10 minutes run time are executed once an hour, you should be good to use a Single Logic app and build 4 workflows under it.

In addition to the above information, if you would like to get and compare the cost usage by resource, you can get it by running the Cost analysis by using Microsoft Cost Management and Billing and get a forecast of the resources to compare both approaches.

Hope this helps! Please let us know if you have any additional questions.

---

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.