Real-Time PDF Report Generation on Power Pages: Replacing SSRS with Azure Function Apps for a US-Based Cybersecurity Firm

Summary

• A Houston-based cybersecurity firm eliminated report failures (~65%) by replacing SSRS with an Azure Function App pipeline.
• Dynamics 365 bound action ensured authentication stayed internal, bypassing Defender-related token failures.
• Integrated Power Pages, Power Automate, Dynamics 365, and Azure Functions for real-time PDF generation.
• Report generation time reduced from 3–8 minutes to under 15 seconds with zero infrastructure overhead.

Table of Contents

• 1. About the Customer
• 2. The Challenge
• 3. The Solution
• 4. Technical Implementation
• 5. Business Impact
• 6. FAQs
• 7. Conclusion

The client is a technology consulting and cybersecurity services firm based in Houston, Texas. They manage multiple concurrent client engagements using Dynamics 365 Project Operations as their core platform.

Project managers and clients access live project data through a customer-facing portal built on Microsoft Power Pages.

The organization needed one-click downloadable Project Status Reports from their Power Pages portal covering risks, issues, logs, and timelines.

Their SSRS-based solution failed frequently due to authentication breakdowns caused by Microsoft Defender for Cloud Apps across multiple service boundaries.

Key pain points:

1. Silent authentication failures with no clear errors
2. Retry delays of 60–90 seconds per attempt
3. Separate SSRS infrastructure dependency
4. Slow report customization cycle

Project managers avoided generating reports during live meetings due to reliability concerns.

At Cloudfronts, while working on this project, I replaced the SSRS pipeline entirely with a synchronous, serverless architecture that keeps the authentication context inside the Dynamics 365 service layer.

Technologies Used:

1. Dynamics 365 Project Operations
2. Power Pages
3. Power Automate
4. Plugins
5. Azure Function Apps

The solution generates fully formatted PDFs in real time using structured JSON payloads.

This eliminated authentication failures while significantly improving speed and reliability.

1] Power Pages Button triggers Flow

A “Download Report” button captures the project GUID and triggers a Power Automate flow with real-time progress feedback.

2] Dynamics 365 Plugin prepares JSON payload

A bound action plugin retrieves all project data and converts it into a clean JSON payload for PDF generation.

3] Azure Function generates PDF

The Azure Function processes the JSON and generates a formatted PDF, returning it as a Base64 string.

4] SharePoint Integration

The generated PDF is automatically stored in the associated SharePoint document location linked to the project. This ensures centralized document management, version control, and easy access for stakeholders directly within the project workspace.

5] Portal PDF Preview

The Base64 PDF is rendered directly in the portal using an iframe, allowing instant preview and download.

Video: End-to-end implementation of real-time PDF report generation.

1. 100% success rate — zero failures post deployment
2. Under 15 seconds report generation time
3. No infrastructure — fully serverless
4. Zero authentication failures
5. Faster iteration for report updates

Project managers can now confidently generate reports during live client meetings.

Why not fix the SSRS authentication issue instead of replacing SSRS entirely?

The authentication failures were a structural consequence of traversing multiple service boundaries in an environment with strict Defender for Cloud Apps session policies. Fixing them would have required either relaxing those policies — which the client’s security posture did not permit — or re-architecting the data retrieval to stay inside the platform, which is exactly what the bound action approach achieves. Replacing SSRS also removed a separate infrastructure dependency and gave the client full control over report formatting in code.

Can this pattern be reused for other document types in Dynamics 365?

Yes. The Azure Function App’s renderer is data-driven — it consumes a JSON payload and builds tables from whatever keys are present. The Dynamics 365 plugin can be adapted to query any entity and produce an equivalent payload. CloudFronts has applied the same pattern to inspection records, summary reports, and client-facing status documents across Professional Services and Manufacturing implementations.

Does this work for environments without Microsoft Defender for Cloud Apps?

Yes. The architectural benefits — synchronous generation, serverless PDF rendering, no SSRS infrastructure, and in-browser preview — apply regardless of the security layer on the environment.

Replacing SSRS with an Azure Function App-based PDF renderer resolved both the reliability and authentication problems in a single architectural shift, delivering instant, professional-quality Project Status Reports from a Microsoft Power Pages portal with no legacy reporting infrastructure to maintain. The key lesson from this project is that keeping authentication within the Dynamics 365 service layer — rather than bridging to external systems — eliminates an entire category of environment-specific failures that are otherwise very difficult to diagnose and fix.

By keeping authentication within Dynamics 365 and leveraging serverless architecture, the solution delivers instant, high-quality reports without infrastructure overhead.

This approach demonstrates how modern cloud-native patterns can eliminate entire classes of system failures while improving user experience dramatically.