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
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
Friday Fact: You can debug API policies in Azure API Management using Trace
Feb 27, 2026
When working with Azure API Management (APIM) policies, troubleshooting can feel like navigating a maze in the dark Complex inbound and outbound
Friday Fact: You can parameterize your Recurrence trigger using App Settings
Feb 20, 2026
Ever needed to change a Logic App execution time from 11:30 to 14:00 and thought: Wait do I really need to open Visual Studio, change the JSON, and/or run a
Fix “Functions:Worker:HostEndpoint” missing in Azure Functions (.NET Isolated)
Feb 16, 2026
Recently, I was trying to run an Azure Function locally in my Visual Studio 2020 environment, and while trying to run, I got the following error:
Friday Fact: Effortless migration with “Clone to Standard”
Feb 6, 2026
Historically, moving a workflow from an Azure Logic App (Consumption) to a Logic App (Standard) required manual effort, since it meant exporting templates,
Logic App Best Practices, Tips, and Tricks: #49 The Hidden 32-Character Naming Trap in Logic Apps...
Feb 3, 2026
When working with Azure Logic Apps (Standard), most of us focus on workflows, connectors, networking, and deployment pipelines Naming That usually feels like
Friday Fact: The “Empty Workflow” trap in Logic App Standard
Jan 30, 2026
When developing Azure Logic Apps (Standard) locally, we often create placeholders or new folders to organize our logic A common pitfall occurs when creating a
Friday Fact: “Run with payload” in the new Logic Apps designer enforces JSON only
Jan 23, 2026
When manually executing a workflow using Run with payload in the new Azure Logic Apps designer, the payload editor currently enforces JSON input and does not



