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

18 min

Who can see what: workspace roles and item permissions

Assign the right workspace role or item permission with least privilege.

By the end of this lesson you can

  • Pick the lowest workspace role that covers a person's tasks
  • Share one Lakehouse or Warehouse with the right item permissions
  • Choose Read, Build, Write or Reshare on a semantic model
  • Decide between a workspace role, an item share and an app

From earlier lessons · 1 of 2

A Juniper Coffee report uses Direct Lake on OneLake. A query exceeds the capacity's guardrails. What happens?

Pick one answer.

From earlier lessons · 2 of 2

A Juniper report page is slow. Which Power BI Desktop tool shows how long each visual's DAX query takes?

Pick one answer.

Juniper Coffee's analytics workspace holds the sales Lakehouse, the finance Warehouse and the sales semantic model. A new analyst must build reports on the model, but not change it. Finance wants to query the Warehouse with T-SQL, nothing more. And 120 store managers need the sales report. Someone suggests making everyone Admin. You need a better plan.

[6]

Three layers of access

Exam depth: know it cold.

Fabric controls access in layers, from broad to narrow.

  1. Workspace roles apply to every item in a workspace.
  2. Item permissions apply to one item you share, without workspace access.
  3. Fine-grained security limits what someone sees inside an item: rows, columns, tables or folders.

The first two decide what you can do to items. The third decides which data you see. This lesson covers layers 1 and 2. The next lesson covers layer 3.

[268][274]

Rendering diagram…
Broad to narrow: a role covers the workspace, a share covers one item, fine-grained security covers part of an item.

[268]

The four workspace roles

Exam depth: know it cold.

A workspace role is a set of rights over a whole workspace. There are four: Admin, Member, Contributor and Viewer. If someone gets roles through several groups, the highest one wins.

CapabilityAdminMemberContributorViewer
Update or delete the workspace.✅❌❌❌
Add or remove anyone, including Admins.✅❌❌❌
Connect the workspace to Git.✅❌❌❌
Add people as Member or lower.✅✅❌❌
Share items, allow resharing, publish an app.✅✅❌❌
Create, edit and delete items.✅✅✅❌
Build reports on the workspace's models.✅✅✅❌
Read Lakehouse data with Spark (ReadAll).✅✅✅❌
Query Lakehouse and Warehouse with T-SQL (ReadData).✅✅✅✅
View and interact with reports.✅✅✅✅

[265][271]

[265][271][275]

Match

Match each Juniper Coffee task to the lowest workspace role that can do it

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

[265][271]

You are an analytics engineer at Juniper Coffee. A new BI developer must create and edit semantic models and reports in the analytics workspace. They must not add people, share items or publish the app. You need least privilege. Which role should you assign?

Pick one answer.

[271]

Least privilege: hand over the one item they need, not the keys to the whole workspace. Picture: Vintage instruction-manual drawing: a line-art barista hands a single small key to a smiling customer, while a huge ring of keys hangs on a

Item permissions: share one item

Exam depth: know it cold.

Sharing grants item permissions: rights on one item, with no access to the rest of the workspace. Admins and Members can share by default. Contributors and Viewers need Reshare permission first.

Permission (name in the share dialog)What it allows
Read (always included).Find and open the item. Connect to its SQL endpoint, but query nothing.
ReadData (Read all with SQL analytics endpoint).Query every table and view with T-SQL, read-only.
ReadAll (Read all with Apache Spark).Read the data with Spark, OneLake APIs or the Lakehouse explorer.
Build.Build new content on a semantic model.
Reshare (Share).Share onward, up to your own permissions.
Write (Edit).Change the item. Granted by roles or on some items, such as semantic models.

[267][274][275]

The Manage permissions page of a Warehouse. Workspace Admin and Member rows show Read, Write, Reshare, ReadData, ReadAll. A Contributor shows Read, Write, ReadData, ReadAll. Two shared users with no role show Read, ReadData, ReadAll and Read, ReadData.
Microsoft Learn, CC BY 4.0

[275]

[267][274][275]

You are an analytics engineer at Juniper Coffee. A finance analyst has no workspace role. They must query every table in the finance Warehouse with T-SQL from SQL Server Management Studio. They must not edit anything or see other items. What should you do?

Pick one answer.

[275]

Semantic model permissions: Read, Build, Write, Reshare

Exam depth: know it cold.

A semantic model has its own four permissions.

PermissionWhat it allowsAdminMemberContributorViewer
Read.Open and interact with reports on the model.✅✅✅✅
Build.Build new reports and composite models, use Analyze in Excel, query over XMLA.✅✅✅❌
Write.Republish, change the model over XMLA, select Refresh now, edit most settings.✅✅✅❌
Reshare.Grant others access to the model.✅✅❌❌

