# Understanding the Core Components of Power Platform

> Chapter 2 of the Courseiva PL-900 curriculum — https://courseiva.com/learn/pl-900/power-platform-components

**Official objective:** 1.2 — Identify the core components of Microsoft Power Platform

## Introduction

What exactly are the different pieces inside Microsoft Power Platform, and how do they fit together? If you are studying for the PL-900 exam, this is the single most important question to answer, because the exam will ask you to identify each component and its role. Without a clear picture of the core components, you risk confusing Power Apps with Power Automate, or assuming Dataverse is just a database — mistakes that will cost you marks.

## The Tool Shed Analogy

Have you ever walked into a friend’s shed and felt overwhelmed by the chaos? There’s a hand saw, an electric drill, a spirit level, and a bucket of paint — each can do a specific job, but none of them can build a shelf on their own. You need them to work together: the drill makes the hole, the level makes it straight, and the paint makes it look tidy.

Microsoft Power Platform is exactly like that well-organised tool shed — but for solving business problems instead of home renovations. The core components are four specialist tools: Power Apps is the handsaw for building apps; Power Automate is the electric screwdriver for repetitive tasks; Power BI is the spirit level for seeing data clearly; and Power Virtual Agents is the paint bucket for creating chatbots. Microsoft Dataverse is the workbench — the central storage space where all the tools share materials. Without the workbench, the tools can’t see what each other is doing. When you understand this shed, you see that Power Platform is not one product but a coordinated set of tools that, together, turn messy business problems into tidy, repeatable solutions.

## Core explanation

Microsoft Power Platform is a collection of four main tools — plus a central data service — that let you build business apps, automate workflows, analyse data, and create chatbots, all without needing to write computer code from scratch. Let’s break each one down from the ground up.

**Power Apps** is a tool for building custom applications. Think of an app as a piece of software that lets someone perform a task, like filling in an expense report or tracking inventory. Before Power Apps, if a business needed a custom app, they had to hire a professional software developer to write code, which was expensive and slow. Power Apps lets you create apps by dragging and dropping visual elements (buttons, forms, lists) onto a canvas — like designing a PowerPoint slide, but the result is a real working app that runs on a phone, tablet, or computer. The key idea is that you don’t need to know programming languages like C# or Java. You just connect the app to your data (for example, a list in Excel or a table in Dataverse), and the app can read, update, or delete that data.

**Power Automate** is a tool for creating automated workflows. A workflow is a series of steps that happen in sequence, like: when a new customer signs up, send them a welcome email, add them to a mailing list, and create a record in your database. Power Automate lets you build these flows using a visual designer — you choose a trigger (the event that starts it, e.g., “when a new email arrives in my inbox”) and actions (the things that happen next, e.g., “send an SMS” or “create a file in SharePoint”). The real power is that it connects many different services (Microsoft 365, Twitter, Dropbox, hundreds more) so that information moves automatically between them. The old way involved a person manually copying data from one system to another — slow and error-prone. Power Automate does that in seconds, 24/7, without mistakes.

**Power BI** is a business analytics tool. Analytics means turning raw numbers into charts, graphs, and dashboards that reveal trends and insights. For example, a shop manager could see a visual dashboard showing sales by product, by day, and by region — updating in real time. You get the data from sources like Excel, SQL databases, or web services, and then Power BI lets you create interactive reports that you can share with colleagues. The old alternative was printing reports from an accounting system or spending hours stitching together Excel charts. Power BI makes it fast and interactive — you can click on a region to see only that region’s data, or drill into a month to see daily numbers.

**Power Virtual Agents** is a tool for building chatbots without writing code. A chatbot is a computer program that can hold a conversation with a person, usually through text. Think of the help chat you see on a shopping website — that’s often a chatbot. Power Virtual Agents lets you define topics (like “how do I reset my password?”) and then map out the conversation: the bot asks a question, the user replies, the bot gives an answer. You create the logic using a visual editor, so you don’t need to program the bot. It uses natural language understanding — meaning the bot can figure out what the user means even if they phrase things differently.

