Black Friday50% off your first month on any monthly plan with EARLY50 See plans
All 35 lessons
  1. Start here: cloud, data, Fabric and Power BI basics

    1. 1. Start here: the exam, the plan and what you already know
    2. 2. Cloud in plain words: SaaS, PaaS, IaaS and where Fabric fits
    3. 3. Data basics: files, tables, formats and the lakehouse idea
    4. 4. A tour of Microsoft Fabric: OneLake, workspaces and items
    5. 5. Power BI in plain words: semantic models, reports and DAX
  2. Prepare data: get data in (exam area 2, 45-50%)

    1. 6. Connect to data and find it: connections, gateways, OneLake catalog and Real-Time hub
    2. 7. Choosing a data store: lakehouse, warehouse or eventhouse
    3. 8. Use data without copying: shortcuts, mirroring and OneLake integration
    4. 9. Ingest data: Dataflow Gen2, pipelines, Copy job and notebooks
    5. 10. Power Query in Dataflow Gen2: filter, data types, merge and new columns
    6. 11. Messy data: duplicates, missing values and nulls
  3. Prepare data: transform and query (exam area 2)

    1. 12. Views, functions and stored procedures in T-SQL
    2. 13. Build a star schema in a lakehouse or warehouse
    3. 14. Aggregate, join and enrich: SQL and PySpark side by side
    4. 15. Query with the Visual query editor and SQL
    5. 16. Query with KQL
    6. 17. Query with DAX: DAX query view and EVALUATE
  4. Design and build semantic models (exam area 3, 25-30%)

    1. 18. Choose a storage mode: Import, DirectQuery, Direct Lake and Dual
    2. 19. Relationships: star schemas, bridge tables and many-to-many
    3. 20. DAX foundations: measures, filter context, CALCULATE and variables
    4. 21. DAX functions the exam tests: iterators, table filters, windows and information functions
    5. 22. Calculation groups, dynamic format strings and field parameters
    6. 23. Composite models and large semantic model storage format
  5. Optimize models, then secure them (exam areas 3 and 1)

    1. 24. Direct Lake in depth: fallback, refresh and the two flavors
    2. 25. Incremental refresh for semantic models
    3. 26. Faster reports and DAX: finding and fixing slow queries
    4. 27. Who can see what: workspace roles and item permissions
    5. 28. Fine-grained security: rows, columns, objects and files
    6. 29. Governance: sensitivity labels and endorsement
  6. Lifecycle, then exam practice (exam area 1)

    1. 30. Version control: Git integration and Power BI projects (.pbip)
    2. 31. Deployment pipelines and impact analysis
    3. 32. XMLA endpoint and reusable assets: .pbit, .pbids and shared semantic models
    4. 33. Mock exam 1
    5. 34. Final review and exam day: every decision on one page
    6. 35. Mock exam 2
See the leaderboard

15 min

Governance: sensitivity labels and endorsement

Apply sensitivity labels to Fabric items and endorse trusted items.

By the end of this lesson you can

  • Apply a sensitivity label and predict where it flows
  • Choose between Promoted, Certified and Master data for an item
  • Name who can apply each badge and each label
  • Tell a governance need from a security need

From earlier lessons · 1 of 2

A Juniper manager has the Contributor role and sits in a dynamic RLS role. Why does she see every region?

Pick one answer.

From earlier lessons · 2 of 2

Which feature hides a whole column, and its name, from a semantic model role?

Pick one answer.

An auditor visits Juniper Coffee. She asks which Fabric items hold loyalty members' personal data, and how anyone would know. Meanwhile, finance has built reports on three different sales models. Nobody can say which one is right. Last lesson you controlled who sees which rows. This lesson you tell people what each item is.

[6]

Sensitivity labels: how sensitive is this item?

Exam depth: know it cold.

A sensitivity label is a tag on an item that says how sensitive its data is, such as General or Confidential.

Labels come from Microsoft Purview Information Protection, Microsoft's compliance service. Your security team creates and publishes them there. Fabric only applies them.

To apply a label you need:

  • A Power BI Pro or Premium Per User (PPU) license.
  • Edit permission on the item.
  • The label published to you in Purview. Otherwise it shows greyed out.

