The forgotten local semantic model that most Power BI Report Server teams probably forgot about
This is a conversation I have more often than you might think. Especially last week. A team has landed on Power BI Report Server because the data needs to stay on-premises. They’ve done half a dozen or more reports. Then someone asked the obvious question: “Couldn’t we point all this to one common data set, like we do in Services?” And the answer is no. Power BI Report Server does not do that.
What’s that do do, if you know where to look, is something older and frankly better suited to the job: the SSAS Tabular model, created once and used by every report via a direct connection. When used correctly, SSAS Tabular with Power BI Report Server is equivalent to a certified shared dataset. It is your only source of truth. Most teams miss it, then wonder why three reports give the board three different numbers for the same metric.
Yes, the pattern works. Yes, it is supported. And for any farm that has more than one report and real governance requirements, this is the right decision, not over-engineering. The caveats are narrow but worth knowing.
Why Power BI Report Server forces the question
In Power BI Services, shared semantic models are the backbone of mature reporting. You publish one model, certify it, and then reports are connected to it. Everyone uses the same definitions, the same security, the same logic.
The Power BI Report Server is unmatched. Reports deployed there can be connected using imports, DirectQuery, or direct connections, but they cannot treat published .pbix datasets as shared sources like Services can. This was a question in my course last week focusing on Power BI Report Server, a great question, and the reason I wrote this. If you want a managed model that provides lots of local reporting, you need a place to place the model. SSAS Tabular is in there somewhere.
SSAS Tabular is your local certified model
Define once, consume anywhere. Relationships, hierarchies, certified actions, and row-level security are all in the SSAS model. The Report Server becomes the thin client in question. Nothing is copied into the report. Each interaction sends a query to the model and returns the latest processing results, so reports always reflect the current state of the model.
There’s a practical bonus in place: when Power BI Desktop and the SSAS server are on your network, a direct connection doesn’t require a gateway. The two just talked to each other.
Imagine a healthcare reporting area. One Tabular model contains admissions, RTT, and theater activity facts based on customized Date, Location, and Skill dimensions, with certified measures for 18 week RTT performance And use of theatre. Every board plan, every operational overview page, and every analyst ad hoc connection uses the same measurements. When Chief Executives and directorate managers quote the 18-week figure, the figure is the same, because it is calculated once, in the model, and not re-escalated in each report. For the scope of freedom of information and audit trails, it is that single lineage that is at the heart of the matter.
Security is in the model, not the report
With a direct connection, you secure the data in the model. Roles and rules are defined in SSAS, not in Power BI Desktop. When users open a report, their identity is passed to Analysis Services via the EffectiveUserName property, and model row-level security determines what they are allowed to see. Define security once, and every connected report will inherit it. You can’t accidentally leave the back door open on report number seven.
One sharp edge to plan. The Reports Server does not have a UPN mapping table, which the Service uses to reconcile cross-border identities. So direct connections across domain boundaries, with Report Server in one domain and SSAS in another, have no clean way to remap credentials and will cause you problems. Keep Report Server and SSAS on the same domain, or budget for Kerberos delegation work before you start.
The rewards of this approach
A pure direct connection is a single source. You can’t insert a second data source or Power Query step into a thin report. You can add report-level measurements, but a model is still a model. These obstacles are doing their job, not holding you back, but set expectations with your analyst early on.
Composite models alleviate this problem by allowing reports to extend the central model with local tables. However, they have a basic version: connecting to SSAS Tabular models in composite mode requires SQL Server Analysis Services 2022 or later. And it’s worth verifying rather than assuming, whether your Report Server built from Power BI Desktop, which lags behind mainstream Desktop, exposes composite Analysis Services on the version you’re running. Treat a clean, single-source live connection as your default, and prove that the composite works before you promise it.
Two more practicalities. Processing and refreshing are separate clocks: SSAS models are processed on their own schedule, and thin reports have no data to refresh, so they always display the last processed state of the model. And watch out for compatibility drift, models built at a compatibility level that the Report Server tool doesn’t understand, is a classic production failure. Embed your version and keep the Report Server Desktop in sync with the server.
License changed in November 2025 (check your SQL Server version)
Licensing shifted significantly with SQL Server 2025, so the old advice is now only half true. Under SQL Server 2025, Power BI Report Server is included with the Standard edition, not just Enterprise, and Software Assurance is no longer required. Any SQL Server 2025 Standard or Enterprise core license is eligible to run it. This is a real cost saver for teams that just want onsite reporting without Enterprise pricing. And stems from the decision to retire and retire SQL Server Reporting Services
Be aware that these new rights only apply to SQL Server 2025 licenses. In SQL Server 2022 and earlier, the old rules still apply. You need the Enterprise edition with Software Assurance active, or Power BI Premium P-SKU, or Fabric F64+. In each case, a Power BI Pro user subscription is still required to publish shared reports. Scope out client SQL Server versions and editions before you commit to a design, because the answer to “how much will it cost?” now completely dependent on him.
Is it worth it?
Reach for the SSAS Tabular gold standard model when more than one report or team requires the same actions, when row-level security orchestrated at scale is a requirement, when a single audited source of truth is absolutely necessary, or when the model logic will outlast a single report and merits being a version-controlled asset.
Don’t bother if it’s just one report, one team, simple data, and no governance drivers. There, a well-structured .pbix with a clean star schema answers the question, and the SSAS infrastructure, processing schedule, and deployment pipeline give you nothing but overhead.
One line answer: if more than one report uses the same size, the model is included in SSAS, not in .pbix. Below that threshold, you’re polishing infrastructure that no one asked for. On top of it, you’re building something that stops your reports from conflicting with each other.
Work with me on this
Deciding whether your local reporting needs a proper semantic layer — and designing it to scale without being a maintenance burden — is the kind of work I do with data teams. If you’re considering this for your own benefit, check out how my Power BI consulting and training engagements work, or give us a call and we’ll talk it through.
Frequently asked questions
Can Power BI Report Server connect to an on-premises SSAS Tabular model?
Yes. Report Server supports direct connections to SSAS Tabular, and when Power BI Desktop and SSAS are both on-premises, a gateway is not required. The report queries the model directly and displays the most recent processed data.
Why can’t I use shared datasets like I do in Power BI Services?
Reports Server does not support connecting reports to .pbix datasets published as shared sources. That capability is for the Service only. On-premises, the SSAS Tabular model is a supported way to provide multiple reports one layer of orchestrated semantics.
Where is row level security implemented with direct connections?
In the SSAS model, not the report. Roles are defined in Analysis Services, and user identities are passed through EffectiveUserName so that the model implements what everyone can see. Define it once and every connected report will inherit it.
Do I need SQL Server Enterprise to run Power BI Report Server?
Not in SQL Server 2025. Now available with Standard edition and no Software Assurance requirements. In SQL Server 2022 and earlier, you still need Enterprise with SA enabled, Power BI Premium, or Fabric F64+. A Power BI Pro license is required to publish in any way.
Useful Links
Data Platform Accelerator
Why Your AI Output Is Inconsistent (And Nine Frameworks That Fix It)
Data-Driven Storytelling with Power BI
PakarPBN
A Private Blog Network (PBN) is a collection of websites that are controlled by a single individual or organization and used primarily to build backlinks to a “money site” in order to influence its ranking in search engines such as Google. The core idea behind a PBN is based on the importance of backlinks in Google’s ranking algorithm. Since Google views backlinks as signals of authority and trust, some website owners attempt to artificially create these signals through a controlled network of sites.
In a typical PBN setup, the owner acquires expired or aged domains that already have existing authority, backlinks, and history. These domains are rebuilt with new content and hosted separately, often using different IP addresses, hosting providers, themes, and ownership details to make them appear unrelated. Within the content published on these sites, links are strategically placed that point to the main website the owner wants to rank higher. By doing this, the owner attempts to pass link equity (also known as “link juice”) from the PBN sites to the target website.
The purpose of a PBN is to give the impression that the target website is naturally earning links from multiple independent sources. If done effectively, this can temporarily improve keyword rankings, increase organic visibility, and drive more traffic from search results.