**Dataverse** is the data platform that ties these tools together. Dataverse stores business data securely in tables (similar to Excel spreadsheets, but much more powerful). If you build a Power App, it can read from and write to Dataverse. If a Power Automate flow updates a customer record, that change is saved in Dataverse. If Power BI shows a dashboard, the data often lives in Dataverse. The key benefit is that all your tools use the same data source, so you never have data in two different places that disagree. Dataverse also adds standard security features — for example, you can control which users can see which rows of data.

These four components (Power Apps, Power Automate, Power BI, Power Virtual Agents) plus Dataverse form the core of Power Platform. They work together to let people in any job role build solutions that previously required expensive software development. For the PL-900 exam, you must be able to describe each component in one sentence and explain how they connect.

## Real-world context

Imagine Sarah works at a medium-sized logistics company. She is not an IT professional — she is part of the customer service team. Every day, her team receives hundreds of phone calls from customers asking about delivery status. The current process is painful: a customer calls, Sarah opens three different systems (the delivery database, the email system, and a spread sheet) to find information, and then types a response manually. It takes about ten minutes per call, and sometimes Sarah forgets to update the spread sheet, causing confusion.

Sarah decides to use Power Platform. Here is what happens step by step:

1. **Build a Power App for the team** — Sarah uses Power Apps to create a simple mobile app that shows a delivery’s current status, the customer’s phone number, and the expected delivery time, all in one screen. The app reads data from Dataverse, which holds the delivery records. Now, when a customer calls, Sarah opens the app and sees the information in seconds, not minutes.

2. **Automate the notifications** — She builds a Power Automate flow that triggers when a delivery status changes to “delivered.” The flow automatically sends a “your parcel has arrived” email to the customer, and also writes a note into Dataverse so the customer service team can see it. This eliminates the manual step of typing emails.

3. **Create a dashboard** — Using Power BI, Sarah creates a dashboard for her manager that shows how many deliveries are on time, how many are delayed, and which drivers have the most pending deliveries. The dashboard refreshes every hour from Dataverse, so decisions are based on current data.

4. **Add a chatbot** — Finally, Sarah builds a Power Virtual Agents chatbot on the company’s website. Customers can type “Where is my order?” and the bot checks Dataverse and replies with the current status. This handles about 60% of the phone calls automatically, freeing Sarah’s team to focus on complex issues.

In this scenario, the core components are not used in isolation — they are connected through Dataverse. Power Apps shows data, Power Automate moves data, Power BI visualises data, and Power Virtual Agents talks about data. The IT professional (or in this case, Sarah acting as a citizen developer) didn’t write a single line of code. The PL-900 exam tests that you understand this interplay: each component has a distinct job, but they all share the data layer.

## Exam focus

The PL-900 exam objective 1.2 is very specific: you need to identify the core components and match them to the problems they solve. The exam will not ask you to build anything — it will give you a scenario and ask which component to use. Here is exactly what to expect.

**Question types you will see:**
- “A company wants to create a custom app that lets employees submit holiday requests. Which Power Platform component should they use?” (Answer: Power Apps)
- “A manager needs to see sales data in a visual dashboard. Which tool?” (Answer: Power BI)
- “An IT department wants to automate sending an approval email when a purchase order is submitted. Which component?” (Answer: Power Automate)
- “A help desk wants a chatbot to answer common questions about password resets. Which tool?” (Answer: Power Virtual Agents)
- “Where should the data for all these components be stored to keep it consistent and secure?” (Answer: Dataverse)

**Common traps the exam sets:**
- They might describe a task that involves *both* automation and an app. For example: “Users need a mobile app to submit expenses, and the expense should automatically be sent to a manager for approval.” The correct answer could be “Power Apps for the app, and Power Automate for the approval flow.” The exam will sometimes list single-component answers to tempt you.
- They might describe a scenario that *could* be done with multiple tools, but one is the best fit. For example, a scenario about reporting and visualisation should always point to Power BI, not Power Apps (though Power Apps *can* show data, the exam expects Power BI for analytics).
- They might confuse Dataverse with SharePoint or Excel. Dataverse is the structured, secure, integrated data store of Power Platform. SharePoint lists are simpler and not as secure at row level. The exam will test that distinction.
- They might ask about Power Automate vs. Power Apps: Power Automate is for background processes (no user interface needed), Power Apps is for interactive user interfaces.

