If you’ve used Microsoft Flow before, you’ll feel right at home working inside a Logic App. That said, while there’s a lot of similarities (Flow itself is built on top of Logic Apps), there’s still several core differences, and reasons why you might elect to use Azure Logic Apps over Microsoft Flow to implement no-code and low-code process automation.
While Flow is intended to be used by business users and offers a more self-service and user-specific workflow experience, Logic Apps are really designed for IT Pros. Logic Apps run as event and/or timer-based process within your Azure environment, meaning they’re not necessarily tied to a specific user. Logic Apps offer more advanced integration and lifecycle management capabilities, including the ability to leverage Azure Resource Management and source control.
For these reasons, you may choose to use a Logic App over Flow for scenarios that span across the organization, are scoped to a wider number of users, or have the mission criticality that justifies deeper testing, source control, and deployment techniques.
In this guide, we’ll create a basic Logic App that leverages ElasticOCR to OCR files added to OneDrive for Business. This guide is intended to show the mechanics of creating and rolling out your first Logic App. Error handling has been omitted for the sake of simplicity. If you don’t currently have an ElasticOCR subscription, you can sign up for 30-day free trial to follow along with this guide.