Launch Deal · 50% off 1st month ·

1.7 — XMLA Endpoint and Reusable Assets

DP-600 Domain 1 · Skill 1.7

What You Need to Know

Enterprise semantic models are often managed outside Power BI Desktop, through the XMLA endpoint. Teams also save time by reusing templates, data source files and shared models instead of rebuilding them.

The XMLA endpoint

Fact Detail
What it is The Analysis Services protocol endpoint of a workspace on a Fabric, Premium or PPU capacity. Tools treat it as an Analysis Services server
Connection string powerbi://api.powerbi.com/v1.0/myorg/<Workspace Name>, with the workspace name URL-encoded
Read-only (default) Query models and read their metadata: DAX Studio, SSMS, Excel (Analyze in Excel), paginated reports, third-party BI tools
Read-write A capacity admin sets the capacity's XMLA Endpoint setting to Read Write. Then you can deploy and change models with Tabular Editor, SSMS, Visual Studio or TMSL/TOM scripts
Typical write tasks Deploy a model, add partitions, refresh single tables or partitions, script role definitions and OLS, edit calculation groups, automate with PowerShell
Prerequisites A capacity or PPU workspace, the tenant setting allowing XMLA endpoints, and Build permission (or workspace access) on the model
Side effects After a model is changed through XMLA, you can no longer download it as a .pbix. Large semantic model storage format speeds up XMLA writes

Querying through XMLA (for example running DAX queries in DAX Studio or SSMS) is how you test measures and investigate performance against the published model.

Reusable assets

Asset What it contains Use it for
Power BI template (.pbit) Report pages, model, queries and parameters, but no data A standard starting point: corporate layout and theme, a date table, common measures. Opening it prompts for the parameter values
Power BI data source file (.pbids) Only a connection (source type, server, database) Giving report authors the right connection without them typing server names
Shared semantic model One published, ideally certified, model that many reports connect to (live connection) One version of the truth. Authors need Build permission
Report theme (.json) Colors, fonts and visual defaults Consistent branding (lesson 1.1)
Composite model on a shared model Local tables or measures added on top of a published model (DirectQuery for Power BI semantic models) Extending a certified model without copying it

Key Concept: XMLA is read-only by default. Enabling read-write in the capacity settings opens up enterprise tooling. Reuse comes in increasing scope: .pbids shares a connection, .pbit shares a whole report starting point, and a shared semantic model shares the model itself.

Exam Traps

  • Trying to deploy a model with Tabular Editor while the capacity's XMLA endpoint is read-only
  • Expecting a .pbit file to contain data
  • Expecting a .pbids file to contain queries or visuals
  • Planning to download a model as a .pbix after changing it through XMLA
  • Copying a shared model into every report instead of live-connecting with Build permission

Check your understanding

Practice Scenario

You try to deploy changes to a published semantic model from Tabular Editor through the workspace's XMLA endpoint, and you get an error saying that write operations aren't allowed. The workspace is on a Fabric capacity. What should be changed?

Report issue

Log in to save your progress.

You've finished the free part of DP-600

The lessons stay free. Pro unlocks the other 17 DP-600 practice scenarios and the 50-question timed mock exam, plus everything for every other exam.

See plans

Launch Deal: first month €9.95, then €19.90/month. Enter code LAUNCH50 at checkout. Ends 1 December.

Cancel anytime. Or €199 a year, which saves 17%.

Not sure yet? Try 10 free mock exam questions.