**Key definitions to memorise:**
- Power Apps: Build custom apps with low code.
- Power Automate: Automate workflows between services.
- Power BI: Visualise and analyse data.
- Power Virtual Agents: Create chatbots using natural language.
- Dataverse: The underlying data platform with security and business logic.

Practice questions in the exam will ask you to “identify the component” — so focus on the core purpose of each, not the advanced features.

## Step by step

1. **Identify the business problem** — Before choosing a Power Platform component, you must figure out what the business needs. Is the problem about collecting data from users (use Power Apps)? Automating a repetitive task (use Power Automate)? Visualising existing data (use Power BI)? Or providing self-service answers (use Power Virtual Agents)?
2. **Decide whether you need a user interface** — If the solution requires someone to type into a form, tap buttons, or view a custom screen, Power Apps is the right choice. If no human interaction is needed — the process runs on its own — then Power Automate is appropriate.
3. **Consider where the data lives** — If the data is already in Dataverse, SharePoint, Excel, or many other sources, Power Platform can connect to it. For the PL-900, remember that Dataverse is the recommended storage because it gives you security, standardised tables, and seamless integration across all components.
4. **Map the flow of information** — Draw a simple diagram: what triggers the process? What happens next? If there are multiple steps (e.g., create record, send email, update status), Power Automate is your tool. If the flow includes branching decisions or approvals, Power Automate handles that too.
5. **Choose the component that fits the outcome** — Based on the previous steps, select one or more components. For example, a customer portal that lets users check their order and sends a confirmation email would use Power Apps (for the portal) and Power Automate (for the email). Then you connect them through Dataverse.
6. **Test and iterate** — Power Platform is low-code, so you can quickly change things. Test with real users, gather feedback, and adjust the app, flow, dashboard, or chatbot. The exam does not test this step, but it is the real-world pattern you need to know.

## Comparisons

### Power Apps vs Power Automate

**Power Apps:**
- Creates interactive apps with buttons, forms, and screens
- Requires a user to open and interact with the app
- Primary purpose is user-facing data entry and viewing

**Power Automate:**
- Creates automated workflows that run in the background
- No user interface needed once the flow is set up
- Primary purpose is automatically moving data between services

### Power BI vs Power Apps

**Power BI:**
- Used for analysing and visualising existing data
- Output is charts, dashboards, and reports
- Users view data but cannot change it through the report

**Power Apps:**
- Used for collecting new data or editing existing data
- Output is a custom application with forms and controls
- Users can read and write data through the app

### Dataverse vs SharePoint Lists

**Dataverse:**
- Supports complex relationships between tables
- Provides row-level security and business rules
- Designed for use across all Power Platform tools

**SharePoint Lists:**
- Simple list structure with limited relationships
- Security is at the list level, not individual rows (without extra configuration)
- Primarily designed for document management and team collaboration

### Power Virtual Agents vs Power Automate

**Power Virtual Agents:**
- Designed for conversational interactions with users
- User initiates the conversation by typing a question
- Built on natural language understanding

**Power Automate:**
- Designed for event-driven processes (e.g., new email triggers a flow)
- Flow runs automatically after a trigger
- No natural language processing; uses structured conditions and actions

## Diagram

_A decision flowchart showing how to choose the right Power Platform component based on whether a user interface is needed, with Dataverse as the central data store feeding all components._

```mermaid
flowchart TD
    A[Business Problem] --> B{Need a user interface?}
    B -- Yes --> C[Power Apps]
    B -- No --> D[Power Automate]
    C --> E[Dataverse]
    D --> E
    E --> F[Power BI for reports]
    E --> G[Power Virtual Agents for chatbots]
```

## Common misconceptions

