What Is Power BI? Desktop, Service & the Ecosystem
“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.
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.
- 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
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.
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.
| Capability | Power BI Desktop | Power BI service (app.powerbi.com) |
|---|---|---|
| What it is | A free Windows application you install | A cloud SaaS platform in the browser |
| Cost | Free | Free tier exists; sharing needs Pro or capacity |
| Get data & Power Query | Full transformation experience | Limited — dataflows and some editing |
| Data modelling | Full: relationships, hierarchies, properties | Editing available, but Desktop is where this work belongs |
| Writing DAX measures | Full authoring experience | Possible, but not the practical place to build a model |
| Building report visuals | Yes — the primary authoring surface | Yes — good for edits and quick builds |
| Dashboards (pinned tiles) | No — this concept exists only in the service | Yes |
| Scheduled refresh | No — refresh is manual | Yes — this is a core reason to publish |
| Sharing with others | No — you send a file | Yes — workspaces, apps, links |
| Row-Level Security | Define and test roles | Assign real users to those roles |
| Runs on | Windows only | Any modern browser; mobile apps for iOS/Android |
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.
| Tier | What you get | Key limitation |
|---|---|---|
| Free (per user) | Power BI Desktop in full; publish to your own My Workspace in the service | Cannot 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 collaboration | Every 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 features | Viewers 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 workspaces | Substantially higher cost; sized and managed as infrastructure |
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.
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.
| Activity | Where it happens | Why |
|---|---|---|
| Connect to a database or file | Desktop (or a dataflow) | The connector runs where the query is authored |
| Clean and shape data | Desktop — Power Query | Full transformation UI; the service's is limited |
| Build relationships | Desktop — Model view | Modelling belongs in the authoring tool |
| Write DAX measures | Desktop | Best authoring experience, with DAX formula bar and validation |
| Design report pages | Desktop (mostly) | Full formatting control; the service can edit |
| Set a refresh schedule | Service | Only the cloud can run something on a timer |
| Give someone access | Service | Identity and permissions live in the cloud |
| Pin a tile to a dashboard | Service | Dashboards do not exist in Desktop at all |
| Assign users to RLS roles | Service | Desktop defines roles; the service maps real people to them |
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.
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.
Step-by-Step Exercise
Build yourself a one-page environment reference. It takes five minutes and you will refer back to it repeatedly.
Expected Result
A short reference that answers, without you having to think about it: where do I do this, and am I allowed to?
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.
Common Mistakes
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.
Fix: Build in Desktop, publish to the service. Treat the service's editing as a convenience for small changes, not as your development environment.
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.
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.
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.
Professional Tip
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.
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?
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.
- 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.
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:
- 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.
- 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.
- 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
| Option | How it works | Trade-off |
|---|---|---|
| 22 × Pro licences | Every 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”.
4 · What I would confirm first
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
Lesson Summary
- 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
Progress
Marking a lesson complete stores your progress in this browser and updates your BitWithBite learner dashboard. Nothing is uploaded anywhere.