Black Friday50% off your first month on any monthly plan with EARLY50 See plans
All 33 lessons
  1. Start here: cloud and data 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. The three languages: SQL, PySpark and KQL side by side
    6. 6. Getting data in: the map of Fabric tools
  2. Store, ingest and transform batch data (exam area 2, 30-35%)

    1. 7. Choosing a data store and a transformation tool
    2. 8. Shortcuts and mirroring: use data without copying it
    3. 9. Ingest data with pipelines and Copy job
    4. 10. Transform with PySpark and SQL: join, denormalize, aggregate
    5. 11. Messy data: duplicates, missing values and late arrivals
    6. 12. Full and incremental loads, and loading a star schema
  3. Orchestrate and stream (exam areas 1 and 2)

    1. 13. Pipeline or notebook? Choosing how to orchestrate
    2. 14. Schedules and event-based triggers
    3. 15. Parameters and dynamic expressions
    4. 16. Streaming in Fabric: Eventstreams, Spark streaming and KQL
    5. 17. KQL and windowing functions for real-time data
  4. Set up and secure a Fabric solution (exam area 1, 30-35%)

    1. 18. Workspace settings: Spark, domains, OneLake and data workflows
    2. 19. Version control with Git and database projects
    3. 20. Deployment pipelines: development, test and production
    4. 21. Who can see what: workspace roles and item permissions
    5. 22. Fine-grained security: rows, columns, objects, files and masking
    6. 23. Governance: sensitivity labels and endorsement
  5. Monitor, fix and optimize (exam area 3, 30-35%)

    1. 24. Monitoring hub, alerts and Activator
    2. 25. Fixing errors in pipelines, dataflows and notebooks
    3. 26. Fixing errors in Eventhouse, Eventstream and T-SQL
    4. 27. Optimize lakehouse tables: V-Order, OPTIMIZE, VACUUM and partitions
    5. 28. Optimize Spark, pipelines and warehouses
    6. 29. Optimize eventstreams, eventhouses and queries
  6. Exam practice and final review

    1. 30. Exam day: question types, timing and how to think
    2. 31. Mock exam 1
    3. 32. Mock exam 2
    4. 33. Final review: every decision on one page
See the leaderboard

14 min

Governance: sensitivity labels and endorsement

Label sensitive items and mark trusted ones so people find the right data.

By the end of this lesson you can

  • Apply a sensitivity label to a Fabric item and predict where it flows
  • Choose between Promoted, Certified and Master data for an item
  • Say who can apply each endorsement badge
  • Find labels and badges in the OneLake catalog

From earlier lessons · 1 of 2

Support agents must see only the last four digits of a card number. Finance must see all of it. What fits best in a Warehouse?

Pick one answer.

From earlier lessons · 2 of 2

Which two objects do you create for row-level security in a Warehouse?

Pick one answer.

An auditor visits Northwind Rides. She asks which Fabric items hold customer payment data, and how anyone would know. Meanwhile the ops team has built reports on three different copies of the trips table. Nobody knows which copy to trust. Last lesson you controlled who sees what. This lesson you tell people what each item is.

[4]

Sensitivity labels: a tag that says how sensitive

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. Purview is Microsoft's compliance service. Your security team creates and publishes the labels there. Fabric only applies them.

To apply a label you need two things:

  • A Power BI Pro or Premium Per User license.
  • Edit permission on the item.

The label must also be published to you in Purview. If it isn't, it shows greyed out.

You apply a label 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.

[209][210]

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

[209]

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, or download a .pbix file, and the label goes along. Export to .csv or .txt does not carry protection.

[210]

Inheritance: labels flow downstream

Exam depth: know it cold.

Inheritance means a label copies itself to items built from a labeled item. You don't label every item by hand. It happens three ways:

  • On creation. A Notebook, Pipeline or shortcut created from a labeled Lakehouse gets the Lakehouse's label.
  • Downstream. You change the label on a parent item. Its existing downstream items get the new label too.
  • On a new connection. You connect a General Notebook to a Confidential Lakehouse. The Notebook becomes Confidential.

The tenant setting Automatically apply sensitivity labels to downstream content makes downstream inheritance fully automatic. It's on by default. When it's off, Fabric asks you to consent first.

[210][211][212]

Rendering diagram…
One label on the Lakehouse flows down to the items built from it. A label someone set by hand stays put.

[210][212]

[210][211][212]

You are a data engineer at Northwind Rides. A payments Lakehouse is labeled Confidential. Twelve downstream items inherited that label. An analyst manually set one report to General. You change the Lakehouse to Highly Confidential, with fully automated inheritance on. Which items change?

Pick one answer.

[211][212]

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. Endorsed items show the badge and often appear first in lists.