- **Misconception:** Power Apps and Power Automate are the same tool because they both make things easier. **Reality:** Power Apps builds interactive applications that a user opens and clicks on. Power Automate runs processes in the background without a user interface — they are different tools for different problems. (Beginners hear 'automation' and 'apps' as similar concepts, but a flow has no screen, while an app is all screen.)
- **Misconception:** Dataverse is just a fancy name for a database — it’s the same as SQL Server. **Reality:** Dataverse is a low-code data platform that includes security, business logic, relationships, and standardisation. It is built on top of databases but adds features like role-based access (RBAC) and pre-built business tables. (The term 'database' is familiar, so learners oversimplify Dataverse. They miss that Dataverse adds layers of governance that a raw database does not have.)
- **Misconception:** You need to know programming to use any Power Platform component. **Reality:** All four core components are designed for low-code or no-code development. Power Apps uses drag-and-drop, Power Automate has a visual designer, Power BI uses point-and-click, and Power Virtual Agents uses a graphical topic editor. (Many beginners come from a non-IT background and assume that any 'development' tool requires coding. Power Platform’s selling point is that it empowers non-developers, which is exactly what the PL-900 tests.)
- **Misconception:** Power BI can send emails automatically like Power Automate. **Reality:** Power BI is for visualisation and analytics only. To trigger an email based on a dashboard metric, you need Power Automate. Power BI can integrate with Power Automate, but by itself it does not perform actions. (Both tools deal with data, so learners assume they have overlapping features. The exam relies on precise boundaries.)
- **Misconception:** Power Virtual Agents requires you to write artificial intelligence (AI) code. **Reality:** Power Virtual Agents uses pre-built natural language understanding models. You define topics and responses in a visual editor — no AI programming is needed. (The word 'agents' and 'chatbot' sounds advanced and technical, so beginners fear it. In reality, it is as simple as mapping out a conversation tree.)

## Key takeaways

- Power Apps lets you build custom mobile and web applications without writing code by using drag-and-drop visual elements.
- Power Automate creates automated workflows that connect multiple services, triggered by an event like a new email or a new row in a table.
- Power BI transforms raw data into interactive dashboards and reports so decision-makers can spot trends at a glance.
- Power Virtual Agents allows you to build conversational chatbots that can answer common questions using natural language understanding.
- Dataverse is the central, secure, and standardised data store that all Power Platform components can share and use.
- Each component has a distinct role: apps for interaction, automation for background processes, analytics for visualisation, chatbots for conversation, and Dataverse for storage.

## FAQ

**Do I need to know how to code to use Power Apps?**

No. Power Apps uses a visual canvas where you drag and drop elements. You can add logic with formulas similar to Excel, but you do not need to write traditional programming code.

**Is Power Automate the same as a macro in Excel?**

Not exactly. A macro automates tasks inside Excel only. Power Automate connects hundreds of different services — like Microsoft 365, Twitter, Salesforce, and Dataverse — to move data between them automatically.

**Can I use Power BI without Dataverse?**

Yes. Power BI can connect to many data sources like Excel, SQL databases, web pages, and cloud services. Dataverse is just one of many possible data sources.

**Does Power Virtual Agents work with languages other than English?**

Yes. Power Virtual Agents supports multiple languages, including Spanish, French, German, and many others. You can configure the language in the bot’s settings.

**What happens if I need a feature that Power Apps does not have?**

You can extend Power Apps by adding custom code using ‘Power Apps Component Framework’ or connecting to custom APIs. But for the PL-900 exam, focus on the built-in low-code capabilities.

**Is Dataverse free?**

Dataverse comes with certain Power Platform licences but is not free by itself. You typically pay per user or per capacity. The PL-900 exam does not test pricing models, just the concept and role of Dataverse.

## Check your understanding

1. **A company wants to build a chatbot that can answer customer questions about order status. Which Power Platform component should they use?**

   Answer: Power Virtual Agents.

2. **What is the primary purpose of Power Automate?**

   Answer: To create automated workflows that connect different services and run without manual intervention.

3. **A manager needs a real-time dashboard showing sales figures across regions. Which component is the best fit?**

   Answer: Power BI.

4. **Why is Dataverse often recommended as the data store for Power Platform solutions?**

   Answer: Because it provides standardised, secure tables that all core components can share, ensuring data consistency.

5. **What distinguishes Power Apps from Power Automate in terms of user interaction?**

   Answer: Power Apps requires a user to interact with a visual interface, while Power Automate runs processes in the background with no user interface needed.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/pl-900/power-platform-components