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

A tour of Microsoft Fabric: OneLake, workspaces and items

Name every Fabric item an analytics engineer uses and how they share one copy of data.

By the end of this lesson you can

  • Explain what OneLake is and why each tenant has exactly one
  • Place tenant, capacity, workspace and item in order, and tell My workspace from a shared one
  • Tell the items that store data from the items that move it and the items that consume it
  • Say where a semantic model sits and how Direct Lake reads lake data

From earlier lessons · 1 of 3

In Fabric, what do you pay for to get compute power?

Pick one answer.

From earlier lessons · 2 of 3

What does Delta Lake add on top of Parquet files?

Pick one answer.

From earlier lessons · 3 of 3

In Juniper's star schema, which table holds the quantity and amount of each item sold?

Pick one answer.

It's your first week as an analytics engineer at Juniper Coffee. You open Fabric and see a dozen item types: Lakehouse, Warehouse, Eventhouse, Dataflow Gen2, Semantic model and more. Finance asks where their sales report will get its numbers. You can't answer until you know what each box is for.

[6]

OneLake: one lake for the whole organization

Exam depth: know it cold.

OneLake is the single data lake that every Fabric tenant gets automatically. A tenant is your organization's one instance of Fabric.

There is exactly one OneLake per tenant. You can't create a second one or delete it, and there's nothing to set up. Teams still keep their own areas inside it, so one lake doesn't mean one big mess.

OneLake stores tables in open formats, by default Delta Parquet. Every Fabric engine reads and writes that same format. So a table loaded with SQL can be read by Spark or a Power BI semantic model with no copy and no export. That's the core idea: one copy of data, many engines.

[2][36]

[8]

Tenant, capacity, workspace, item

Exam depth: know it cold.

Fabric organizes everything in four levels.

  1. Tenant: your whole organization. It owns the one OneLake.
  2. Capacity: a pool of compute inside the tenant, in one region.
  3. Workspace: a container where a team builds and shares work. Each workspace runs on one capacity and controls who can access what's inside.
  4. Item: one object you create in a workspace, such as a Lakehouse or a semantic model.

Every user also gets My workspace, a personal workspace for their own drafts. Team work belongs in a shared workspace you create, where you can add people and roles. Creating and sharing Power BI items outside My workspace needs a Pro or PPU license.

A workspace holds up to 1,000 items. Each workspace shows up as a folder in OneLake, and each item as a folder inside it.

[2][9][36][37]

Rendering diagram…
One tenant, one OneLake. Workspaces hold items, run on a capacity, and can be grouped into a domain.

[36][38]

A Fabric workspace in list view. The items list shows a Lakehouse, its SQL analytics endpoint listed under it, and a Dataflow Gen2, each with its type, owner and refresh columns.
Microsoft Learn, CC BY 4.0

[37]

Items that store data

Exam depth: know it cold. Lesson 7 teaches choosing between them in full.

Four items hold data. All of them keep it in OneLake.

  • Lakehouse: files and Delta tables in one place, written mostly with Spark, an engine that splits big jobs across many machines. Fabric adds a SQL analytics endpoint to every Lakehouse, so you can read its tables with T-SQL.
  • Warehouse: structured tables with full T-SQL. You can insert, update and delete, and run transactions across several tables.
  • Eventhouse: a store for streaming, time-stamped events. It holds one or more KQL databases, queried with KQL.
  • Mirrored database: a read-only copy of an outside database that Fabric keeps in sync. It gets a SQL analytics endpoint too.
NeedPick
Spark, files, any shape of data.Lakehouse
SQL-first team, T-SQL writes.Warehouse
Streaming events, queries in seconds.Eventhouse
Live copy of an operational database.Mirrored database

[2][12][39][40][41]

A Lakehouse open in Fabric with Tables and Files folders on the left. The Analyze data with menu is open, showing Notebook, SQL analytics endpoint and Eventhouse endpoint.
Microsoft Learn, CC BY 4.0

[12]

[12]

You are an analytics engineer at Juniper Coffee. The finance analysts know only T-SQL. They must load budget data into fact and dimension tables and update several tables in one transaction. You need to choose where they store this data. What should you use?

Pick one answer.

[2][12]

Items that move and transform data

Exam depth: recognize it. Lesson 9 teaches when to use each for loading data.

Five items move or reshape data. None of them is where data lives.

  • Dataflow Gen2: cleans and reshapes data in Power Query, a low-code, point-and-click editor. The analytics engineer's everyday tool.
  • Copy job: copies data from a source to a destination, in full or only what changed.
  • Pipeline (older pages say Data pipeline): runs a series of steps in order, on a schedule or when an event happens.
  • Notebook: a page where you write and run code, usually PySpark.
  • Eventstream: captures live events and routes them to an Eventhouse, a Lakehouse or an alert, without code.

Decision rule: no-code reshaping, Dataflow Gen2. Copy only, Copy job. Code, Notebook. Many steps in order, Pipeline. Live events, Eventstream.

[2][42][43][44]

Match

Match each Juniper Coffee task to the Fabric item for it

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

[2][43][44]

Many items upstream. One semantic model at the top. Every report drinks from it. Picture: Isometric diagram cartoon: a small isometric town on a lake.

Semantic models and reports: where the data ends up

Exam depth: know it cold for the semantic model's place. Recognize it for the rest.