BadgeWhat it meansWho can apply it
PromotedThe creator thinks it's ready to share.Anyone with write permission on the item.
CertifiedIt meets the organization's quality bar.Reviewers the Fabric admin authorizes.
Master dataIt's the single source of truth, like a customer list.Users the Fabric admin authorizes.

The admin names certifiers in the Certification tenant setting, using security groups. Authorized users also need write permission on the item.

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: self-check is Promoted, an official review is Certified, the one reference copy is Master data.

[213][214][215][216]

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

[213]

[213][214]

Match

Match each Northwind Rides item to the badge it should get

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

[213]

Three trips tables walk into a meeting. Only one has a badge. Guess which one finance uses. Picture: Sticky-note sketch style: three yellow sticky notes on a corkboard, each with a simple cartoon table drawn in marker.

Label or badge? They answer different questions

Exam depth: know it cold.

Sensitivity labelEndorsement
AnswersHow sensitive is this?Can I trust this?
Comes fromMicrosoft Purview.Fabric itself.
Spreads to other itemsYes, by inheritance.No.
Can control accessYes, with a protection policy.No.

An item can have both. A payments Lakehouse might be Confidential and Certified at once.

Decision rule: if the requirement is about protecting data, pick a label. If it's about helping people find the right data, pick a badge.

[210][213]

Where governance shows up: the OneLake catalog

Exam depth: recognize it.

The OneLake catalog is Fabric's central place to find and govern items. You open it from the navigation pane. It has three tabs: Explore, Govern and Secure.

  • Explore lists the items you can access. It has an Endorsement column and a Sensitivity column, and you can filter by endorsement.
  • Govern shows insights such as label coverage and the share of unlabeled items. It suggests actions to fix gaps.

Admins also reach tenant settings here: Govern > Configurations > Tenant settings. That's where certification is turned on.

[215][217][218][219]

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 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 settings of the same Lakehouse.
  2. Expand the endorsement section and select Promoted.
  3. Select Apply.
  4. Open the OneLake catalog and find the item. Check its Endorsement column.

[209][214]

Exam-style practice

You are a data engineer at Northwind Rides. Only the data governance team may mark items as meeting company quality standards. You have write permission on the trips semantic model but aren't on that team. You need the model to carry that mark. What should happen?

Pick one answer.

[214][215]

You are a data engineer at Northwind Rides. Several teams keep their own station lists. Leadership names one Lakehouse table as the single source of truth for station IDs. You need people to recognize it as that. Which badge fits?

Pick one answer.

[213]

You are a data engineer at Northwind Rides. A Lakehouse holds customer payment data. Every notebook and pipeline built from it must be flagged as sensitive, with the least manual effort. What should you do?

Pick one answer.

[210]

FlashcardsIndex cardsFlashcards ⚡

Card 1 of 14

[209][210][211][213][215][217]

Worth keeping

  1. Sensitivity labels come from Microsoft Purview; you apply them to items with edit permission.
  2. Labels flow downstream, but never overwrite a manual label or a stricter one.
  3. Promoted needs write permission; Certified and Master data need an admin-authorized user.
  4. Labels protect data; endorsement badges help people find data they can trust.
  5. The OneLake catalog shows each item's label and badge in one list.

On the job

Back to the auditor at Northwind Rides. You label the payments Lakehouse Confidential. The notebooks and pipelines you build from it pick up the label. When she asks which items hold payment data, the answer is a filter in the catalog.

Next, the three trips tables. You agree with ops which one is correct. You promote it and request certification from the data office. Once it's certified, the ops team builds every new report on it. The other two copies get deleted.

Once a month, you open the Govern tab and check label coverage. Unlabeled items in the rides workspaces go on your to-do list.

[210][214][219]

Your items are secured, labeled and badged. Then at 6 a.m. the certified trips model fails to refresh, and nobody notices until the ops meeting. Next lesson: where to watch every run, and how to get alerted first.

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 (12)

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

  1. [4]Microsoft Learn: Study Guide for Exam DP-700
  2. [209]Microsoft Learn: Apply sensitivity labels to Fabric items
  3. [210]Microsoft Learn: Information protection in Microsoft Fabric
  4. [211]Microsoft Learn: Sensitivity label downstream inheritance
  5. [212]Microsoft Learn: Sensitivity label inheritance upon update and relationship changes in Microsoft Fabric
  6. [213]Microsoft Learn: Endorsement overview
  7. [214]Microsoft Learn: Endorse Fabric and Power BI items
  8. [215]Microsoft Learn: Enable item certification
  9. [216]Microsoft Learn: Enable master data endorsement
  10. [217]Microsoft Learn: OneLake catalog overview
  11. [218]Microsoft Learn: Find and explore data in the OneLake catalog
  12. [219]Microsoft Learn: Govern and manage your Fabric data estate with the OneLake catalog