πŸ”’ Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided DP-600 Domain 1
Domain 1 β€” Module 7 of 7 100%
7 of 29 overall

DP-600 Study Guide

Domain 1: Maintain a Data Analytics Solution

  • Workspace Access Controls
  • Row-Level & Object-Level Security
  • Sensitivity Labels & Endorsement
  • Git Version Control in Fabric
  • Deployment Pipelines: Dev β†’ Test β†’ Prod
  • Impact Analysis & Dependencies
  • XMLA Endpoint & Reusable Assets

Domain 2: Prepare Data

  • Microsoft Fabric: The Big Picture Free
  • Lakehouses: Your Data Foundation Free
  • Warehouses in Fabric Free
  • Choosing the Right Data Store Free
  • Data Connections & OneLake Catalog
  • Shortcuts & OneLake Integration
  • Ingesting Data: Dataflows Gen2 & Pipelines
  • Star Schema Design Free
  • SQL Objects: Views, Functions & Stored Procedures
  • Transforming Data: Reshape & Enrich
  • Data Quality & Cleansing
  • Querying with SQL
  • Querying with KQL
  • Querying with DAX

Domain 3: Implement and Manage Semantic Models

  • Semantic Models: Storage Modes
  • Relationships & Advanced Modeling
  • DAX Essentials: Variables & Functions
  • Calculation Groups & Field Parameters
  • Large Models & Composite Models
  • Direct Lake Mode
  • DAX Performance Optimization
  • Incremental Refresh

DP-600 Study Guide

Domain 1: Maintain a Data Analytics Solution

  • Workspace Access Controls
  • Row-Level & Object-Level Security
  • Sensitivity Labels & Endorsement
  • Git Version Control in Fabric
  • Deployment Pipelines: Dev β†’ Test β†’ Prod
  • Impact Analysis & Dependencies
  • XMLA Endpoint & Reusable Assets

Domain 2: Prepare Data

  • Microsoft Fabric: The Big Picture Free
  • Lakehouses: Your Data Foundation Free
  • Warehouses in Fabric Free
  • Choosing the Right Data Store Free
  • Data Connections & OneLake Catalog
  • Shortcuts & OneLake Integration
  • Ingesting Data: Dataflows Gen2 & Pipelines
  • Star Schema Design Free
  • SQL Objects: Views, Functions & Stored Procedures
  • Transforming Data: Reshape & Enrich
  • Data Quality & Cleansing
  • Querying with SQL
  • Querying with KQL
  • Querying with DAX

Domain 3: Implement and Manage Semantic Models

  • Semantic Models: Storage Modes
  • Relationships & Advanced Modeling
  • DAX Essentials: Variables & Functions
  • Calculation Groups & Field Parameters
  • Large Models & Composite Models
  • Direct Lake Mode
  • DAX Performance Optimization
  • Incremental Refresh
Domain 1: Maintain a Data Analytics Solution Premium ⏱ ~12 min read

XMLA Endpoint & Reusable Assets

Deploy and manage semantic models programmatically. XMLA endpoints, .pbit templates, .pbids files, and shared semantic models.

Enterprise model management

β˜• Simple explanation

Think of the XMLA endpoint as a back door to your semantic model.

Power BI Desktop is the front door β€” click and design. The XMLA endpoint is the maintenance entrance β€” powerful tools (SSMS, Tabular Editor, DAX Studio, ALM Toolkit) connect directly to manage the model programmatically. Scripted deployments, automated testing, and bulk changes all use XMLA.

Reusable assets (.pbit templates, .pbids files, shared models) are like recipe cards β€” standardised starting points that save teams from rebuilding the same thing every time.

The XMLA endpoint exposes Power BI semantic models via the Analysis Services protocol. It supports read operations (query models, refresh status, metadata inspection) and read/write operations (deploy models, process tables, modify objects). XMLA read/write requires Premium or Fabric capacity.

Reusable assets include: .pbit (Power BI Template β€” report + model without data), .pbids (data source connection definition), and shared semantic models (centralised models that multiple reports connect to).

XMLA endpoint

What can you do with XMLA?

OperationReadRead/Write
Query the model with DAXYesYes
View model metadataYesYes
Check refresh statusYesYes
Deploy a model (overwrite)NoYes
Process (refresh) tablesNoYes
Modify model objects (add measures, tables)NoYes
Script and automate deploymentsNoYes

