scheduling-with-azure-logic-apps-consumptionlisted

# Scheduling with Azure Logic Apps (Consumption tier) Lightweight recurring triggers on Azure. Consumption tier bills per action (~$0.000025), so a 5-minute schedule runs about 8,640 actions a month — about 22 cents. ## When to invoke - Adding a recurring HTTP trigger to your app (cache invalidation, heartbeat ping, recrawl tick) - A Microsoft consultant client has hit Power Automate's plan limits for a backend-only flow and you need to migrate it - Polling a SharePoint list / Teams channel / external API on a cadence - Anything that used to be a `cron` job on a VM and shouldn't need a VM ## When NOT to invoke - **Anything that needs user context.** Logic Apps Consumption can't sign in as the user. Power Automate is the right tool there. - **Long-running flows with many actions.** At 100k+ actions/month, switch to Logic Apps Standard (consumption-priced compute, but Workflow Standard plan). Standard is **not currently proven** in this skill pack — add it only when a real project uses it. - **Workflows requiring premium connectors.** Some connectors (Salesforce, SAP) carry a per-execution surcharge that changes the cost model. - **Sub-minute cadence.** Logic Apps minimum recurrence is 1 minute. For sub-minute, use Functions timer triggers or Container Apps. ## ⚠️ Cost warning — don't point a frequent scheduler at a DB-backed endpoint A recurring scheduler that hits an endpoint which queries a **SQL Serverless** database resets the DB's auto-pause timer on every run. At