Co-authored by

What Is Power BI Report Server and Why Does It Matter for GCC Enterprises?

Quick answer: Power BI Report Server (PBIRS) is Microsoft's on-premises reporting platform that lets GCC enterprises host interactive Power BI reports, paginated reports, and KPIs entirely within their own data centers — critical for organizations bound by UAE PDPL, Saudi PDPL, or sector-specific data sovereignty mandates.

Power BI Report Server occupies a specific and increasingly important position in the Microsoft BI stack for Gulf Cooperation Council enterprises. While the cloud-based Power BI Service dominates most global deployments, GCC organizations — particularly government agencies, defense contractors, financial regulators, and critical infrastructure operators — frequently face constraints that prevent sensitive data from leaving sovereign territory.

PBIRS runs on Windows Server infrastructure within an organization's own data center, hosting Power BI reports (.pbix), paginated reports (.rdl), and Excel workbooks through a web portal. No data leaves the network perimeter. No cloud dependency exists for report rendering or data refresh.

The platform matters more in 2026 than it did two years ago for three reasons. First, SQL Server 2025 licensing changes have made PBIRS dramatically more accessible — Standard edition now qualifies, and Software Assurance is no longer required. Second, Microsoft has retired SQL Server Reporting Services (SSRS) as a standalone product, making PBIRS the only supported on-premises reporting path forward. Third, Saudi Arabia's Azure region will not be available until Q4 2026, leaving Saudi government agencies without an in-kingdom cloud option for most of the year.

For a broader view of how Power BI fits into GCC public sector strategy, see our guide to Power BI for GCC government analytics.

How Has Power BI Report Server Licensing Changed with SQL Server 2025?

Quick answer: SQL Server 2025 extends PBIRS rights to Standard edition licenses and removes the Software Assurance requirement — reducing the cost of entry for on-premises BI by 50-70% compared to the previous Enterprise-with-SA model.

This is the most consequential licensing change for on-premises Power BI in years.

Previous Licensing (SQL Server 2022 and Earlier)

PBIRS required SQL Server Enterprise edition core licenses with active Software Assurance. Enterprise core licensing runs approximately USD 15,000 per 2-core pack at open NL pricing, with a minimum of 4 cores per server. For a typical 16-core production server, that translates to roughly USD 120,000 before adding SA at approximately 25% annually.

New Licensing (SQL Server 2025)

Starting with SQL Server 2025, any customer with a paid edition — Enterprise or Standard — can use their product key to install both the database engine and Power BI Report Server. Software Assurance is no longer required. SQL Server Standard edition 2-core packs cost approximately USD 3,945, putting the same 16-core server at roughly USD 31,560.

For GCC government agencies running centralized procurement through Enterprise Agreements, the Standard edition path opens PBIRS to departments that previously could not justify Enterprise licensing. The caveat: Standard edition carries feature limitations — notably a 256 GB memory cap (doubled from 128 GB in SQL Server 2022) and a 32-core limit, with limited high-availability options — which are acceptable for most mid-size deployments but may constrain agencies serving thousands of concurrent users.

Why Is SSRS Being Retired and What Replaces It?

Quick answer: SQL Server 2022 is the final version to include SSRS. Microsoft has consolidated all on-premises reporting under Power BI Report Server starting with SQL Server 2025, with SSRS 2022 receiving security-only support through January 11, 2033.

According to the Reporting Services Consolidation FAQ, no new versions of SSRS will be released. PBIRS is the sole on-premises reporting product going forward. SSRS 2022 remains supported until January 11, 2033 with security updates, and organizations can continue using SSRS 2022 with later SQL Server Database Engine versions during a transition period.

PBIRS is a superset of SSRS — every SSRS capability (paginated reports, RDL authoring, subscriptions, row-level security) exists in PBIRS, plus interactive Power BI reports (.pbix), custom visuals, and data modeling:

For GCC enterprises running SSRS, migration to PBIRS is a question of timing, not whether. Organizations planning SQL Server 2025 upgrades should consolidate reporting as part of that project.

How Does Power BI Report Server Compare to the Power BI Service?

Quick answer: PBIRS provides full on-premises control and data sovereignty but lacks dashboards, Q&A natural language queries, real-time streaming, and the monthly feature cadence of the cloud service — making it the right choice specifically when data cannot leave sovereign territory.

