Home Course home Curriculum Learner dashboard Skill tree Business projects Datasets Final project
🧭 Module 0 · Data Analytics & Power BI Orientation Beginner LESSON 02 / 72

What Is Power BI? Desktop, Service & the Ecosystem

26 min 5 quiz questions 1 practical challenge 5 syllabus topics

“Power BI” is not one product. It is a family of applications and services that share a name, and a great deal of beginner confusion comes from not knowing which one someone is talking about. This lesson draws the map precisely, so that for the rest of the course you always know which component you are working in.

Lesson 2 of 72 · Data Analytics & Power BI Orientation 3%
01

Learning Objective

Power BI spans a desktop application, a cloud service, mobile apps, two report-authoring tools and a self-hosted server — with licensing that gates real capabilities. Knowing which is which prevents a whole class of wasted effort.

By the end of this lesson you will be able to
  • Describe what Power BI is and the problem it was built to solve
  • State precisely what Power BI Desktop does that the Power BI service cannot, and vice versa
  • Name the components of the Power BI ecosystem and what each is for
  • Explain how the licensing tiers differ and which features they gate
  • Explain accurately how Microsoft Fabric relates to Power BI
02

Why This Matters

Three concrete ways this confusion costs people time:

  • A learner spends an afternoon trying to write DAX in the browser, not realising that modelling and DAX authoring belong in Desktop. The service can edit reports, but the modelling experience lives on the desktop.
  • A team builds a beautiful report, then discovers they cannot share it with colleagues because sharing requires Pro licences (or Premium/Fabric capacity) — a constraint that should have been checked on day one.
  • Someone follows a tutorial that uses a feature their tenant has disabled, concludes their install is broken, and gives up. It was a tenant setting, not a bug.
The licensing question to ask first
Before you plan any Power BI project, find out what licences your organisation actually has. It determines whether you can share reports at all, how large your models can be, how often they can refresh, and whether AI features are even available to you. It is a five-minute question that prevents weeks of rework.
03

Concept

What Power BI is

Power BI is Microsoft's business intelligence platform. It connects to data sources, transforms and models the data, lets you write calculations over that model, build interactive reports on top, and publish them so other people can use them.

The problem it was built to solve is worth naming, because it explains the product's shape. Before tools like this, business reporting meant either (a) spreadsheets that nobody could trust or refresh, or (b) an IT ticket and a six-week wait for a static report. Power BI's design goal was to let an analyst — not a developer — build governed, refreshing, interactive reporting themselves.

Desktop vs the service — the distinction that matters most

These are two different applications with substantially different jobs. Nearly everything in this course happens in Desktop; Module 12 covers the service.

Power BI Desktop vs the Power BI service
CapabilityPower BI DesktopPower BI service (app.powerbi.com)
What it isA free Windows application you installA cloud SaaS platform in the browser
CostFreeFree tier exists; sharing needs Pro or capacity
Get data & Power QueryFull transformation experienceLimited — dataflows and some editing
Data modellingFull: relationships, hierarchies, propertiesEditing available, but Desktop is where this work belongs
Writing DAX measuresFull authoring experiencePossible, but not the practical place to build a model
Building report visualsYes — the primary authoring surfaceYes — good for edits and quick builds
Dashboards (pinned tiles)No — this concept exists only in the serviceYes
Scheduled refreshNo — refresh is manualYes — this is a core reason to publish
Sharing with othersNo — you send a fileYes — workspaces, apps, links
Row-Level SecurityDefine and test rolesAssign real users to those roles
Runs onWindows onlyAny modern browser; mobile apps for iOS/Android
The mental model
Desktop is the workshop. The service is the showroom. You build in Desktop — connect, clean, model, calculate, design. You publish to the service so it can refresh on a schedule and other people can use it. Trying to do heavy building in the showroom is the most common beginner detour.
Power BI Desktop is Windows-only. There is no native macOS or Linux version. Mac users generally run Windows in a virtual machine, use a cloud Windows desktop, or work in the service with its more limited authoring. This is a real constraint and worth planning around before you start.

The wider ecosystem

Beyond those two, several other components carry the Power BI name. You will not need all of them, but you should know they exist so you recognise them when they come up.

Licensing, stated plainly

Licensing gates real capability, so it is worth understanding at a high level even as a learner. Microsoft changes the specifics periodically — treat the shape below as reliable and verify current details and prices on Microsoft's own pricing page.