Apply it in one of two places. Select the sensitivity indicator in the item's header, or open the item's settings and use the sensitivity section.

[284][289][290]

A Lakehouse header with the Confidential sensitivity indicator selected. The flyout shows a Sensitivity drop-down set to Confidential and a note that the label is applied to downstream items created from this Lakehouse.
Microsoft Learn, CC BY 4.0

[284]

A label on its own is information. It controls access only when the security team links it to a Purview protection policy. Then the policy decides who can open the item.

Labels also travel with data in some exports:

  • Export to Excel, PDF or PowerPoint.
  • Analyze in Excel.
  • Download of a .pbix file.

Export to .csv or .txt carries no label and no protection.

[290]

Inheritance: labels flow downstream

Exam depth: know it cold.

Label inheritance means a label copies itself to related items, so you don't label each one by hand.

  • On creation. A report built on a labeled semantic model gets the model's label. So does a Notebook created from a labeled Lakehouse.
  • Downstream. Change the label on a parent, and its existing reports and dashboards follow.
  • From data sources. An Import model on a labeled Azure SQL Database inherits that label on refresh.

The tenant setting Automatically apply sensitivity labels to downstream content makes downstream inheritance fully automatic. It's on by default. When it's off, the user ticks a consent checkbox instead.

[290][291][292]

Rendering diagram…
A label flows from the source down to the reports. A label someone set by hand stays put.

[290][291]

[290][291][292]

You are an analytics engineer at Juniper Coffee. The sales semantic model is labeled Confidential. Twelve reports inherited that label. An analyst set one report to General by hand. You change the model to Highly Confidential, with fully automated inheritance on. Which reports change?

Pick one answer.

[291]

Exam depth: recognize it.

A Fabric admin controls labels in the Information protection tenant settings: OneLake catalog > Govern > Configurations > Tenant settings.

Setting or policyWhat it does
Allow users to apply sensitivity labels for content.Turns labels on, for everyone or chosen groups.
Apply sensitivity labels from data sources to their data in Power BI.Turns on inheritance from data sources.
Automatically apply sensitivity labels to downstream content.Fully automated downstream inheritance.
Default label (Purview policy).New or edited items get a label automatically.
Mandatory label (Purview policy).Users can't save without a label. Fully supported for Power BI items only.

[289][290]

Endorsement: Promoted, Certified, Master data

Exam depth: know it cold.

Endorsement puts a badge on an item so people can find content they can trust.

BadgeWhat it meansWho can apply it
Promoted.The creator thinks it's ready to share and reuse.Anyone with write permission on the item.
Certified.It meets the organization's quality bar.Reviewers the Fabric admin authorizes, with write permission.
Master data.Core, single-source-of-truth data, like a product list.Users the Fabric admin authorizes, with write permission.

You can promote or certify any item except Power BI dashboards. Master data fits only items that hold data, such as a Lakehouse or semantic model.

Decision rule: the creator's own signal is Promoted, an official review is Certified, and the one reference copy is Master data.

[285][286][287][288]

An item list with an Endorsement column showing Master data, Certified and Promoted badges, next to a Sensitivity column with labels such as Highly Confidential and Public.
Microsoft Learn, CC BY 4.0

[287]

Certified and Master data work only after a Fabric admin turns them on:

  • Certification tenant setting: the admin lists security groups of certifiers. Named users aren't accepted. The admin can let domain admins set their own certifiers.
  • Endorse master data (preview) tenant setting: the admin picks the whole organization or chosen security groups.

Not authorized? In the item's settings the Certified or Master data button is greyed out. Select How do I get content certified to request it.

When you promote or certify a semantic model, a Make discoverable box may appear. It lets people without access find the model and request access.

[285][286][288]

Match

Match each Juniper Coffee item to the badge it should get

Pick an item on the left, then its match on the right.

[287]

Three sales models walk into a finance meeting. Only one has a badge. Guess which one gets used. Picture: Movie-poster parody, illustrated style: three cartoon database cylinders stand like heroes on a poster.

Label, badge or security? Three different questions

Exam depth: know it cold.

