EPC Group - Enterprise Microsoft AI, SharePoint, Power BI, and Azure Consulting
G2 High Performer Summer 2025, Momentum Leader Spring 2025, Leader Winter 2025, Leader Spring 2026
BlogContact
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌

EPC Group

Enterprise Microsoft consulting with 29 years serving Fortune 500 companies.

(888) 381-9725
contact@epcgroup.net
4900 Woodway Drive, Suite 830
Houston, TX 77056

Follow Us

Solutions

  • M&A Practices

    • M&A Tenant Migration
    • Carve-Out Migration
    • Private Equity Practice
    • Engagement Operating Model
  • All Services
  • Microsoft 365 Consulting
  • AI Governance
  • Azure AI Consulting
  • Cloud Migration
  • Microsoft Copilot
  • Data Governance
  • Microsoft Fabric
  • Dynamics 365
  • Power BI Consulting
  • SharePoint Consulting
  • Microsoft Teams
  • vCIO / vCAIO Services
  • Large-Scale Migrations
  • SharePoint Development

Industries

  • All Industries
  • Healthcare IT
  • Financial Services
  • Government
  • Education
  • Teams vs Slack

Power BI

  • Case Studies
  • 24/7 Emergency Support
  • Dashboard Guide
  • Gateway Setup
  • Premium Features
  • Lookup Functions
  • Power Pivot vs BI
  • Treemaps Guide
  • Dataverse
  • Power BI Consulting

Company

  • About Us
  • Our History
  • Microsoft Gold Partner
  • Case Studies
  • Testimonials
  • Fixed-Fee Accelerators
  • Blog
  • Resources
  • All Guides & Articles
  • Video Library
  • Client Reviews
  • Engagement Operating Model
  • FAQ
  • Contact
  • Schedule a consultation

Microsoft Teams

  • Teams Questions
  • Teams Healthcare
  • Task Management
  • PSTN Calling
  • Enable Dial Pad

Azure & SharePoint

  • Azure Databricks
  • Azure DevOps
  • Azure Synapse
  • SharePoint MySites
  • SharePoint ECM
  • SharePoint vs M-Files

Comparisons

  • M365 vs Google
  • Databricks vs Dataproc
  • Dynamics vs SAP
  • Intune vs SCCM
  • Power BI vs MicroStrategy

Legal

  • Sitemap
  • Privacy Policy
  • Terms
  • Cookies

About EPC Group

EPC Group is a Microsoft consulting firm founded in 1997 (originally Enterprise Project Consulting, renamed EPC Group in 2005). 29 years of enterprise Microsoft consulting experience. EPC Group historically held the distinction of being the oldest continuous Microsoft Gold Partner in North America from 2016 until the program's retirement. Because Microsoft officially deprecated the Gold/Silver tiering framework, EPC Group transitioned to the modern Microsoft Solutions Partner ecosystem and currently holds the core Microsoft Solutions Partner designations.

Headquartered at 4900 Woodway Drive, Suite 830, Houston, TX 77056. Public clients include NASA, FBI, Federal Reserve, Pentagon, United Airlines, PepsiCo, Nike, and Northrop Grumman. 6,500+ SharePoint implementations, 1,500+ Power BI deployments, 500+ Microsoft Fabric implementations, 70+ Fortune 500 organizations served, 11,000+ enterprise engagements, 200+ Microsoft Power BI and Microsoft 365 consultants on staff.

About Errin O'Connor

Errin O'Connor is the Founder, CEO, and Chief AI Architect of EPC Group. Microsoft MVP multiple years, first awarded 2003. 4× Microsoft Press bestselling author of Windows SharePoint Services 3.0 Inside Out (MS Press 2007), Microsoft SharePoint Foundation 2010 Inside Out (MS Press 2011), SharePoint 2013 Field Guide (Sams/Pearson 2014), and Microsoft Power BI Dashboards Step by Step (MS Press 2018).

Original SharePoint Beta Team member (Project Tahoe). Original Power BI Beta Team member (Project Crescent). FedRAMP framework contributor. Worked with U.S. CIO Vivek Kundra on the Obama administration's 25-Point Plan to reform federal IT, and with NASA CIO Chris Kemp as Lead Architect on the NASA Nebula Cloud project. Speaker at Microsoft Ignite, SharePoint Conference, KMWorld, and DATAVERSITY.

