Power BI Report Delivery Automation: From Attachments to Embedded Intelligence
ENTERPRISE • FINTECH

Enterprise Financial Client

Power BI Report Delivery Automation: From Attachments to Embedded Intelligence

When 34% of your BI reports are never read, the problem isn't the data — it's the delivery.

United StatesFinancial Services6 weeks2 engineers
162%
Increase in report consumption
34% → 89%
Reports actually read by recipients
3.8 days → 2.4hrs
Time from report to executive awareness
511%
First-year ROI

Overview

A financial services firm with 180 Power BI dashboards and a $185,000 annual BI investment found their executives weren't reading reports — not because they didn't care, but because opening a PDF attachment on a phone during a commute is friction nobody has time for. We built a hybrid automation pipeline that intercepts Power BI subscription emails, converts PDFs to high-resolution embedded visuals, and delivers rich HTML emails that work instantly on any device. Report engagement jumped from 34% to 89% in the first month.

The Challenge

Despite a significant investment in Power BI, the firm's actual report consumption rate was 34%. User research with 45 executives revealed the root cause: Power BI's native subscription emails deliver only a tiny thumbnail image and require recipients to download and open a PDF attachment. On mobile during a commute, this process takes 2-3 minutes and competes with 50 other emails. Executives weren't lazy — they were rational. The attachment friction was enough to push report review to 'later', which became never. The business impact was significant: average time from report generation to executive awareness was 3.8 business days, meaning critical operational indicators were routinely ignored for days.

The Solution: A Hybrid Automation Pipeline

We designed a five-component hybrid architecture that bridges cloud Power Automate with on-premises .NET processing — maintaining complete data sovereignty while leveraging the integration capabilities of the Power Platform. Power BI subscriptions are redirected to a processing mailbox. A Power Automate cloud flow detects incoming subscription emails and triggers a desktop flow to download PDF attachments to a monitored directory. A custom C# .NET 8 Windows Service (PDFProcessorService) uses FileSystemWatcher to detect new PDFs, renders each page at 300 DPI using PdfiumViewer, applies ImageSharp post-processing (sharpening, contrast enhancement), and outputs publication-ready PNG images. A second cloud flow then constructs branded HTML emails with images embedded as base64 — no attachments, no downloads, images visible instantly on any device.

The .NET Service: Engineering for Production

PDFProcessorService is the technical core of the solution. Built on .NET 8's BackgroundService pattern, it implements a ConcurrentQueue for job management, SQL Server-based distributed locking to prevent race conditions during peak morning distribution, structured logging via Serilog, and a Microsoft Teams webhook integration for processing alerts. Performance tuning was critical: initial PDF rendering took 45 seconds per page. Switching from PdfSharp to PdfiumViewer reduced this to 3.2 seconds per page. Adaptive DPI scaling (300 DPI for single-page, 150 DPI for 4+ pages) and intelligent JPEG compression reduced average email size from 25 MB to 4.2 MB — comfortably within Exchange limits while preserving visual quality.

Results That Changed Behavior

The transformation in executive behavior was immediate and measurable. Email open rates within 2 hours jumped from 42% to 89%. The VP of Operations, who previously ignored subscription emails on her commute due to PDF friction, now reviews the operations dashboard on her phone every morning and has sent pre-8AM intervention emails to her team based on data she saw. Supply chain standups — previously spent navigating PDFs on screen share — are now data-driven discussions because every team member arrives having already read the report. Time savings: 4,354 hours annually recovered across executive review, meeting efficiency, and administrative distribution. Payback period: 1.6 months.

Tech Stack

C# .NET 8Power AutomatePdfiumViewerImageSharpSQL ServerSharePointAzure FunctionsWindows Services

Results

Report consumption rate increased from 34% to 89% — 162% improvement

Executive report review time reduced from 8.5 to 2.1 minutes per report

Time from issue appearance in reports to corrective action: 1.9 days → 4.2 hours

4,354 hours of annual time savings valued at $354,800

Zero sensitive data left corporate network — all processing on-premises

99.7% system reliability over 6-month production period

I actually look forward to these reports now. I see the entire dashboard the moment I open the email on my phone. We've caught operational issues days earlier than we would have with the old system.

VP of Operations

Enterprise Financial Services Client

Ready to build something similar?

We bring the same engineering rigor and attention to detail to every project. Let's discuss yours.

Start a Conversation