The feature comparison from Microsoft makes the trade-offs explicit:

Organizations choosing PBIRS are explicitly trading feature velocity for data sovereignty. In the GCC context, that trade-off is often non-negotiable when UAE PDPL, Saudi PDPL, or NESA Information Assurance Standards require data to remain on-premises.

The practical recommendation for most GCC enterprises is a hybrid architecture: PBIRS for classified or regulated datasets, and the Power BI Service for non-sensitive workloads. The on-premises data gateway bridges the two environments without replicating sensitive data to the cloud.

What Is the Saudi Interim Architecture Before Azure Saudi East?

Quick answer: Until the Azure Saudi Arabia East region launches in Q4 2026, Saudi enterprises deploy PBIRS on-premises for sovereign data and use the on-premises data gateway for hybrid connectivity — avoiding cross-border data transfer while preserving cloud collaboration for non-sensitive workloads.

Microsoft confirmed in February 2026 that the Saudi Arabia East datacenter region will be available for production workloads from Q4 2026. Until then, the Power BI Service stores data outside the Kingdom, conflicting with SDAIA's National Data Governance Framework.

Recommended Three-Tier Architecture

Tier 1 — Classified and regulated data (PBIRS on-premises). Datasets containing personal data under the Saudi PDPL, government-classified information, or sector-regulated data remain on PBIRS in Saudi data centers. No data leaves Saudi territory.

Tier 2 — Non-sensitive workloads (Power BI Service via UAE North). Aggregated, anonymized, or public datasets can use the Power BI Service through Azure UAE North with contractual data handling agreements, providing access to dashboards, Q&A, and AI visuals unavailable in PBIRS.

Tier 3 — Hybrid bridge (on-premises data gateway). Gateway clusters in Saudi data centers enable cloud-hosted reports to query on-premises databases via DirectQuery — the data stays in Saudi Arabia while report rendering occurs in the cloud.

Once Azure Saudi East goes live, organizations reconfigure their tenant to the Saudi region, migrate eligible PBIRS workloads to the cloud, and maintain PBIRS only for classifications that mandate physical on-premises infrastructure.

How Do You Migrate from SSRS to PBIRS in a GCC Environment?

Quick answer: SSRS-to-PBIRS migration is a direct upgrade for paginated reports — existing .rdl files are fully compatible — but GCC environments must account for Arabic RTL layouts, Hijri date formatting, and data classification requirements during the transition.

Microsoft provides a detailed migration guide: back up encryption keys and the report server database, install PBIRS, restore the database, and reconfigure the web portal URL. Existing RDL reports, data sources, subscriptions, and schedules carry over without modification.

GCC-Specific Considerations

Arabic RTL and bilingual reports. The RDL specification supports locale-based formatting through the Language property — setting ar-SA or ar-AE enables RTL rendering, Arabic numeral formatting, and Hijri calendar dates. These properties transfer intact, but bilingual reports require validation of text box alignment and RTL table column ordering in the PBIRS web portal.

Hijri calendar parameters. Saudi government reports frequently use Hijri dates for fiscal periods and compliance deadlines. PBIRS supports Hijri formatting through System.Globalization.UmAlQuraCalendar expressions. Verify that Hijri date pickers and subscriptions aligned to Hijri fiscal periods continue functioning after migration.

Data classification. Before migrating, classify datasets against the applicable framework — NESA Information Assurance Standards for UAE, SDAIA classification for Saudi. This determines which reports can later move to the cloud and which must remain permanently on PBIRS.

Migration Checklist

1. Inventory all SSRS reports, data sources, and subscriptions
2. Classify datasets by sovereignty requirement (on-premises mandatory vs. cloud eligible)
3. Back up SSRS encryption keys and report server database
4. Install PBIRS using a SQL Server 2025 Standard or Enterprise key
5. Restore the database and validate Arabic RTL layouts and Hijri dates
6. Test subscriptions, scheduled refreshes, and row-level security
7. Document the deployment for NESA, UAE PDPL, or Saudi PDPL compliance

What Does Data Sovereignty Mean for the PBIRS Decision in UAE and Saudi Arabia?