© 2026 EPC Group. All rights reserved. Microsoft, SharePoint, Power BI, Azure, Microsoft 365, Microsoft Copilot, Microsoft Fabric, and Microsoft Dynamics 365 are trademarks of the Microsoft group of companies.

‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
‌
Power BI Paginated Reports: Enterprise Guide 2026 - EPC Group enterprise consulting

Power BI Paginated Reports: Enterprise Guide 2026

Power BI Paginated Reports enterprise guide — when to use vs interactive PBI, SSRS-to-Paginated migration, authoring best practices, capacity sizing, governance, regulated-industry use cases.

HomeBlogPower BI
Back to BlogPower BI

Power BI Paginated Reports: Enterprise Guide 2026

Power BI Paginated Reports enterprise guide — when to use vs interactive PBI, SSRS-to-Paginated migration, authoring best practices, capacity sizing, governance, regulated-industry use cases.

EO
Errin O'Connor
CEO & Chief AI Architect
•
January 9, 2026
•
5 min read
Power BIPaginated ReportsSSRSRDLPower BI Report BuilderMicrosoft Fabric
Power BI Paginated Reports: Enterprise Guide 2026
5 min readPublished January 9, 2026

Key Takeaways

  • Power BI Paginated Reports enterprise guide — when to use vs interactive PBI, SSRS-to-Paginated migration, authoring best practices, capacity sizing, governance, regulated-industry use cases.

Power BI Paginated Reports Enterprise Guide (2026)

Power BI Paginated Reports are the modern successor to SQL Server Reporting Services (SSRS), providing pixel-perfect, multi-page, formatted reports for invoices, financial statements, regulatory filings, audit reports, and operational documents that demand precise layout.

This is the working enterprise guide EPC Group uses for Fortune 500 Paginated Reports deployments — Power BI Report Builder authoring, Microsoft Fabric capacity sizing, RDL migration from SSRS, governance, sensitivity-label integration, and Microsoft 365 Copilot considerations.

EPC Group has delivered SSRS and Power BI Paginated Reports engagements for Fortune 500 healthcare, financial services, government, manufacturing, and technology since the SQL Server Reporting Services GA wave (2004) and through the Power BI Paginated Reports general availability.

TL;DR — When to Use Paginated Reports

Use Case Why Paginated
Invoices, statements, receipts Pixel-perfect, multi-page printable
Financial statements Regulatory formatting requirements
Regulatory filings (10-K, 10-Q, EDGAR) Pre-defined templates, reproducibility
Audit reports Page numbering, headers/footers, formal structure
Compliance reports (HIPAA, SOC 2) Templated, reproducible, legally-defensible
Operational documents Bulk parameterized printing
Subscription reports Scheduled email delivery

When NOT to use Paginated Reports: interactive dashboards (use Power BI reports), self-service exploration (use Power BI), real-time monitoring (use Power BI with DirectQuery or Real-Time Intelligence).

Architecture

Power BI Report Builder

Power BI Report Builder is the free authoring tool for Paginated Reports. It uses RDL (Report Definition Language) — the same XML-based format as SSRS, enabling:

  • Direct migration from SSRS RDL
  • Re-use of existing parameter, expression, and dataset patterns
  • Co-existence with SSRS during migration
  • Standard BIDS / SSDT / Visual Studio extensibility

Capacity Requirement

Paginated Reports require Microsoft Fabric capacity OR Power BI Premium Per User (PPU):

Tier Notes
Microsoft Fabric F-SKU (F2+) Paginated Reports supported
Power BI Premium Per User (PPU) Paginated Reports supported
Power BI Pro NOT supported
Power BI Free NOT supported

Most enterprise Paginated Reports deployments run on Microsoft Fabric F-SKU capacity (F64+ for Power BI Copilot, F128+ for typical Fortune 500 mixed workloads).

Data Source Connectivity

Paginated Reports support broad data source connectivity:

  • SQL Server, Azure SQL Database, Synapse, Microsoft Fabric Warehouse
  • Oracle, Teradata, SAP HANA, IBM Db2 (via on-premises gateway)
  • Power BI semantic models (DirectQuery)
  • OData, REST APIs (via custom data connectors)
  • Excel files, CSV files
  • Web Service data sources (SOAP)

Phase 1: SSRS to Power BI Paginated Reports Migration

Migration Tooling

