Skip to end of metadata
Go to start of metadata

Rough notes only at this time - not fully vetted because I do not have Power Bi Report Server installed anywhere right now. Stephen Fuqua  




  • SQL Server Analysis Services (SSAS) 2016 or newer
    • During install process, be sure to select the "Tabular Data Model" mode.
    • If you already have SSAS with OLAP mode, then you can either switch (destroying your OLAP cubes) or install a second instance.
  • Power Bi Report Server


Overall process probably should be:

  1. Deploy the Tabular Data Model
    1. Schedule refresh appropriately
    2. Configure Active Directory integration for row-level security
  2. Deploy Power Bi

Tabular Data Model


Two options for deployment:

Even for the second case you have to start from within Visual Studio. For the command prompt option, you build the solution in Visual Studio, and it creates output in the Bin directory. These output files are then used for the deployment.


Scheduling a refresh is most easily done using SQL Server Agent. See for example How to automate SSAS tabular model processing in SQL Server 2016.


There are two Roles in this model: "Role" and "StudentRecordsAuth". Customize the membership as appropriate. The role named "Role" is a leftover that doesn't seem to be required. To customize after deployment, connect to SSAS using SQL Server Management Studio and then double click on the role.

The row-level security expects to match up user email addresses to records in the edfi.Staff  table. These roles in Tabular Data Model are at a looser grain than the detailed row-level security built into the Analytics Middle Tier, but are still important. All users who are going to access the Power Bi dashboards need to have read permission in this Role.

Power Bi

See Step 4: Save your report to the report server for deployment using Power Bi Desktop, or see this thread for a discussion and tips on how to automate the deployment.

  • No labels