At the end of the line sit Power BI items, which consume data rather than store it. A semantic model defines tables, relationships and measures: saved calculations written in DAX, such as Total Sales. They build on the number columns of a fact table. Reports are the pages of charts built on top of it. One model can serve many reports, so finance and every store manager see the same numbers.

Direct Lake is a semantic model mode that reads Delta tables straight from OneLake, with no import copy. Its refresh only updates metadata, so it takes seconds. Lessons 18 and 24 teach it in full.

Three more names you'll meet in lesson 6:

  • Domain: groups workspaces by business area, such as Sales or Finance. It doesn't grant access.
  • OneLake catalog: the place to find and explore the items you can access.
  • Real-Time hub: the place to find live data streams.

[2][36][38][45]

Try it in Fabric

A free Fabric trial is enough for this.

  1. Sign in to the Fabric portal at app.fabric.microsoft.com.
  2. Select Workspaces, then + New workspace.
  3. Enter a unique Name, such as Juniper Coffee Dev.
  4. Expand Advanced. Under Workspace type, select Fabric Trial. This assigns the workspace to your trial capacity.
  5. Select Apply. The new, empty workspace opens.
  6. Select + New item, then search for and select Lakehouse.
  7. Name it juniper_lakehouse. Start with a letter, then use only letters, numbers and underscores. No spaces.
  8. Leave Lakehouse schemas selected (the default), then select Create. The Lakehouse opens with its Tables and Files folders.

Go back to the workspace list. You'll see two items: the Lakehouse and its SQL analytics endpoint, created for you.

[12][47][48]

Exam-style practice

You are an analytics engineer at Juniper Coffee. Sales data sits in large Delta tables in a Lakehouse. The finance report must show it without keeping a second copy of the data or waiting for long import refreshes. What should the semantic model use?

Pick one answer.

[2][45]

You are an analytics engineer at Juniper Coffee. The finance team wants its own data area, separate from the store operations team, with its own admins. A colleague suggests creating a second OneLake for finance. You need to meet the goal. What should you do?

Pick one answer.

[36][38]

You are an analytics engineer at Juniper Coffee. You built the sales semantic model in My workspace. Now two colleagues must help maintain it, and store managers must get reports from it. You need a setup where the team can work on it together. What should you do?

Pick one answer.

[9][37]

FlashcardsIndex cardsFlashcards ⚡

Card 1 of 15

[2][9][12][36][37][38][39][43]

Worth keeping

  1. One tenant has one OneLake, and every engine reads the same Delta tables in it.
  2. Workspaces hold items and run on a capacity; My workspace is personal, team work goes in shared ones.
  3. Lakehouse, Warehouse, Eventhouse and mirrored database store data.
  4. Dataflow Gen2, Copy job, Pipeline, Notebook and Eventstream move or reshape it.
  5. Semantic models are the destination; Direct Lake reads lake tables with no import copy.

On the job

Here's how Juniper Coffee's solution might look after a few months.

A workspace called Sales data holds the data items. The till database in Azure SQL is mirrored into Fabric, so a read-only copy stays in sync with no load jobs. A Dataflow Gen2 cleans the suppliers' price-list CSVs each night and writes them to a Lakehouse. Finance's T-SQL team keeps budgets in a Warehouse. Loyalty-app events flow through an Eventstream into an Eventhouse, where marketing queries the last hour with KQL.

A second workspace, Store reports, holds one semantic model in Direct Lake mode, built as a star schema over those tables. Finance's report and the store managers' report both read it, so everyone sees the same totals.

Both workspaces sit in a Sales domain, so people can find them in the OneLake catalog. Your job is the middle of this picture: the shaping, the model and keeping it correct.

[38][40][44][45]

Every arrow in this tour ends at a semantic model. But what's actually inside one, and what is this DAX that keeps coming up? Next lesson opens the model, the report and DAX in plain words.

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

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

  1. [2]Microsoft Learn: Fabric terminology
  2. [6]Microsoft Learn: Study guide for Exam DP-600: Implementing Analytics Solutions Using Microsoft Fabric
  3. [8]Microsoft Learn: What is Microsoft Fabric?
  4. [9]Microsoft Learn: Understand Microsoft Fabric licenses and capacity
  5. [11]Microsoft Learn: Dimensional modeling in Fabric Data Warehouse
  6. [12]Microsoft Learn: What is a lakehouse in Microsoft Fabric?
  7. [28]Microsoft Learn: Delta Lake overview
  8. [36]Microsoft Learn: What is OneLake?
  9. [37]Microsoft Learn: Workspaces in Microsoft Fabric and Power BI
  10. [38]Microsoft Learn: Fabric domains
  11. [39]Microsoft Learn: Eventhouse overview
  12. [40]Microsoft Learn: What is Mirroring in Fabric?
  13. [41]Microsoft Learn: Choose an analytical data store in Microsoft Fabric
  14. [42]Microsoft Learn: What is Data Factory in Microsoft Fabric?
  15. [43]Microsoft Learn: Quickstart: Create a Copy job
  16. [44]Microsoft Learn: Overview of Microsoft Fabric eventstreams
  17. [45]Microsoft Learn: Direct Lake overview
  18. [47]Microsoft Learn: Lakehouse tutorial: Create a Fabric workspace
  19. [48]Microsoft Learn: Create a lakehouse in Microsoft Fabric