Microsoft Power BI Report Server

Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Power BI Report Server Integration (Configuration Manager) Article09/27/2024 In this article -->Applies to: SQL Server 2016 (13.x) Reporting Services and later Power BI Report ServerThe Power BI Integration page in Reporting Services Configuration Manager is used to register the report server with the desired Microsoft Entra tenant to allow users of the report server to pin supported report items to Power BI dashboards. For a list of the supported items you can pin, see Pin Reporting Services items to Power BI Dashboards. Requirements for Power BI IntegrationIn addition to an active internet connection so you can browse to the Power BI service, the following are requirements to complete Power BIintegration.Microsoft Entra ID: Your organization must use Microsoft Entra ID (formerly Azure Active Directory), which provides directory and identity management for Azure services and web applications. For more information, see What is Microsoft Entra ID?Microsoft Entra tenant: The Power BI dashboard you want to pin report items to must be part of a Microsoft Entra tenant. A tenant is created automatically the first time your organization subscribes to Azure services such as Microsoft 365 and Microsoft Intune. Viral tenants are not supported.The user performing the Power BI integration needs to be a member of the Microsoft Entra tenant, a Reporting Services system administrator and a system administrator for the ReportServer catalog database.The user performing the Power BI integration needs to start the Reporting Services Configuration Manager either with the account used to install Reporting Services, or the account the Reporting Services service is running under.The server with Reporting Services installed needs to be configured to use TLS 1.2 or newer. For more information, see Transport

As a benchmark, we extrapolated the total user base Power BI Report Server could handle with 99% reliability.Workload8 Core/32 GB16 Core/64 GBPower BI Report Heavy1,000 users3,000 usersPaginated Report Heavy2,000 users3,200 usersSummaryFor each load test run, CPU was the most overwhelmed resource at the point of peak load on the Power BI Report Server machine. Due to this, the first resource that should be increased is the number of cores. Alternately, you can consider scaling out by adding more servers hosting Power BI Report Server in your topology.The results presented in this paper were derived from executing a specific set of reports consuming a specific set of data, repeated in a specific way. It's a useful reference point, but keep in mind that your usage will depend on your reports, queries, usage patterns and deployment of your Power BI Report Server.Appendix1 Topology1.1 Power BI Report Server TopologyTo focus solely on Power BI Report Server behavior under different configurations, the VM configuration for each type of machine (except for the machine hosting Power BI Report Server) was fixed. Each machine was provisioned according to the second-generation (v2) D Series machines with Premium Storage Disks. You can find detailed information about each VM size under the "General Purpose" section.Virtual Machine TypeProcessorMemoryAzure VM SizeActive Directory Domain Controller2 Cores7 GBStandard_DS2_v2SQL Server Database Engine and Analysis Services16 Cores56 GBStandard_DS5_v2Report Server Database16 Cores56 GBStandard_DS5_v21.2 Power BI Report Server Virtual Machine ConfigurationDifferent configurations of processor and memory were used for the Virtual Machine hosting Power BI Report Server. Unlike the other VMs, this machine was provisioned according to the third-generation (v3) D Series Machines with Premium Storage Disks. You can find detailed information about this VM size under the "General Purpose" sectionVirtual MachineProcessorMemoryAzure VM SizePower BI Report Server (Small)8 Cores32 GBStandard_D8S_v3Power BI Report Server (Large)16 Cores64 GBvStandard_D16S_v32 Run the LoadTest toolIf you'd like to run the Reporting Services LoadTest tool against your or a Microsoft Azure deployment of Power BI Report Server, follow these steps.Clone the Reporting Services LoadTest project from GitHub ( the project directory, you will find a solution file called RSLoadTests.sln. Open this file in Visual Studio 2015 or later.Determine whether you want to run this tool against your deployment of Power BI Report Server or against a deployment of Power BI Report Server in Microsoft Azure. If you are going to run it against your own deployment, go to step 5.Follow the instructions listed on to create a Power BI Report Server environment in Azure.Once you finish deploying the environment, follow the instructions listed on to run the tests.More questions? Try asking the Power BI Community --> Feedback Additional resources In this article

Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Capacity planning guidance for Power BI Report Server Article11/30/2020 In this article -->Power BI Report Server is a self-service BI and enterprise reporting solution that customers can deploy on their premises, behind their firewall. It combines the interactive report capability of Power BI Desktop with the on-premises server platform of SQL Server Reporting Services. With heavy and growing usage of analytics and reporting within enterprises, budgeting the hardware infrastructure and software licenses required to scale to an enterprise user base can be a challenge. This paper aims to offer guidance on capacity planning for Power BI Report Server by sharing results of numerous load test executions of various workloads against a report server. While organizations' reports, queries, and usage patterns vary widely, the results presented in this paper, along with the actual tests used and a detailed description of how they were executed, serve as a reference point for anyone in the early-stage planning process of deploying Power BI Report Server.Executive summaryWe executed two different types of workloads against Power BI Report Server; each workload consisted of rendering different types of reports as well as performing various web portal operations.In "Power BI Report Heavy" workload, the most frequently executed operation (i.e. the operation executed 60% of the time) was rendering Power BI reports.In "Paginated Report Heavy" workload, the most frequently executed operation was rendering paginated reports.Under a four-server topology of Power BI Report Server and the expectation that no more than 5% of users will access a report server at any one time, the following table describes the maximum number of users Power BI Report Server can handle with at least 99% reliability.Workload8 Core/32 GB RAM16 Core/64 GB RAMPower BI Report Heavy (>60%)1,000 users3,000 usersPaginated (RDL) Report Heavy (>60%)2,000 users3,200 usersIn each run, the most overwhelmed resource was CPU. Due to this, increasing the number of cores to Power BI Report Server would yield a higher gain in the reliability of the system than increasing the amount of memory or hard-disk space.Test methodologyThe testing topology used was based on Microsoft Azure Virtual Machines instead of vendor-specific physical hardware. All machines were hosted in US regions. This reflects the general trend of hardware virtualization both on-premises and in the public cloud.Power BI Report Server topologyThe Power BI Report Server deployment consisted of the following virtual machines:Active Directory Domain Controller: this was needed by SQL Server Database Engine, SQL Server Analysis Services, and Power BI Report Server to securely authenticate all requests.SQL Server Database Engine and SQL Server Analysis Services: this was where we stored all the databases for the reports to consume when we rendered them.Power BI Report ServerPower BI Report Server Database. The report server database is hosted on a different machine than Power BI Report Server so that it does not need to compete with SQL Server Database Engine for memory, CPU, network,