Licence tiers and what they gate
TierWhat you getKey limitation
Free (per user)Power BI Desktop in full; publish to your own My Workspace in the serviceCannot share content with other users, and cannot consume most shared content
Pro (per user)Everything in Free, plus publishing to shared workspaces, sharing, apps and collaborationEvery person who views your content also needs a Pro licence (unless capacity is in play)
Premium Per User (PPU)Pro plus larger models, more frequent refresh, paginated reports and advanced featuresViewers also need PPU — it does not open content up to Free users
Premium / Fabric capacity (per capacity)Dedicated capacity; Free users can view content in capacity-backed workspacesSubstantially higher cost; sized and managed as infrastructure
Licence names, feature boundaries and prices change. Verify against Microsoft's licensing documentation before making a purchasing or architectural decision. The one stable rule: publishing for yourself is free; sharing with others is not.

How Fabric relates to Power BI

This causes real confusion, so here it is precisely. Microsoft Fabric is an integrated analytics platform. Power BI has been brought inside it as the business intelligence workload, sitting alongside data engineering, warehousing, data science and real-time analytics, all sharing one storage layer (OneLake).

What this means for you as a learner: nothing changes about how you build a report. Desktop is still Desktop, Power Query is still Power Query, DAX is still DAX. What changes is that in a Fabric-enabled organisation your semantic model may read from a lakehouse or warehouse rather than a file or database, and some newer features (including Copilot) require Fabric capacity.

Terminology that changed
What used to be called a dataset in the Power BI service is now called a semantic model. This is the same object with a clearer name. Older documentation, tutorials and forum answers still say “dataset”, and the two terms refer to the same thing. This course uses “semantic model”, matching current Microsoft terminology.
04

Visual Explanation

How the pieces fit together. Data flows left to right; the dashed boundary marks what you do on your own machine versus what lives in the cloud.

The standard Power BI delivery path
🗄️ Data sources
🖥️ Power BI Desktop
📤 Publish
☁️ Power BI service
👥 Consumers
Which side of the line each activity sits on
ActivityWhere it happensWhy
Connect to a database or fileDesktop (or a dataflow)The connector runs where the query is authored
Clean and shape dataDesktop — Power QueryFull transformation UI; the service's is limited
Build relationshipsDesktop — Model viewModelling belongs in the authoring tool
Write DAX measuresDesktopBest authoring experience, with DAX formula bar and validation
Design report pagesDesktop (mostly)Full formatting control; the service can edit
Set a refresh scheduleServiceOnly the cloud can run something on a timer
Give someone accessServiceIdentity and permissions live in the cloud
Pin a tile to a dashboardServiceDashboards do not exist in Desktop at all
Assign users to RLS rolesServiceDesktop defines roles; the service maps real people to them
A test you can apply
Ask: does this action need to happen on a timer, or need to know who someone is? If yes, it is a service activity. If no, it is almost certainly Desktop. That heuristic resolves most “where do I do this?” questions correctly.
05

Power BI Demonstration

You have not installed anything yet — that is the next lesson but one. What you can do right now is establish which environment you are actually working with, because it determines what the rest of this course will let you do.

Determine whether you have a work or school Microsoft account
Power BI's sharing features are built on Microsoft Entra ID (formerly Azure AD). A personal outlook.com or gmail.com address cannot sign in to the Power BI service. If you only have a personal address, you can still do everything in Desktop — which is the great majority of this course.
If you have a work account, check your licence
Sign in at app.powerbi.com, open the settings gear, and look for account or licence information. It will tell you whether you are Free, Pro or PPU.
Check whether your tenant restricts features
Some organisations disable publishing to web, custom visuals, or export. If a documented feature is missing for you, a tenant setting is the most likely cause — not a broken install.
Note your Desktop version once installed
In Desktop: Help › About. Power BI Desktop updates monthly, so knowing your version makes it far easier to interpret a tutorial that does not match what you see.
app.powerbi.comSettings (gear)Manage personal storage / About
No work account? You lose almost nothing here
Modules 0 through 11 — orientation, Desktop, connecting, Power Query, modelling, all of DAX, visualisation, dashboard design, interactivity, the five business projects, and advanced optimisation — run entirely in free Power BI Desktop. Only Module 12 (the service) and parts of Module 13 (Copilot) need an organisational account. Those modules are written so you can follow them meaningfully even without one.
06

Example Dataset

This lesson is conceptual and needs no download — it uses the sample data shown inline above. The next lesson that requires a file will link it here.

You can still browse every dataset in the course from the dataset library.

07

Step-by-Step Exercise

Build yourself a one-page environment reference. It takes five minutes and you will refer back to it repeatedly.

Record your operating system
Windows 10/11 means you can install Desktop directly. macOS or Linux means you need a Windows VM, a cloud desktop, or a service-only approach — decide which now rather than at the start of Module 1.
Record your account type
Personal Microsoft account, work/school account, or none. This determines service access.
Record your licence tier if applicable
Free, Pro, PPU, or covered by capacity. Write “unknown” if you cannot find out — that is a useful thing to know too.
List which modules you can fully complete
Using the box above: essentially all of them on Desktop alone; Module 12 and part of 13 need an organisational account.
Write down your Desktop version once installed
Add it after Lesson 5. Update it when Desktop updates — it takes seconds and saves confusion.
08