Quick answer: The UAE PDPL (Federal Decree-Law No. 45 of 2021) and Saudi PDPL (enforced by SDAIA with fines up to SAR 5 million) both impose data localization requirements that make PBIRS essential for classified government data and regulated personal data.

Azure UAE North holds the DESC CSP Security Standard certification, so UAE organizations have a viable cloud path for most workloads. PBIRS remains necessary for data classified at NESA tier 3 or above where policy mandates physical on-premises infrastructure. The UAE PDPL Executive Regulations have not yet been published as of early 2026 — once issued, organizations will have six months to comply.

Saudi Arabia's PDPL is in active enforcement since September 2024 — SDAIA is actively reviewing complaints and can impose fines up to SAR 5 million and imprisonment for unauthorized disclosure. Until Azure Saudi East launches in Q4 2026, PBIRS is the only Microsoft BI platform that can guarantee full Saudi data sovereignty for classified and personal data.

PBIRS system requirements are modest — Windows Server 2019+, .NET 4.8+, SQL Server 2014 SP3+ for the catalog database, and CPUs with AVX instruction support (required since May 2025). For production GCC deployments, plan for 16-64 GB RAM, SSD storage, and Windows Server 2025 on the official requirements. Full details on UAE and Saudi compliance frameworks are covered in our GCC government analytics guide.

Frequently Asked Questions

Q: Can we run Power BI Report Server on SQL Server Standard edition?

Yes, starting with SQL Server 2025. Microsoft expanded PBIRS licensing to include both Standard and Enterprise editions and removed the Software Assurance requirement. Any customer with a paid SQL Server 2025 license can use the same product key to install PBIRS. This applies only to SQL Server 2025 licenses; earlier versions still require Enterprise with active SA.

Q: When does SSRS reach end of life?

SSRS 2022 is the final version. Microsoft will provide security updates through January 11, 2033, in alignment with the SQL Server 2022 support lifecycle. SSRS 2022 can continue to use later Database Engine versions, so upgrading to SQL Server 2025 does not force an immediate SSRS migration.

Q: Is Power BI Report Server a full replacement for SSRS?

Yes. PBIRS is a superset of SSRS — it supports all SSRS capabilities (paginated RDL reports, subscriptions, row-level security) plus interactive Power BI reports, custom visuals, and data modeling. Existing RDL reports are fully compatible without modification. Migration involves a database backup and restore, not a report-by-report rewrite.

Q: Does PBIRS support Arabic right-to-left reports?

PBIRS supports RTL layouts for paginated reports through the RDL Language property — setting ar-SA or ar-AE enables Arabic RTL rendering, Arabic numerals, and Hijri calendar dates. Interactive Power BI reports (.pbix) have more limited RTL support, as Power BI Desktop does not currently offer full RTL authoring. For heavy Arabic reporting, paginated reports remain the stronger format.

Q: Can PBIRS and the Power BI Service run in parallel?

Yes, and this hybrid model is recommended for most GCC enterprises. PBIRS handles sovereign datasets while the Power BI Service provides cloud collaboration features for non-sensitive workloads. The on-premises data gateway bridges the two environments, enabling cloud reports to query on-premises data without replicating it.

Q: What is the Saudi interim architecture before Azure Saudi East launches?

Deploy PBIRS on-premises for data subject to Saudi PDPL or government classification. Non-sensitive workloads can use the Power BI Service via Azure UAE North with contractual data handling agreements and a cross-border transfer risk assessment per SDAIA's March 2025 regulations. Once Azure Saudi East goes live in Q4 2026, reconfigure for in-kingdom data residency.

Q: How long does an SSRS-to-PBIRS migration take?

The technical migration — backup, install, restore, validate — takes 1-2 weeks. GCC-specific validation (Arabic RTL testing, Hijri date verification, bilingual report QA, data classification, compliance documentation) extends the realistic timeline to 4-8 weeks for organizations with established change management processes.

Q: Does Power BI Report Server support Microsoft Fabric features?

No. PBIRS operates independently from Microsoft Fabric. Copilot, OneLake, data pipelines, and real-time analytics are cloud-only capabilities. PBIRS receives a subset of Power BI Desktop features through its three-times-per-year release cycle (January, May, September). Organizations needing both Fabric and on-premises sovereignty should implement the hybrid architecture with gateway connectivity.