Event-Driven Automation

From Azure Blob Storage to Email in 3 Steps

Introduction

In modern cloud environments, automation is not a luxury — it is a necessity. One of the most common real-world requirements is: “Notify the team when a new file arrives.” This sounds simple, but doing it in a scalable, enterprise-grade way requires the right tools

.

In this article, I will show you how I built a fully automated notification workflow using Azure Logic Apps — step by step, with practical screenshots and real code.

Note for Power Platform users: Azure Logic Apps is the enterprise equivalent of Power Automate. Both share the same connector ecosystem. If you know one, you understand the other.

---

What We Are Building

New file uploaded to Azure Blob Storage
            ↓
    Logic App Trigger fires
            ↓
    HTTP POST to REST API
            ↓
  Automated Email Notification sent

A complete end-to-end automation — no manual steps, no polling, no scripts running on a server.

---

Prerequisites

• Azure Subscription (Pay-as-you-go works fine)

• Outlook or Office 365 account for email

• Basic understanding of Azure Portal

Cost: This demo costs only a few cents on Pay-as-you-go. Logic Apps Consumption plan charges per action execution.

---

Step 1: Create a Resource Group

First, organize everything under one Resource Group.

1. Go to portal.azure.com

2. Click “Resource Groups” → “+ Create”

3. Fill in:

   • Name: my-demo

   • Region: West Europe

4. Click “Review + Create” → “Create”

Best Practice: Always group related resources together. Makes cleanup, cost tracking, and access control much easier.

---

Step 2: Create Azure Storage Account

1. Click “+ Create a resource”

2. Search “Storage Account” → Click “Create”

3. Fill in:

   • Resource Group: my-demo

   • Name: uttamdemo2026

   • Region: West Europe

   • Performance: Standard

   • Redundancy: LRS (Locally Redundant Storage)

4. Click “Review + Create” → “Create”

---

Step 3: Create Blob Container

1. Open your Storage Account

2. Click “Containers” on the left menu

3. Click “+ Container”

4. Fill in:

   • Name: documents

   • Access level: Private

5. Click “Create”

Security Note: Always use Private access for production containers. Use SAS tokens or Managed Identity for access control.

---

Step 4: Create the Logic App

1. Click “+ Create a resource”

2. Search “Logic App” → Click “Create”

3. Fill in:

   • Resource Group: my-demo

   • Name: demo-blob-notification

   • Region: West Europe

   • Plan type: Consumption ← important for cost efficiency

4. Click “Review + Create” → “Create”

---

Step 5: Configure the Blob Storage Trigger

1. Open your Logic App

2. Click “Logic App Designer”

3. Click “Blank Logic App”

4. Search for “Azure Blob Storage”

5. Select trigger: “When a blob is added or modified (V2)”

6. Configure:

   • Connection name: blob-connection

   • Storage account: uttamdemo2026

   • Container: /documents

   • Interval: 1 Minute

---

Step 6: Add HTTP Action — Call a REST API

This step demonstrates API integration — a core DevOps skill.

1. Click “+ New Step”

2. Search “HTTP”

3. Select “HTTP” (Built-in)

4. Configure:

   • Method: POST

   • URI: https://jsonplaceholder.typicode.com/posts

   • Headers:

     • Key: Content-Type

     • Value: application/json

   • Body:

json

{
  "fileName": "@{triggerBody()?['Name']}",
  "message": "New file uploaded to Blob Storage",
  "uploadedAt": "@{utcNow()}"
}

Real World Usage: Replace the test URI with your actual Azure Function or API Management endpoint. This pattern is used for triggering downstream processes, logging events, or notifying microservices.

---

Step 7: Add Email Notification

1. Click “+ New Step”

2. Search “Outlook”

3. Select “Office 365 Outlook”

4. Select action: “Send an email (V2)”

5. Sign in with your Microsoft account

6. Configure:

   • To: your-email@domain.com

   • Subject:

   New file uploaded: @{triggerBody()?['Name']}

• Body:

   Hello,

   A new file has been uploaded to Blob Storage.

   File Name: @{triggerBody()?['Name']}
   Uploaded At: @{utcNow()}

   This is an automated notification.

   Regards,
   Uttam Chaturvedi
   DevOps Engineer

---

Step 8: Save and Publish

1. Click “Save”

2. Click “Publish”

3. Status should show “Active”

---

Step 9: Test the Workflow

1. Go to your Storage Account

2. Open the documents container

3. Click “Upload”

4. Upload any file — for example your CV or a test PDF

5. Wait 1-2 minutes

6. Check your inbox — you should receive the automated email!

---

Results

After uploading a file, the Logic App:

✅ Detected the new blob in under 1 minute
✅ Called the REST API with file metadata
✅ Sent an automated email with filename and timestamp
✅ Completed in 648 milliseconds

The Run History in Azure Portal shows every execution with status, duration, and input/output for each step — perfect for debugging and monitoring.

---

Why This Matters for DevOps

This simple demo demonstrates several important DevOps principles:

1. Event-Driven Architecture
React to events rather than polling. More efficient, more scalable.

2. API Integration
Connecting systems via REST APIs is at the heart of modern integration patterns.

3. Infrastructure as Code mindset
Logic Apps can be exported as ARM templates and deployed via CI/CD pipelines — making them fully automatable.

4. Monitoring built-in
Every run is logged automatically. No extra monitoring setup needed for the demo.

5. Security
Blob container is private. Connections use OAuth. No credentials hardcoded anywhere.

---

Logic Apps vs Power Automate — What is the Difference?

FeatureLogic AppsPower AutomateTarget audienceDevelopers / DevOpsBusiness usersHostingAzure PortalMicrosoft 365PricingPay per executionPer user licenseCI/CD supportFull ARM template supportLimitedCustom connectorsYesYesSame connectorsYesYes

Key insight: For enterprise DevOps scenarios, Logic Apps gives you more control, better CI/CD integration, and infrastructure-level governance. For business user automation, Power Automate is faster to get started.

---

Next Steps

You can extend this workflow to:

• Send to Microsoft Teams instead of email

• Write metadata to Azure SQL Database

• Trigger an Azure Function for processing

• Add approval gates before notification

• Deploy via Azure DevOps pipeline using ARM templates

---

Conclusion

In less than an hour, we built a production-ready automated notification system using Azure Logic Apps. This pattern is directly applicable to real enterprise scenarios — file processing, compliance notifications, audit trails, and more.

The same concept applies in Power Automate — if you understand Logic Apps, you understand Power Automate. The connectors, triggers, and actions work the same way.

Have questions or feedback? Connect with me on LinkedIn or visit my website.