Microsoft provides:

  • RDL Migration Tool — bulk migration of SSRS reports to Power BI service
  • Reportbuilder /noprompt /pbi — command-line conversion
  • PowerShell SQLServer module — programmatic migration

Migration Considerations

Most SSRS reports migrate cleanly. Common compatibility considerations:

  • Custom code references (Code property in SSRS) — supported in Power BI Paginated, but some assemblies require update
  • Custom report items — verify Power BI compatibility
  • Linked reports — pattern differs in Power BI service (use parameter datasets instead)
  • Custom datasets in Microsoft .NET assemblies — refactor to Power Query or T-SQL
  • Email subscription delivery — migrate to Power BI subscriptions
  • Snapshot rendering — migrate to scheduled refresh patterns

Phased Migration

EPC Group standard SSRS migration phasing:

  • Phase 1 (Discovery): Inventory all SSRS reports, identify custom code, prioritize by business value
  • Phase 2 (Pilot): Migrate 10-20 high-value reports, validate process
  • Phase 3 (Bulk migration): Department-aligned waves
  • Phase 4 (Subscription migration): Email subscriptions migrated to Power BI
  • Phase 5 (Decommission): SSRS infrastructure decommission

Typical Fortune 500 timeline: 6-12 months for 1,000-5,000 SSRS reports.

Phase 2: Authoring Best Practices

Parameterization

  • All filterable values as parameters (date range, region, customer ID, account)
  • Multi-value parameter support for "select multiple" scenarios
  • Cascading parameters (Region → Country → State)
  • Default values for common scenarios
  • Hidden parameters for technical use (server-side defaults)

Pixel-Perfect Layout

  • Use rectangle containers for grouped layout sections
  • Page header and footer with logo, page number, generation date
  • Repeating row headers on tables that span pages
  • Page break controls for multi-page reports
  • Print-optimized margins and orientation

Performance

  • Pre-aggregate at source rather than in report
  • Use stored procedures for complex business logic
  • Avoid expression-heavy column calculations (compute upstream)
  • DirectQuery to Power BI semantic models for simple aggregations
  • T-SQL for complex transformations