The role columns show what each workspace role gives automatically. For anyone else, an Admin or Member grants permissions on the model's Manage permissions page.

Only the model's owner can set scheduled refresh and data source credentials.

[273]

[271][273]

You are an analytics engineer at Juniper Coffee. A marketing analyst works in their own workspace. They must create new reports on the certified sales semantic model in your workspace. They must not change the model. You need least privilege. What should you grant?

Pick one answer.

[264][273]

Apps and audiences: reports for many readers

Exam depth: recognize it.

A workspace app bundles a workspace's reports into one read-only package for consumers. Admins and Members publish it. A Contributor can update an existing app only if an Admin allows it.

An app can have several audiences. Each audience is a group of users that sees its own subset of the content. App users can't open the workspace itself.

Each audience has two advanced options:

  • Allow users to share the semantic models in this app.
  • Allow users to build content with the semantic models in this app. This grants Build.

Decision rule: builders get a workspace role. Many read-only consumers get an app.

[264][271][272]

Least privilege, with groups

Exam depth: know it cold.

Assign roles and permissions to Microsoft Entra groups, not to individuals. Entra ID is Microsoft's sign-in directory. A new hire joins the group and gets the right access at once. Workspace roles accept security groups, Microsoft 365 groups, distribution lists and people.

Then ask three questions in order.

  1. Do they build or edit in this workspace? Give the lowest role that covers it, usually Contributor.
  2. Do they only need one item? Share it with ReadData, ReadAll or Build.
  3. Do they only read reports? Publish an app to their audience, or give Viewer.

Fine-grained security, such as RLS, goes on top.

[265][266][270]

Try it in Fabric

A free Fabric trial is enough. Use a workspace where you're Admin, with a Lakehouse in it.

Give a workspace role

  1. Open the workspace and select Manage access.
  2. Select Add people or groups.
  3. Enter a name or group, choose Viewer, and select Add.

Share one Lakehouse with Read and ReadData

  1. In the workspace list, select the Share icon next to your Lakehouse.
  2. Enter a person. Tick Read all with SQL analytics endpoint and leave Spark unticked. Select Grant.
  3. Select ... next to the Lakehouse, then Manage permissions. Find the person in Direct access and check their permissions.

[266][267]

Exam-style practice

You are an analytics engineer at Juniper Coffee. Regional leads have the Viewer role in the analytics workspace. They must analyze the sales semantic model in Excel PivotTables. They must not edit any item. You need least privilege. What should you do?

Pick one answer.

[271][273]

You are an analytics engineer at Juniper Coffee. 120 store managers must view the sales reports. Finance must view a different set of reports. Neither group may see work-in-progress items in the workspace. You need the least administration. What should you do?

Pick one answer.

[269][272]

FlashcardsIndex cardsFlashcards ⚡

Card 1 of 15

[265][271][272][273][274][275]

Worth keeping

  1. Admin manages the workspace, Member adds people and publishes apps, Contributor builds, Viewer reads.
  2. Share one item for one-item access: ReadData for T-SQL, ReadAll for Spark.
  3. On a semantic model, Build creates reports and Write changes the model.
  4. Many read-only consumers get an app with audiences.
  5. Grant to groups, and pick the lowest access that still works.

On the job

At Juniper Coffee you set up three Entra groups. BI Developers get Contributor on the analytics workspace. Finance Analysts get the finance Warehouse shared with ReadData. Store Managers get the sales app, with one audience for managers and one for finance.

A month later, marketing wants its own reports. You don't add them to the workspace. You grant their group Build on the sales model, and they build in their own workspace.

Each quarter you open Manage access and the model's Manage permissions page. Anyone added by name instead of by group gets moved into a group.

[270][272]

The store managers can open the sales report. But right now every manager sees every region. Next lesson: row-level security, so each manager sees only their own region's rows.

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

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. [247]Microsoft Learn: Integrate Direct Lake security
  3. [252]Microsoft Learn: Use Performance Analyzer to examine report performance
  4. [264]Microsoft Learn: Build permission for shared semantic models
  5. [265]Microsoft Learn: Roles in workspaces in Microsoft Fabric
  6. [266]Microsoft Learn: Give users access to workspaces
  7. [267]Microsoft Learn: How lakehouse sharing works
  8. [268]Microsoft Learn: Data security in OneLake
  9. [269]Microsoft Learn: Power BI implementation planning: Content distribution and sharing
  10. [270]Microsoft Learn: Power BI implementation planning: Content creator security planning
  11. [271]Microsoft Learn: Roles in workspaces in Power BI
  12. [272]Microsoft Learn: Publish a workspace app in Power BI
  13. [273]Microsoft Learn: Semantic model permissions
  14. [274]Microsoft Learn: Share items in Microsoft Fabric
  15. [275]Microsoft Learn: Share your data and manage permissions