Power BI Report Server & Custom Visuals: Compatibility Guide (2026)

Custom visuals (.pbiviz) do run in Power BI Report Server, and Microsoft states they only work with Report Server versions released after May 2021, earlier builds have known rendering problems that a server upgrade fixes. What trips people up is that PBIRS is the on-premises product and intentionally lags the cloud Power BI Service: it ships on a roughly three-times-a-year cadence (recent releases are May 2025, September 2025, January 2026, and May 2026), so its visuals platform is always a few steps behind Fabric. Three conditions decide whether a given visual works on-prem: (1) you authored it with the Report-Server-optimized Desktop build that matches your server, (2) the visual targets a visuals-API version your server supports, and (3) the visual doesn't depend on an internet service your deployment can't reach. The rest of this guide unpacks each one.

Report Server has its own Desktop client, 'Power BI Desktop (optimized for Power BI Report Server)', separate from the monthly Desktop you use for the Service. You must author and save your .pbix with the build that matches your server release: a report saved by a newer Desktop build cannot be published to an older server, and since the September 2025 release the server returns a specific error when you try. Download the matching build from Microsoft's Download Center (there is a distinct download per release) and standardize your report authors on it. Recent pairings from the official Report Server change log:

Every Report Server release bundles a specific Power BI visuals API. The September 2025 release (and the May 2025 release before it) shipped visuals API v5.10.0; Microsoft doesn't always print a new API number with each subsequent build, so for the exact version on your release, check the 'Custom Visual API shipped with release' line in the Report Server change log for the January 2026 or May 2026 build you run. Why it matters: a .pbiviz compiled against a newer apiVersion than your server understands may fail to render. There is a safety net, Power BI on Report Server will fall back to a previous version of a visual that's compatible with the server's API if one is available, but that fallback isn't guaranteed for every visual. When you generate or build a visual for an on-prem deployment, target an apiVersion at or below what your server ships, and test on the actual server before rolling out.

In the cloud, admins publish approved visuals to an organizational repository through the Admin portal, and users pull them straight into Desktop. That organizational-visuals store does not exist in Power BI Report Server, Microsoft explicitly states organizational Power BI visuals aren't supported on-prem. On PBIRS, each report carries its own visual: you import the .pbiviz into the report and publish it. Certification still governs behavior. A 'certified' visual is one Microsoft has tested to confirm it doesn't access external services or resources, its capabilities declare no WebAccess privileges and it makes no fetch or XMLHttpRequest calls off the machine. That is exactly the property you want on-prem, and especially in air-gapped networks, because such a visual has no external dependency to fail. Uncertified visuals aren't inherently unsafe and do import from file, but any visual that calls an external service (map visuals like Mapbox, Visio, Power Automate, and similar) will not work where that service is unreachable. If a certified-visuals-only policy is enforced, the 'Import a visual from a file' option is disabled and only certified visuals are allowed.

Step by step: 1) Open your report in the matching 'Power BI Desktop (optimized for Report Server)' build. 2) In the Visualizations pane, select the '...' (Get more visuals) button. 3) Choose 'Import a visual from a file' and pick your .pbiviz, or choose 'Get more visuals' to browse AppSource (this requires internet access from the authoring machine). 4) Drop the new visual onto the canvas and bind your fields. 5) Save the report to your Report Server (File > Save as > Power BI Report Server) or upload the .pbix through the web portal. Because there's no central organizational repository, the visual travels inside the report, every report that needs it imports its own copy, and updating a visual means re-importing it and republishing the affected reports.

Even a self-contained visual can appear to hang on import. By default, when you import a local .pbiviz, Power BI Desktop for Report Server tries to reach https://pbivisuals.powerbi.com to fetch the latest copy of the visual; if the machine is offline or that host is blocked, the visual spins and never appears, and logs show a DNS-lookup failure for pbivisuals.powerbi.com. On the authoring side, either allowlist https://pbivisuals.powerbi.com or, on a machine with no internet at all, set a user environment variable and restart Desktop so it uses the copy packaged in the report:

Works in Desktop, blank in Report Server: version mismatch or an out-of-date server. Confirm you authored with the matching Report-Server-optimized Desktop build, and that the server is a post-May-2021 release; upgrade the server if not. || Visual spins forever on import: the machine can't reach pbivisuals.powerbi.com. Allowlist it, set PBI_userFavoriteResourcePackagesEnabled to 0, or set EnableCDNVisual to False on the server (an advanced server property, default True, configurable in SQL Server Management Studio) so visuals load from the published report. Expect a 20 to 30 second delay on first load while the offline lookup times out. || Rendering errors after updating Desktop: since the May 2025 Desktop-for-RS build your CPU must support AVX instructions, and AVX must be enabled in BIOS or VM settings; older or restricted CPUs throw visual-rendering errors. || 'Get more visuals' or 'Import from file' greyed out: a certified-visuals-only policy is in effect, so only certified visuals are permitted. || Slow custom visuals: setting EnableCDNVisual to False (loading from the report rather than the CDN) commonly resolves sluggish rendering on Report Server. || Publishing rejected: your .pbix was saved by a newer Desktop build than the server supports, re-save with the matching build.