SUMMARY:
SQL Server 2025’s new licensing includes Power BI Report Server, offering cost-effective on-premise BI with better data security and performance.
Table of contents
Introduction
The debate between cloud and on-premises business intelligence has always been a balance between convenience and control. For many organizations with strict data sovereignty, security, or performance requirements, the Power BI Service (cloud) introduced complexities that often offset its ease of use. However, a significant shift in Microsoft’s licensing strategy with SQL Server 2025 now makes the on-premise solution, Power BI Report Server (PBIRS), the compelling choice for enterprise clients.
The most critical update is simple yet powerful: Power BI Report Server is now included with SQL Server 2025 Standard and Enterprise core licenses. This removes the previous, costly requirement for an active Software Assurance (SA) subscription or Power BI Premium capacity. By eliminating this significant licensing barrier, Power BI On-Premise becomes a far more accessible and cost-effective option for organizations already invested in the SQL Server ecosystem.
Beyond the cost savings, your clients gain essential benefits, which we’ve consistently observed in our own project work.
Case Studies: The Real-World Benefits of On-Premise Control
Based on real-world challenges encountered by organizations leveraging Power BI with on-premise data, here is why a switch to a fully on-premise PBIRS solution with SQL Server 2025 is the strategic move:
1. Eliminating Security and Data Locality Concerns
The Challenge: Connecting the Power BI Service to on-premise data often requires setting up a Data Gateway. While functional, this hybrid approach involves complexity and can inadvertently create data security and locality concerns.
The Case: A client (Client A) with on-premise SQL data was using the Power BI Service with the Import method. This meant the data was going to Azure via the gateway and then being used to render the reports, creating a round trip and raising immediate cybersecurity concerns about data moving off-site, even temporarily.
The Solution: A fully on-premise Power BI Report Server deployment keeps all data, reports, and report consumption within the client’s firewall. This eliminates the data gateway as a dependency and satisfies the strictest data sovereignty and compliance requirements by ensuring data never leaves the local environment.
2. Streamlining Performance and Troubleshooting
The Challenge: Hybrid environments introduce latency and multiple points of failure. When performance issues arise, troubleshooting must span local servers, the Data Gateway, and the cloud service.
The Case: A client (Client B) experienced significant slowness in both the Power BI Desktop and Online versions of a report, with visuals taking several minutes to render. Notably, the underlying SQL queries executed fine in SSMS (on-prem). In another instance, the client faced a security issue where a Power BI Data Gateway update enforced encryption for on-prem SQL Server connections, necessitating a complex fix involving certificates and potential application impacts.
The Solution: PBIRS runs entirely on your client’s infrastructure. Performance is solely reliant on the server’s specifications and network speed. This simplifies the architecture, significantly reduces latency, and removes the cloud-to-on-prem communication layer as a source of performance degradation and unforeseen technical/security hurdles.
3. Achieving Full Security and Governance Control
The Challenge: Leveraging on-premise data security (like Windows Authentication) through the cloud Power BI Service can be challenging, often forcing clients into workarounds that compromise their desired security model.
The Case: During a Power BI SSAS implementation, a Kerberos issue was identified that prevented user-level security when connecting from the Power BI Service to the on-prem SSAS cube. The only working fix was to use a generic service account, which, in the client’s words, prevented them from giving specific users access to the information they needed and would prevent them from progressing to a new phase involving highly confidential financial data.
The Solution: With Power BI Report Server, the security model is integrated directly with your existing on-premise Active Directory and SQL Server permissions. This allows for granular, user-specific security end-to-end, leveraging decades of investment in on-premises Windows and database security infrastructure, without the “double-hop” or service account compromises seen in hybrid scenarios.
Conclusion
SQL Server 2025 marks a pivotal moment for Power BI Report Server. By making this modern on-premise reporting platform available with Standard edition core licenses, Microsoft is giving clients a powerful, cost-effective option to take back control of their BI environment. For clients with security concerns, performance demands, or strict data locality requirements—issues that regularly complicate the Power BI Service/Data Gateway model—the switch to a fully integrated Power BI Report Server and SQL Server 2025 architecture is not just an option; it’s the intelligent path forward.
Note: Microsoft is consolidating its on-premises reporting under Power BI Report Server, effectively replacing the traditional SQL Server Reporting Services (SSRS) in SQL Server 2025.
Contact us for any questions.