Blob to Email Attachment Delivery

Overview

This flow automates the last-mile delivery of files that back-end systems drop into Azure Blob Storage. Every morning it sweeps an outbound blob folder, attaches each file to an email, routes it to the right recipient using a Dataverse-backed distribution map, logs the delivery for audit, and archives the file to a sent folder so it is never re-sent.

Why it matters: reports and invoices generated by automated jobs still need to reach people. This flow closes that gap with no manual downloads, full audit logging, and tenant-portable configuration.

Ships Off (demo).

Use Case

A reporting job, billing system, or RPA process writes finished files (invoices, statements, reports) into an Azure Blob container, and those files must be emailed to the right customer or internal team. Instead of someone downloading and forwarding them, this flow delivers, logs, and archives them automatically on a daily schedule.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Link vs attach

For files over the mailbox attachment limit, replace the email with a SAS-link email (generate a time-limited link and send the URL).

Batch by recipient

Group files per recipient and send one email with multiple attachments instead of one email per file.

Routing rules

Add rows to the Blob Distribution Map table; no flow edit needed. Prefix matching is case-insensitive on text before the first hyphen.

Schedule / trigger

Change the recurrence, or convert to a blob-added trigger for near-real-time delivery.

Failure handling

Add a parallel failed branch on the email that logs Status = Failed and skips archive/delete so undelivered files retry next run.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

toUpper(first(split(item()?['DisplayName'], '-')))

if(empty(body('Filter_Recipient_Match')), variables('varDefaultRecipient'), first(body('Filter_Recipient_Match'))?['flowlibs_recipientemail'])

equals(item()?['IsFolder'], false)

concat(variables('varSentFolder'), '/', item()?['DisplayName'])