Logic App Tips: Watch out for the 'effect of scale'

Highlight

When it comes to private networking there is a new element that must be considered when rolling out solutions at scale, and that is…

networking... uh...

Intro

if you look at deployment architecture of a logic apps in standard sku, with laid out mandatory private networking components it will look something like this.

What should be noted here

6 Private Endpoints
1. One for Web App
2. Second for Azure Blob Storage
3. Third for Azure Queue Storage
4. Forth for Azure Table Storage
5. Fifth for Azure File Storage
6. Sixth for Azure Data Lake File Service
Two of them are not required, and yet many companies provion these as part of teir TF/bicep modules, and those are
1. Private Endpoint for File Storage
2. Private Endpoint for Data Lake File Service
Storage is required always because logic app save their state their
Storage Accounts can’t be shared

So at minimum Logic App Standard requires 4 private endpoints, but I’ve seen many companies deploy all 6 because they do not understand logic app designarchitecture requirements, or 5 if they deploy blob instead of data lakes. Let’s use 5 for further calculations.

So how much a single logic app private endpoints will cost us in a month?

36 USD per month, for literally logic app just to exist. That might not blow our mind, but I was talking about the effect of scale.

For example, I currently manage a large data platform for my client, where we have 500+ solutions and many new are coming every day. We also have 3 environments, but I’ve seen some organizations with 6!

Let’s use smaller example with still large platform that has 160 solutions, each having logic app standard app and 3 environments?

Wooow… 207,000 USD yearly cost just to host these apps. This is a static cost, it will get higher if apps will start working. This is just cost of having logic apps on your platform.

So make sure to fight this and consider following tips