Friday Fact: You can call other workflows in the same Logic App Standard — no HTTP request needed
May 1, 2026
Building a big, complex workflow in a single file There's a better way — and it's faster, cheaper, and cleaner than you might expect What's the
Logic Apps Best Practices, Tips, and Tricks: #51 Controlling the Initial State of a Logic Apps St...
Apr 30, 2026
When working with Azure Logic Apps Standard, one of the most common (and unpleasant) surprises happens right after deployment: Your workflows start running
Friday Fact: Stop Paying for Empty Logic App Consumption Executions
Apr 24, 2026
Imagine this scenario: you design a Logic App Consumption to process critical alerts or specific emails Everything works flawlessly, but when you check
Logic Apps Best Practices, Tips, and Tricks: #50 Controlling the Initial State of a Logic Apps Co...
Apr 22, 2026
Today, we'll cover a critical practice that every integration architect should understand: how to properly control the initial state of your Consumption Logic
Prototyping Your Frontend: How to Mock Responses in Azure API Management
Apr 21, 2026
Sometimes the best way to unblock your team is not to wait for a fully functional backend Whether you're validating a contract with a partner, letting
Friday Fact: The Hidden Retry Behavior That Makes Logic Apps Feel Stuck
Mar 27, 2026
If your Azure Logic App feels like it’s stuck in an endless loop… it probably isn’t You notice your workflow keeps retrying — sometimes dozens
Logic App Designer Fails with Can’t Start the Background Design‑Time Process
Mar 17, 2026
Today I was helping the team with a strange Logic app design issue, which meant I was back to my favorite topic: Errors, Warnings, Causes, and
Friday Fact: You can use Named Values to centralize configuration in Azure API Management
Mar 13, 2026
Why hardcoding APIM policies becomes a problem When working with Azure API Management (APIM), hardcoding values such as backend URLs, API keys, or
Friday Fact: Your APIM Policy Change Didn’t Do Anything — Because You Edited the Wrong Scope
Mar 6, 2026
It’s a classic scenario: you update your policy in Azure API Management, hit save, and test your API Nothing changed You test again, but the old behavior