Expected Result

A short reference that answers, without you having to think about it: where do I do this, and am I allowed to?

Example of a completed reference
OS: Windows 11 → Desktop installs natively ✓
Account: Work account (Microsoft 365) ✓
Licence: Pro → can publish and share ✓
Tenant restrictions: Publish to web disabled; custom visuals allowed
Desktop version: to be filled after Lesson 5
Modules fully available: all — including Module 12
Copilot: unavailable (no Fabric capacity) — Module 13 Lesson 2 is read-only for me

If your reference has gaps, that is fine and normal. The point is that you now know where the gaps are instead of discovering them mid-project.

09

Common Mistakes

Assuming a Power BI “dashboard” means what you think it means
In everyday speech a dashboard is any page of charts. In Power BI the word has a specific technical meaning: a single-page collection of tiles pinned from one or more reports, which exists only in the service. What you build in Desktop is a report.

Fix: Say “report” for what you build in Desktop, and reserve “dashboard” for the pinned-tile artifact in the service. Module 12 Lesson 2 covers the distinction fully. Using the terms precisely marks you out immediately in an interview.
Trying to build the model in the browser
The service can edit reports, which leads people to attempt relationship and DAX work there. It is possible but it is not the tool for the job, and you will fight it.

Fix: Build in Desktop, publish to the service. Treat the service's editing as a convenience for small changes, not as your development environment.
Planning a sharing model without checking licences
Building a report for “the whole company” and then finding that only three people have Pro licences. The report is finished and cannot be delivered.

Fix: Establish licensing in the first conversation, not the last. If broad distribution to unlicensed users is required, that points to capacity, and that is a budget conversation someone needs to have early.
Assuming every documented feature is available to you
Following a tutorial that uses Copilot, or a preview feature, and concluding your install is broken when the button is not there.

Fix: Check three things before assuming a bug: your Desktop version (Help › About), whether the feature is in preview (File › Options › Preview features), and whether your tenant has disabled it. Module 13 covers this specifically for AI features.
Confusing Power BI Desktop with Power BI Desktop for Report Server
These are different builds. The Report Server version is deliberately held at an older feature level to match the server it publishes to. Files saved in the newer build may not open in it.

Fix: Only install the Report Server build if your organisation actually uses Report Server. If you are unsure, you do not — install the standard version.
10

Professional Tip

Read the release notes for ten minutes a month
Power BI Desktop ships a feature update every month, and Microsoft publishes a detailed blog post with each one. Ten minutes reading it puts you ahead of most practitioners, who discover features years late or never. It also tells you what has moved in the UI, which is the single most common reason a tutorial stops matching reality.

Bookmark the Power BI blog and the monthly update page.

Two related habits:

  • Check preview features once a quarter. File › Options and settings › Options › Preview features. Several features that are now standard spent a year there first. Enable them on a copy of your file, never on production work.
  • Keep a note of your version in the project file itself. A text box on a hidden report page recording the Desktop version and build date takes thirty seconds and saves real time when someone else opens the file in two years.
11

Knowledge Check

Knowledge Check

5 questions. Answer each one to see why the right answer is right.

A colleague says “I'll just add the relationships in the browser.” What is the most useful thing to tell them?

Your team has 40 people who need to view a report. Two of you have Pro licences; the other 38 have Free. What happens?

Which statement about Microsoft Fabric is accurate?

You are on macOS and want to follow this course. What is the accurate assessment?

In current Microsoft terminology, what is the object formerly called a “dataset” in the Power BI service now called?

12

Practical Challenge

Practical Challenge

Produce an environment and licensing assessment

A small business asks you to set up Power BI reporting. There are 25 staff. Three analysts will build reports; the other 22 only need to view them. They have Microsoft 365 Business Standard, which does not include Power BI Pro. Two of the analysts use MacBooks. Write the assessment you would send back before any work starts.

Requirements
  • State what the two Mac-based analysts need in order to build reports, with a recommendation
  • State exactly what licensing is required for the three builders
  • State the licensing options for the 22 viewers, and the trade-off between them
  • Identify one thing you would need to confirm with them before committing to an approach
  • Give a one-paragraph recommendation a non-technical owner could act on

Work through it in three parts:

  • Builders need Desktop (Windows) and, to publish anywhere shareable, a Pro licence each.
  • Viewers are the expensive decision. There are exactly two routes, and they have very different cost shapes: a per-user licence for each viewer, or capacity that lets Free users view.
  • Mac users need a Windows environment of some kind. Consider cost, convenience and who is paying.

