A Step-by-Step Guide to Building a Standard Logic App Workflow in Azure
Please read the article “Azure Logic Apps: Simplifying Integration and Automating Workflows” before proceeding with the creation of a standard logic app.
Picture a world where mundane tasks are handled automatically, freeing you up to focus on more strategic initiatives. That’s the promise of Azure Standard Logic Apps, a powerful tool for automating workflows and streamlining operations.
Standard Logic Apps vs. Consumption Logic Apps
Standard Logic Apps offer several advantages over their Consumption Logic Apps counterparts:
- Dedicated resources: Unlike Consumption Logic Apps, which share resources with other users, Standard Logic Apps have dedicated resources, ensuring consistent performance and scalability.
- Enterprise-grade features: Standard Logic Apps come packed with enterprise-grade features, including high availability, hybrid connectivity, and seamless integration with Azure services.
Let’s build a simple Standard Logic App that retrieves data from a file in Azure Blob Storage in response to an incoming HTTP request.
Prerequisites:
- Azure account
- Azure Blob Storage account
Create a Standard logic app resource
Step 1 - Navigate to the Azure portal and log in.
Step 2 - Search for “Logic Apps” and select “Logic Apps”.
Step 3 - Click on “+ Add” and name your Logic App, for instance, “My-Standard-Logic-App”.
Step 4 - Choose your subscription and create a new resource group.
Step 5 - Select “Standard” as the hosting plan.
When you’re done, your settings look similar to the following example:
Step 6 - Review and click “Create”.
Step 7 - Once the deployment is complete, head to the resource page to start creating your workflow.
Add a blank workflow
After you create your empty logic app resource, you have to add your first workflow.
Step 1 - After Azure opens the resource, on your logic app resource menu, select “Workflows”. On the Workflows toolbar, select “Add”.
Step 2 - Name your workflow and choose between “Stateful“ or “Stateless“ state types in the New Workflow window. Then, click Create when finished.
Step 3 — From the workflow list, select the newly created workflow.
Step 4 — On the workflow menu, under “Developer“, select “Designer“.
Add a trigger
Step 1. Under “Triggers”, select “When an HTTP request is received” and specify the method as “GET.”
This trigger sets up an endpoint for receiving calls from other services or logic app workflows. It waits for incoming requests and seamlessly executes operations within the Azure Logic Apps
We can utilize the generated URL to activate this workflow through an HTTP request.
Add an actions
Step 1. Choose “Azure Blob Storage” as the connector: Select the action “Get blob content” to fetch data from the blob storage file.
Step 2. Configure Blob Storage Connection: Sign in to your Azure account if not signed in and provide details like Storage Account, Container, and Blob name to fetch the file’s content.
Sample.json
{
“id”: 1,
“name”: “John Doe”,
“email”: “john@example.com”,
“role”: “Engineer”
}
Step 3. Create HTTP Response: After fetching the file content, add a new action. Choose “Response” as the action to return the fetched data as an HTTP response.
Step 4. Save and Run the Logic App
Test the Logic App
Use tools like Postman or a web browser to send an HTTP request to the Logic App’s endpoint.
I’m currently using Postman to send an HTTP request to the Logic App’s endpoint. This will help us verify if we’re receiving the file data as a response.
This basic workflow outlines how to create a Standard Logic App that responds to an HTTP request by fetching data from Azure Blob Storage and sends that data as a response. Adjustments and additional actions can be made based on specific requirements and complexities of the workflow.