Tools that use XMLA

ToolPrimary Use
SSMS (SQL Server Management Studio)Model management, scripting, backup
Tabular EditorModel editing, calculation groups, OLS/CLS, deployment
DAX StudioDAX query analysis and performance tuning
ALM ToolkitModel comparison and selective deployment
PowerShell (Invoke-ASCmd)Automated scripting and CI/CD

Enabling XMLA read/write

  1. In the Fabric admin portal, verify XMLA read/write is enabled for the capacity
  2. The workspace must be on Premium or Fabric capacity (not shared)
  3. Connect using the workspace connection URL: powerbi://api.powerbi.com/v1.0/myorg/{workspace-name}
πŸ’‘ Scenario: Raj automates nightly model updates

Raj at Atlas Capital uses PowerShell with the XMLA endpoint to automate nightly model management:

  1. Refresh specific tables β€” only fact_trades (not slow-changing dimensions)
  2. Add daily partition β€” create a new partition for today’s data
  3. Validate measures β€” run a set of DAX test queries and check results
  4. Alert on failure β€” send a Teams notification if any step fails

All of this runs as a scheduled PowerShell script β€” no manual intervention, no UI clicks.

Reusable assets

.pbit β€” Power BI Template

A .pbit file contains a report layout and semantic model definition without data. When a user opens it, they are prompted for connection parameters.

Use CaseHow
Standardised reportsCreate a template with company branding, standard visuals, common measures
Client onboardingJames creates a .pbit for each report type; new clients open and connect to their data
TrainingDistribute templates for workshops β€” students connect to sample data

.pbids β€” Data Source file

A .pbids file defines a connection to a specific data source. Double-click it in Windows to open Power BI Desktop with the connection pre-configured.

{
  "version": "0.1",
  "connections": [
    {
      "details": {
        "protocol": "tds",
        "address": {
          "server": "your-warehouse.datawarehouse.fabric.microsoft.com",
          "database": "your-database"
        }
      }
    }
  ]
}

Shared semantic models

A shared semantic model is a single, centrally managed model that multiple reports connect to:

  • One model, many reports β€” avoids data duplication and measure inconsistency
  • Build permission β€” report creators need Build permission on the shared model
  • Cross-workspace β€” reports in different workspaces can connect to the same model
  • Single source of truth β€” one place to define measures, relationships, and business logic
πŸ’‘ Exam tip: Shared models and Build permission

The exam frequently tests the shared model pattern:

  • A shared semantic model is published to a workspace
  • Report creators in OTHER workspaces connect to it using the Power BI semantic models connector as a data source
  • They need Build permission on the model (granted via item sharing, not workspace roles)
  • Changes to the shared model automatically reflect in all connected reports
Question

What is the XMLA endpoint?

Click or press Enter to reveal answer

Answer

An Analysis Services protocol endpoint that exposes Power BI semantic models for programmatic access. Tools like SSMS, Tabular Editor, DAX Studio, and PowerShell connect via XMLA for management, deployment, and querying. Read/write requires Premium or Fabric capacity.

Click to flip back

Question

What is a .pbit file?

Click or press Enter to reveal answer

Answer

A Power BI Template β€” contains the report layout and model definition WITHOUT data. Users open it and provide connection parameters. Used for standardised reports, client onboarding, and training.

Click to flip back

Question

What is a shared semantic model?

Click or press Enter to reveal answer

Answer

A centrally managed model that multiple reports connect to. One model, many reports. Ensures consistent measures and business logic. Report creators need Build permission to create reports on top of it.

Click to flip back

Knowledge Check

Raj at Atlas Capital needs to automate nightly refresh of specific tables in a semantic model and add new daily partitions. Which approach is correct?

Knowledge Check

James at Summit Consulting wants 20 business analysts to build their own reports using a centrally managed semantic model. The analysts should NOT have access to the underlying workspace. What does James need?

🎬 Video coming soon


Congratulations! You have completed all 29 modules of the DP-600 study guide. Head to the practice questions to test your knowledge.

← Previous

Impact Analysis & Dependencies

Next β†’

Microsoft Fabric: The Big Picture

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.