Sensitivity labelEndorsementRLS, OLS, roles
Answers.How sensitive is it?Can I trust it?Who may see it?
Comes from.Microsoft Purview.Fabric.Fabric and the model.
Spreads to other items.Yes, by inheritance.No.No.
Controls access.Only with a protection policy.No.Yes.

An item can carry all three. The sales model might be Confidential, Certified and secured with RLS.

The OneLake catalog shows the first two: its items list has an Endorsement column and a Sensitivity column.

Decision rule: flag data, use a label. Point people to trusted data, use a badge. Restrict data, use security.

[73][287][290]

Try it in Fabric

Labels appear only if your organization publishes them in Purview. Promotion works on any trial.

Apply a label

  1. Open a semantic model or Lakehouse in your workspace.
  2. Select the sensitivity indicator in the item header.
  3. In the flyout, pick a label from Sensitivity.

Promote the item

  1. Open the item's settings.
  2. Expand the endorsement section, select Promoted, then Apply.
  3. Open the OneLake catalog. Select the Endorsed items filter and find your item.

[73][284][288]

Exam-style practice

You are an analytics engineer at Juniper Coffee. Only the data office may mark items as meeting company quality standards. You have write permission on the sales semantic model but aren't in the data office's security group. You need the model to carry that mark. What should you do?

Pick one answer.

[285][288]

You are an analytics engineer at Juniper Coffee. Several teams keep their own lists of products and prices. Leadership names one Lakehouse as the authoritative product list for the whole company. You need people to recognize it as that. Which badge fits?

Pick one answer.

[287]

You are an analytics engineer at Juniper Coffee. The loyalty semantic model holds members' personal data. Every report anyone builds on it must be flagged as sensitive, with the least manual effort. What should you do?

Pick one answer.

[290][291]

FlashcardsIndex cardsFlashcards ⚡

Card 1 of 14

[284][285][286][287][289][290][291][292]

Worth keeping

  1. Sensitivity labels come from Microsoft Purview; you apply them with edit permission.
  2. Labels flow to new and downstream items, but never overwrite a manual or stricter label.
  3. Promoted needs write permission; Certified and Master data need an admin-authorized user.
  4. Labels flag data, badges point to trusted data, and security restricts it.

On the job

Back to the auditor at Juniper Coffee. You label the loyalty model Confidential. Every report on it picks up the label. When she asks which items hold personal data, the answer is a filter in the catalog.

Next, the three sales models. You agree with finance which one is right. You promote it and request certification from the data office. Once it's certified, new finance reports use it, and the other two copies are retired.

Each month you open the catalog's Govern tab and check label coverage. Unlabeled items go on your to-do list.

[75][288][292]

Your items are secured, labeled and badged. Then someone edits a certified measure directly in production and breaks every finance report. Next lesson: version control with Git and Power BI projects.

Leaderboard

Loading…

50 XP for each lesson you finish, 10 for each right answer. Names show only for learners who turn on Show me on leaderboards.

Sources for this lesson (14)

Each fact in the lesson is marked with the number of the page it comes from.

  1. [6]Microsoft Learn: Study guide for Exam DP-600: Implementing Analytics Solutions Using Microsoft Fabric
  2. [73]Microsoft Learn: Find and explore data in the OneLake catalog
  3. [75]Microsoft Learn: Govern and manage your Fabric data estate with the OneLake catalog
  4. [209]Microsoft Learn: Row-level security (RLS) with Power BI
  5. [279]Microsoft Learn: Object-level security (OLS)
  6. [284]Microsoft Learn: Apply sensitivity labels to Fabric items
  7. [285]Microsoft Learn: Enable item certification
  8. [286]Microsoft Learn: Enable master data endorsement
  9. [287]Microsoft Learn: Endorsement overview
  10. [288]Microsoft Learn: Endorse Fabric and Power BI items
  11. [289]Microsoft Learn: Information protection tenant settings
  12. [290]Microsoft Learn: Information protection in Microsoft Fabric
  13. [291]Microsoft Learn: Sensitivity label downstream inheritance
  14. [292]Microsoft Learn: Sensitivity label inheritance from data sources