Highlight
Here is long-overdue and my promised top 20 Azure Logic Apps tips & tricks
I’ve been building logic apps for what it feels foerver, I think it’s 8 year now, which is almost as long as I’ve been using Azure, almost…
I’ve often been asked to create my top tips & tricks for this great integration service, so here are my top 20+ tips for Logic App service. This has been updated for 2025 changes as well!
Before you start
I would advise everyone to check my post where I outline updates for logic apps in the last 15 months, so up until Match 2025. This post can be found here.
This list isn’t exhastive, but it’s a collection of updates that I’ve found most interesting and most impactful for our day-2-day work.
Mini-series
Here are my top tips for Azure Logic Apps service
- Build Git Integraiton for Standard Logic Apps - replicate behavior similar to Azure Data Factory - so develop in the portal, and sync your code back to Azure DevOps repo
- Triggers and Actions vary between SKUs - when migrating logic apps from consumption to standard SKU, so from Azure connectors to In-App connectors you might find ourself in a difficult situation, so here is what you should be aware of
- Disable Workflows when doing CICD - did you know you can disable Logic App Standard workflows before even deploying them? This could be very useful to ensure you won’t start triggering them before rest of the app is still deploying
- Watch out for In-App vs Azure connector costs - In-App and Azure connectors are priced differently compared to Consumption logic apps, make sure to remember about it
- Watch out for In-App vs Azure connector networking - similarly, networking between these two connectors is different, so in this tip I’ll explain the key difference and why it matters
- Watch out for the ‘effect of scale’ - private networking costs, and let me tell you it’s not cheap
- Find underutilized Logic Apps - Underutilized logic apps might cause governance headache, in this post I’ll covery why and how to get rid of them
- Storage Accounts can’t be shared - When implementing Logic Apps at scale, you might want to know if you can share their state on centrally shared storage account
- SQL db can’t be shared, but… - SQL Database can be used to store logic app state, but should it be? Is there any advantage over storage accounts?
- HTTP connectors to the rescue - What to do when there is no connector, or it doesn’t support your actions? Logic Apps HTTP connector is usually the solution
- Parallelization & retries matter - By default logic apps parallize and retry actions, read here why is it important from my perspective
- Exporting Consumption Workflows - When moving over, or just deploying to a higher environment, it’s good to know how can you export your logic app workflows
- Hide your storage! :) - Hide what? Yea, so this one is a bit less about technical adoption, and more about realistic approach to Azure governance
- Replicate Try-Catch-Finally flow - Try/Catch/Finally has been staple of any object oriented programming for many years, in this post, did you know you can also do it in Logic Apps?
- Find Orphaned API connections - Re-authenticating from the logic app designer is a nightmare for management of logic apps at scale, in this post I’ll explain why and how to clean this situation
- Personal Account is an issue - Connections, connections, connections, if not orphaned, then using an incorrect account. Here is why you shouldn’t do it, and what you should use
- Entra ID Authentication for HTTP connectors without API Management - If you look at blog posts they will suggest to use APIM to provide entra ID authentication for your HTTP REST endpoint workflows, but there is a cheaper way
- Hide secrets in your workflows - Reaching to key vault for a secret? Getting a access token manually? Operating on PII data? Yea, it will be visible in your Logic App logs, so you need to hide it!
- TF AzureRM is not supported for Standard SKU - Did you find an odd error when deploying Logic Apps Standard from Terraform AzureRM provider? Did MS support reply this isn’t supported? We did too, and I’ve reached out to a Product Team to find out more
- Retries cost - If you build pipelines and expect failures, ensure to configure retries appropierately, or you will pay for it
- Polling costs - Are you using one of those “check every X seconds” triggers? Yea, this will cost you… `
Next Actions
Here are some recommendations from me on what you can check out next if you want to learn mores
