![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 93%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAN%3C/text%3E%3C/svg%3E)
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,262 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 70%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Like @MarkKromer-8019 mentioned, ADF is primarily designed for data pipelines in mind. While Logic Apps do seem similar (workflow/pipeline, connectors, triggers, etc.), its better suited for business workflows with lesser amounts of data being moved/processed.
Logic Apps also have significant data limits which don't make them the ideal choice when working with enormous amounts of data. But its specialty lies in the rich integrations that it provides with its large library of connectors from sending emails, notifications, etc. to integrating other workflows like approvals or even triggering an ADF run itself. ADF on the other hand is great for moving/processing substantial amounts of data.
This difference is also seen in how each service is charged for differently with Logic Apps focusing on the number of connector action/trigger executions and ADF focusing on the amount of data being work on for longer periods of time.
The choice on which to use would heavily depend on the scenario at hand and it could also be useful to consider a combined approach with ADF, Logic Apps and other services like Functions too.