Microsoft's low-code option for automating processes and joining up applications, data and services. Each workflow is drawn on a visual canvas: it starts when something happens, then performs steps using any of hundreds of ready-made connectors, and a step may hand work to Azure Functions.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Azure Logic Apps in context, with comparison tables and the common traps.
Terms in this definition
- Foundry workflows
Preview Foundry feature that orchestrates agents and logic in a fixed, declarative order, supporting variables, if/else branches and human-in-the-loop steps. Workflows are being retired on 1 December 2026 and Agent Framework replaces them.
- Authorisation levels
Key requirements for HTTP triggers in Azure Functions: Anonymous needs no key, Function accepts a function or host key, and Admin requires the master key.
Related terms
- Logic Apps SQL Server built-in triggers
Triggers built into the SQL Server connector of Standard Azure Logic Apps (When a row is inserted is one example). They check for changes using change tracking, whereas the managed connector's triggers look at a rowversion or identity column.
- SQL Server connector
Used in Power Automate and Azure Logic Apps, this connector talks to SQL Server, Azure SQL Managed Instance and Azure SQL Database. Triggers for new or changed rows rely on change tracking being enabled.