Accessibility

  • Tab order for screen readers
  • Alt text on images
  • Keyboard navigation
  • Color contrast (avoid red-only or green-only signals)
  • Print-readable layout (don't rely on color alone)

Phase 3: Governance

Workspace Organization

  • Department-level workspaces for ownership
  • Hub-style workspaces for shared infrastructure (corporate templates, datasets)
  • Capacity assignment based on usage patterns
  • Sensitivity label inheritance from source data

Sensitivity Labels

  • Inherited from source semantic model or data source
  • Applied at report or dataset level
  • Block external sharing of Restricted-tier reports
  • Microsoft Copilot grounding scope respects label hierarchy

Row-Level Security and Data Source Security

Paginated Reports respect:

  • Power BI semantic model RLS (when sourced from semantic model)
  • SQL Server / Azure SQL row-level security (with EXECUTE AS user)
  • T-SQL impersonation for source-side security

For multi-customer reports (sales territory, region, etc.), RLS is standard.

Subscription Management

  • User-managed subscriptions (own report)
  • Standard subscription delivery (PDF, Excel, Word, image)
  • Email-based scheduled delivery
  • OneDrive / SharePoint delivery
  • Microsoft Power Automate integration for advanced workflows

Phase 4: Microsoft 365 Copilot Considerations

Copilot Grounding

Microsoft 365 Copilot does not currently natively explore Paginated Reports content (RDL files are not directly grounded). Common patterns:

  • Generate Paginated Report PDF, store in SharePoint with sensitivity label, Copilot grounds on PDF
  • Surface key Paginated Report data points in Power BI semantic model for Copilot grounding
  • Use Microsoft Copilot Studio to wrap Paginated Reports as a custom Copilot agent

Power BI Copilot

Power BI Copilot focuses on interactive Power BI reports rather than Paginated. The differentiation is intentional:

  • Power BI Copilot — natural-language report authoring, semantic model exploration
  • Paginated Reports — pixel-perfect, regulated-format reproduction

Common Use Cases by Industry

Healthcare

  • HEDIS measure reports
  • CMS Star Ratings filings
  • Joint Commission audit reports
  • Patient financial statements
  • Quality and safety reports
  • Provider compensation reports

Financial Services

  • Regulatory filings (Form 10-K, 10-Q, FOCUS, RegW, RegYY)
  • FFIEC call reports
  • Customer account statements
  • Trade confirmations
  • Compliance attestation reports
  • Internal audit reports

Government

  • Federal regulatory filings
  • State agency reports
  • Audit-defensible operational reports
  • Federal grant reporting
  • HHS / DHS / DOD operational reporting
  • FedRAMP continuous monitoring reports

Manufacturing

  • Supplier performance reports
  • Quality control reports (CPK, defect rate)
  • Plant operations reports
  • Inventory aging reports
  • Capital expenditure reports

Retail / CPG

  • Store performance reports
  • Vendor compliance reports
  • Inventory turn reports
  • Promotion effectiveness reports
  • Loss prevention reports

Frequently Asked Questions

Should we use Paginated Reports or Power BI?

Use Paginated Reports for pixel-perfect, multi-page, regulated-format documents. Use Power BI for interactive analytics, dashboards, self-service exploration. Many enterprises use both — Paginated Reports for operational documents, Power BI for executive analytics. EPC Group standard: 80% of reporting needs are Power BI; 20% are Paginated Reports.

Do we need to migrate from SSRS?

For SSRS 2016/2017/2019/2022 on-premises: not strictly required (extended support continues), but Power BI Paginated Reports provides cloud benefits — Microsoft Entra ID identity, Microsoft Purview governance, Microsoft Sentinel auditing, automatic patching. Most Fortune 500 SSRS environments are migrating over 2026-2027.

What about SSRS hybrid?

Power BI Report Server (on-premises) provides SSRS-compatible deployment with Power BI integration. EPC Group recommends Power BI service over Power BI Report Server for new deployments — better cloud feature parity, fewer infrastructure obligations.

How much does this cost?

  • Power BI Report Builder: free (authoring)
  • Microsoft Fabric F64+ capacity: $5,800/month reserved (for Paginated Reports + Power BI Copilot)
  • Power BI Premium Per User: $20/user/month (for organizations with under 200 Power BI users)

What about regulated industries?

Healthcare, financial services, government deploy Paginated Reports for regulatory and audit-defensible reporting. Sensitivity-label coverage, Microsoft Purview audit log retention, and Microsoft Sentinel monitoring are required for compliance posture.

Who delivers Paginated Reports engagements?

EPC Group senior architects with combined SSRS and Power BI experience since SQL Server 2000 / Power BI Project Crescent (2010-2013). Errin O'Connor was on the original Microsoft Power BI beta team and is a 4-time Microsoft Press author including a Power BI book.

Next Steps

Schedule a 30-minute Power BI Paginated Reports discovery call at /schedule or call (888) 381-9725. Senior architects (not sales) take discovery calls.

Related reading: Power BI Premium Pricing Licensing Guide, Microsoft Fabric Quickstart Assessment, Healthcare Analytics Power BI HIPAA Enterprise Guide, Government Analytics Power BI FedRAMP Enterprise Guide, and Power BI Report Automation Scheduled Refresh Guide.

Share this article:
EO

Errin O'Connor

CEO & Chief AI Architect

Microsoft Press bestselling author with 29 years of enterprise consulting experience.

View Full Profile

Related Articles

Power BI

Tableau to Power BI Migration: Enterprise Consolidation Guide (2026)

Why Fortune 500 enterprises are consolidating Tableau workloads to Microsoft Power BI in 2026. The 4-phase migration runbook, cost comparison, governance continuity, and Power BI Beta Team founding-member methodology from 29 years of Microsoft consulting.

Power BI

Microsoft Fabric vs Power BI Premium: When to Migrate (2026)

Microsoft is consolidating Power BI Premium capacity into Microsoft Fabric F-SKUs. When existing Power BI Premium customers should migrate, the F64 inflection point, and the migration playbook for Fortune 500.

Power BI

Power BI May 2026 Update: Visual Calculations GA, Exploration Perspective, and Copilot Summarize — Enterprise Implementation Guide

Power BI May 2026 enterprise rollout: Visual Calculations GA, Exploration Perspective, Copilot Summarize. Governance patterns, migration plan, semantic model impact.

Need Help with Power BI?

Our team of experts can help you implement enterprise-grade power bi solutions tailored to your organization's needs.

Power BI Consulting ServicesSchedule a Consultation