Power BI is a business analytics tool that turns raw data into interactive visual reports and dashboards, enabling anyone to make data-driven decisions without needing a degree in data science. For someone studying for the PL-300 exam, understanding what Power BI is and how its components fit together is the foundational first step — every subsequent concept builds on this knowledge.
Jump to a section
A simple way to picture Introduction to Power BI and the PL-300 Exam
A restaurant head chef's kitchen is a system of raw ingredients, recipes, cooking tools, and serving staff.
The head chef (you, the Power BI analyst) starts with raw ingredients from various suppliers: vegetables from one farm, meat from another, spices from a third. These are your raw data sources — Excel files, SQL databases, cloud services. The chef must clean, chop, and prepare these ingredients before any cooking can begin. This is the data transformation and cleaning process in Power Query.
The chef's core tool is the stove and oven — that is Power BI Desktop, where the actual cooking (data modelling and visualisation creation) happens. The chef uses recipes (DAX formulas) to combine ingredients in specific ways, creating dishes (measures and calculated columns). The final plated dish is a visual report — a bar chart, a map, or a KPI tile.
But a chef does not cook for themselves alone. The finished dishes must be sent out to the dining room. That is Power BI Service, the cloud platform where reports are published and shared. The waitstaff (Power BI mobile apps and SharePoint integration) deliver the reports to customers (stakeholders) who consume them. The chef also uses a display board showing the kitchen's performance metrics in real-time — that is Power BI dashboards, which aggregate multiple reports into a single view.
Finally, the chef must manage permissions and security: not every diner can enter the kitchen. That's row-level security (RLS) in Power BI, ensuring that each stakeholder sees only the data relevant to them.
Power BI is a collection of software services, apps, and connectors that work together to transform unrelated sources of data into coherent, visually immersive, and interactive insights. The name breaks down into two parts: 'Power' refers to its robust analytical engine, and 'BI' stands for Business Intelligence — the practice of using data to inform business decisions.
At its simplest, Power BI lets you connect to data, shape it (clean and transform it), model it (create relationships between tables), and visualise it (build charts, maps, and tables). You can then share those visualisations with others in your organisation. It was developed by Microsoft as part of the Power Platform and integrates deeply with other Microsoft tools like Excel, Azure, and Microsoft Teams.
The Power BI ecosystem contains three primary components:
Power BI Desktop: A free Windows application that you install on your computer. This is where the heavy lifting happens — you connect to data sources, clean the data using Power Query, build a data model, and design visualisations. It is a 'thick client' application, meaning most of the processing happens locally on your machine.
Power BI Service (also called app.powerbi.com): A cloud-based Software as a Service (SaaS) platform. After you finish creating a report in Power BI Desktop, you publish it to the Service. Here, you manage dashboards, schedule data refreshes, configure security, and share reports with colleagues through workspaces. The Service runs on Microsoft's Azure cloud infrastructure.
Power BI Mobile: Native apps for iOS, Android, and Windows phones and tablets. These allow users to view dashboards and reports on the go. Mobile apps are primarily for consuming reports, not creating them.
Why does Power BI exist? Before tools like Power BI, data analysis was slow and fragmented. Analysts would export data into Excel, build complex pivot tables, and email files back and forth. This led to version control nightmares and stale data. Power BI replaced this with live, connected, and automatically refreshed reports. It also centralises data governance — IT can manage who sees what, and users always see the most current data.
The core workflow in Power BI is often described as a four-step pipeline:
Connect: Bring data into Power BI from hundreds of supported sources — including relational databases (like SQL Server), flat files (CSV, Excel), cloud services (Salesforce, Google Analytics), and even web pages.
Transform: Use Power Query Editor to clean the data. This might involve removing duplicate rows, changing data types, splitting columns, merging tables, or filtering out irrelevant records. These steps are recorded as 'applied steps' and can be refreshed automatically.
Model: Build relationships between different tables (like connecting a 'Customers' table to an 'Orders' table using a common Customer ID). Create calculations using DAX (Data Analysis Expressions), a formula language similar to Excel functions. This is where you define measures like 'Total Sales = SUM(Sales[Amount])'.
Visualise: Drag and drop fields onto a canvas to create charts, tables, maps, slicers, and KPIs. Arrange them into a report layout that tells a story. Add interactivity such as cross-filtering — clicking a bar in one chart automatically filters the others.
The term 'Power BI' also covers additional components like Power BI Report Server (for on-premises deployment) and Power BI Embedded (for embedding reports into custom applications). However, for PL-300, the focus is heavily on Power BI Desktop and Power BI Service.
Crucially, Power BI uses a licence model to control features. The free Power BI Desktop can create any report, but publishing to the Service requires either a Power BI Pro licence (per-user, ~£8 per month) or a Power BI Premium capacity (organisation-wide, reserved cloud resources). Certain features — like deploying to workspaces, setting up automatic data refreshes, and using AI visuals — require a Pro or Premium licence. The PL-300 exam tests your understanding of which features belong to which licensing tier.
Install Power BI Desktop
Download and install Power BI Desktop from the Microsoft Store or the official website. This is the primary tool you will use to create all reports and data models. It is free and does not require any licence.
Connect to a data source
Click 'Get Data' and select a source such as Excel, SQL Server, or a CSV file. You will be prompted to enter credentials or a file path. This step imports the raw data into Power BI's memory. For large sources, you may choose 'DirectQuery' to query the source live instead of importing.
Clean and transform data in Power Query
Open Power Query Editor by clicking 'Transform Data'. Here, you can remove columns, filter rows, change data types, merge tables, and split columns. Each action is recorded as an 'applied step' and will be replayed every time the data refreshes.
Build the data model and write DAX measures
After closing Power Query Editor, use the Model view to create relationships between tables (e.g., connecting Orders to Products). Then write DAX formulas to create calculated columns, measures (like Total Profit = [Total Sales] - [Total Cost]), and calculated tables.
Design and publish reports
Drag fields onto the canvas to create visuals (bar charts, maps, card visuals). Arrange them into pages, add slicers for filtering, and apply themes. Save the file as a .pbix file, then click 'Publish' to upload it to a workspace in Power BI Service.
Configure security and schedule refresh in Power BI Service
After publishing, sign in to app.powerbi.com. Set up row-level security (RLS) by uploading a DAX filter, and schedule a daily or hourly data refresh. Finally, share the report with colleagues by granting them access to the workspace or sending a direct link.
Consider a medium-sized retail company, 'Northern Lights Outdoors', that sells camping gear across the UK and Ireland. The company uses three separate systems: an e-commerce platform (Shopify), a point-of-sale system in physical stores (Square), and an inventory database hosted on SQL Server. The CEO wants a single weekly report showing total sales by region, product category, and store channel.
An IT professional (likely a data analyst or a BI developer) would approach this using Power BI in the following way:
First, they open Power BI Desktop on their laptop. They click 'Get Data' and choose 'SQL Server' for the inventory database. They enter the server name and database name, then select the Products and Inventory tables. Next, they add a connection to Shopify using the built-in Shopify connector, authenticating with an API token. Finally, they connect to Square using an OData feed.
Once the data is loaded, they open Power Query Editor. They notice that the Shopify data has 'Sales Amount' stored as text with a '£' symbol. They use the 'Replace Values' step to remove the symbol and change the column data type to currency. They also see that the Square data uses 'County' while the inventory database uses 'Region'. They use the 'Merge Queries' step to create a mapping table that harmonises these location fields. They also filter out test orders by removing rows where 'Customer Name' contains 'Test Account'.
After closing Power Query Editor, the analyst builds the data model. They create relationships: linking 'Products' from the inventory database to 'Order_Items' from Shopify using a ProductID, and linking 'Stores' from Square to 'Orders' using a StoreID. They then write a few DAX measures:
Total Sales = SUM(Shopify_Orders[Amount]) + SUM(Square_Sales[Amount])
Sales Growth % = DIVIDE([Total Sales] - CALCULATE([Total Sales], SAMEPERIODLASTYEAR('Date'[Date])), CALCULATE([Total Sales], SAMEPERIODLASTYEAR('Date'[Date])))
The analyst adds a map visual showing sales by geography, a clustered bar chart for sales by product category, and a card showing total revenue. They add slicers for week and store channel so the CEO can filter interactively.
Finally, they save the .pbix file and publish it to a Power BI workspace in the Service. They set up a scheduled refresh (nightly at 2 AM) so the data stays current. They then configure row-level security so the regional managers can only see their own region's data. The CEO gets a link to the dashboard and views it on the Power BI mobile app during Monday morning meetings.
What does the IT professional actually do day-to-day? They:
Troubleshoot data refresh failures (e.g., a SQL Server password changed).
Optimise slow-performing reports by improving DAX formulas or reducing data load size.
Add new data sources as the business acquires new systems.
Train business users on how to use slicers and drill-through pages.
Manage workspace permissions using Microsoft Entra ID groups.
The PL-300 exam (Exam: Microsoft Power BI Data Analyst) focuses on assessing your ability to perform the entire analytics lifecycle using Power BI. The specific exam objective 1.1 — 'Identify key features and capabilities of Power BI' — will test your understanding of the Power BI ecosystem and what each component does. This is typically the first set of questions you will see.
The exam expects you to distinguish between the three main Power BI products: Power BI Desktop, Power BI Service, and Power BI Mobile. A classic trap is describing a feature available only in Desktop (like building complex calculated columns) as being available in the Service. In reality, the Service is primarily for sharing and consuming, not for heavy data transformation — that is done in Desktop.
Another common trap involves licensing. The exam will present scenarios where you must choose which licence is needed for a given task. For example:
'You need to share a dashboard with a colleague who wants to view it on their phone. What is required?' The correct answer is that both you and the colleague need at least a Power BI Pro licence (or the report must be hosted on Premium capacity). A free licence alone cannot consume shared content in the Service.
'You need to schedule a daily data refresh for a dataset.' This requires a Pro licence for the workspace owner, and the dataset must be hosted in a workspace (not 'My Workspace' for sharing).
The exam loves to test on Power Query versus DAX distinctions. A common question is: 'Which tool would you use to remove duplicate rows?' The answer is Power Query Editor (part of desktop). 'Which tool would you use to calculate a year-over-year percentage change?' The answer is DAX.
Concepts that will appear in questions include:
The purpose of 'workspaces' (formerly called app workspaces): they are collaborative containers for reports and dashboards.
The difference between a 'dashboard' (a single-page canvas with pinned visualisations from one or many reports) and a 'report' (a multi-page collection of visuals from a single dataset). The exam will describe a scenario and ask you to identify which is being described.
The role of the 'natural language query' (Q&A) feature — it allows users to type questions in English and get visual answers.
The concept of 'quick measures' — pre-built DAX calculations you can use without writing code.
The ability to use 'decomposition trees' and 'key influencers' visuals — AI-powered features available in Desktop.
The exam will also test your knowledge of Power BI's integration with other Microsoft products:
Excel: You can export data from Power BI to Excel, or analyse Excel data in Power BI.
Microsoft Teams and SharePoint: Reports and dashboards can be embedded into these platforms.
Microsoft Entra ID: Used for managing user authentication and row-level security.
Azure: Power BI is built on Azure but also can connect to Azure services like Azure SQL Database.
Finally, the exam expects you to know the common data sources that Power BI supports natively: SQL Server, Excel, CSV, SharePoint lists, Dataverse, and over 150 other connectors. You will not be asked to memorise all 150, but you must recognise the major categories (databases, files, cloud services, online services).
Traps to watch for include questions where 'Power BI Desktop' is referred to as a 'report-building tool' (correct) but a distractor says 'Power BI Desktop is used to view reports on mobile phones' (false). Another trap conflates 'row-level security' (which filters data per user) with 'data-level security' — the latter is not a standard Power BI term.
To succeed, you must memorise the exact four-step workflow (Connect, Transform, Model, Visualise) and be able to map each specific task (like 'splitting a column') to the correct step.
Power BI Desktop is the free local application for building reports, while Power BI Service is the paid cloud platform for sharing them.
The four-step Power BI workflow is Connect, Transform, Model, and Visualise.
Data cleaning must be done manually using Power Query Editor — it does not happen automatically.
Row-level security (RLS) restricts data visibility per user and is configured in Power BI Desktop, then enforced in Power BI Service.
DAX (Data Analysis Expressions) is used for creating custom calculations and measures, not for connecting to data.
A Power BI Pro licence is required to publish reports to the Service and to share them with others.
Power BI Mobile apps are for viewing reports only, not for editing or creating them.
Power BI supports well over 150 data source connectors, including databases, files, and cloud services.
These come up on the exam all the time. Here's how to tell them apart.
Power BI Desktop
Installed locally on Windows PC
Used for data transformation and report creation
Free to download and use without a licence
Power BI Service
Cloud-based SaaS platform accessed via browser
Used for report sharing, dashboards, and scheduled refresh
Requires a Pro or Premium licence for most features
Power Query
Used for data extraction, cleaning, and transformation
Operates on rows and columns (like Excel's Power Query add-in)
No formulas needed; uses a graphical interface of applied steps
DAX
Formula language for creating calculations and measures
Evaluates across entire tables and filters (aggregations)
Requires writing expressions like SUM, CALCULATE, FILTER
Row-Level Security (RLS)
Filters data at the row level per user
Configured in Power BI Desktop using DAX filters
Each user sees only rows they are allowed to see
Page-Level Security (PLS)
Controls which report pages a user can see
Configured in Power BI Service via permissions
A user may see one page but not another
Mistake
Power BI Desktop and Power BI Service are the same thing; you can do everything in both.
Correct
Power BI Desktop is a local application for building reports, while Power BI Service is a cloud platform for sharing and managing those reports. You cannot create a data model or build complex visuals from scratch in the Service.
The naming is confusing — both contain 'Power BI', so beginners assume they are interchangeable.
Mistake
You need a paid licence just to use Power BI Desktop.
Correct
Power BI Desktop is completely free to download and use. You only pay for a Pro or Premium licence when you publish reports to the Service and share them with others, or for advanced features like automated data refreshes.
Microsoft offers the desktop app for free to encourage adoption, but many assume that since it is a Microsoft business tool, it must be paid.
Mistake
Power BI can only handle small datasets (like Excel files with a few thousand rows).
Correct
Power BI can handle datasets with millions of rows because it uses an in-memory columnar storage engine (VertiPaq) that compresses data efficiently. It can also connect to large-scale databases like SQL Server and Azure Synapse.
Beginners often confuse Power BI with Excel's limitations, since both have a similar drag-and-drop feel.
Mistake
Power BI automatically cleans all your data when you connect to it, so you never need to touch Power Query.
Correct
Power BI does not automatically clean data. You must use Power Query Editor to manually remove errors, fix data types, filter rows, and handle missing values. Data in its raw form is almost always dirty.
The 'Get Data' wizard is so simple that users think it magically handles everything.
Mistake
You can build a report directly in Power BI Mobile.
Correct
Power BI Mobile is a consumption-only app. You can view, filter, and interact with reports, but you cannot create a new report from scratch or edit an existing report's visuals. Report creation requires Power BI Desktop.
Other mobile apps (like Excel mobile) allow some editing, so users assume Power BI Mobile does too.
Mistake
All Power BI visuals (charts, tables, maps) are pre-installed and cannot be changed.
Correct
While Power BI comes with a core set of visuals, you can import custom visuals from AppSource (Microsoft's marketplace) or build your own using the Power BI Visual SDK. This gives you near unlimited customisation.
Users unfamiliar with extensibility assume the out-of-the-box visuals are the limit.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Power BI Desktop is free to download and use for creating reports. However, to publish and share those reports with others, you need a Power BI Pro or Premium licence.
Excel is a general-purpose spreadsheet tool for manual calculations and small datasets. Power BI is designed for large-scale data analysis, real-time dashboards, and sharing interactive reports. Power BI also handles much larger datasets and refreshes data automatically.
Power BI Desktop is only available for Windows. Mac users can run it through a virtual machine (like Parallels) or use the Power BI Service through a web browser for viewing reports, but not for creating them.
A .pbix file is the native file format for Power BI Desktop. It contains all the data imported (or a connection to the data source), the data model, the DAX calculations, and the report layout in a single file.
In Power BI Desktop, you can manually refresh data by clicking the 'Refresh' button. In Power BI Service, you can set up a scheduled refresh (daily, hourly, etc.) in the dataset settings, which requires a Pro licence for the dataset owner.
A report is a multi-page document of visuals all built from a single dataset. A dashboard is a single-page canvas that can contain visualisations pinned from multiple reports or datasets. Dashboards are created in Power BI Service, not in Desktop.
You've finished Introduction to Power BI and the PL-300 Exam. Continue through the PL-300 study guide to build a complete picture of the exam.
Done with this chapter?