The confirmation question is the part that separates a good assessment from a quote. Think about what would change your recommendation entirely if the answer surprised you.

13

Solution

Try the challenge properly before opening this. Reading a solution you have not attempted feels like learning, but it is not.

A model assessment

1 · The two Mac-based analysts

Power BI Desktop is Windows-only, so both need a Windows environment. Three realistic options, in the order I would suggest them:

  1. A cloud Windows desktop (Windows 365 or Azure Virtual Desktop). Cleanest option: no local hardware change, works from any machine, and IT can manage it centrally. Ongoing monthly cost per user.
  2. A local virtual machine (Parallels or VMware Fusion plus a Windows licence). Lower ongoing cost, one-off setup effort, and it consumes local resources — Power BI Desktop is memory-hungry, so allow 8 GB to the VM.
  3. Replace the machines with Windows laptops. Only sensible if a hardware refresh was due anyway.

I would recommend the cloud desktop for a business this size — it avoids putting hardware and licensing management onto two individuals.

2 · Licensing for the three builders

Each builder needs Power BI Pro (or PPU). Desktop itself is free, but publishing to a shared workspace — which is the entire point — requires Pro. Three Pro licences, billed monthly per user.

3 · The 22 viewers — the real decision

OptionHow it worksTrade-off
22 × Pro licencesEvery viewer gets Pro. Simple, immediate, no infrastructure.Cost scales linearly with headcount. Fine at 22; painful at 200.
Fabric / Premium capacity (F-SKU or P-SKU)Workspace runs on dedicated capacity; Free users can view content in it.Fixed monthly cost regardless of viewer count, but a much higher entry price. Only becomes cheaper than per-user licensing above a break-even headcount.

At 22 viewers, per-user Pro is almost certainly cheaper. Capacity becomes the better answer as the viewer count grows, so the right question is not just “what is cheapest today” but “where is this heading”.

I have deliberately not quoted prices. Microsoft's licence pricing changes and varies by region and agreement. Any real assessment should quote from Microsoft's current pricing page on the day it is written, and say so.

4 · What I would confirm first

The confirmation question
“Does any of this data need to stay inside your own network for regulatory reasons?”

If yes, the entire recommendation changes: the cloud service is off the table and you are looking at Power BI Report Server, with its older feature set and different licensing. Discovering this after building is the most expensive mistake available here.

A close second: “Where is the data now, and who maintains it?” If the answer is “a spreadsheet on someone's laptop”, the licensing question is not the real problem.

5 · Recommendation for the owner

The paragraph I would actually send
“Power BI Desktop, the tool your analysts will build in, is free — so there is no cost to start. The cost is in sharing. Your three analysts each need a Power BI Pro licence to publish reports, and at your current size the simplest approach is a Pro licence for each of the 22 viewers as well. That is 25 licences in total, billed monthly, and it can be scaled up or down as staff change. If your team grows past roughly the point where 25 licences becomes uncomfortable, there is a fixed-cost alternative worth revisiting — I will flag it when you get there rather than over-buying now. Separately, your two MacBook users will need a Windows environment; I would recommend a managed cloud Windows desktop rather than local virtual machines. Before we commit to any of this, I need to confirm one thing: whether any of the data you want to report on is subject to rules about leaving your own network.”
Why this answer is strong
It gives a clear recommendation rather than a menu. It flags the future decision without over-engineering for it today. It refuses to quote prices it cannot verify. And it puts the one genuinely disqualifying question in front of the client before any money is spent.
14

Lesson Summary

Key takeaways
  • Power BI Desktop is the free Windows authoring tool — connect, transform, model, calculate, design. This is where almost all of this course happens.
  • The Power BI service is the cloud platform — publish, schedule refresh, share, collaborate. Dashboards, in the technical sense, exist only here.
  • Desktop is the workshop; the service is the showroom. If an action needs a timer or needs to know who someone is, it belongs in the service.
  • Publishing for yourself is free; sharing with others is not. Free users cannot consume shared content without capacity backing the workspace.
  • Desktop is Windows-only. Mac and Linux users need a Windows environment.
  • Fabric is the broader platform Power BI now sits inside. It changes nothing about how you build a report.
  • A “dataset” in the service is now called a semantic model — same object, clearer name.

Syllabus topics delivered

What is Power BI?Power BI Desktop vs Power BI ServicePower BI ecosystemLicensing tiersWhere Fabric fits
15

Progress

Marking a lesson complete stores your progress in this browser and updates your BitWithBite learner dashboard. Nothing is uploaded anywhere.

Lesson complete — 3% of Power BI Mastery done
Progress saved. Keep the momentum: the next lesson builds directly on this one.