In plain words
Power Platform is Microsoft's low-code platform. Low-code means you build software mostly by dragging, dropping and writing short formulas, instead of writing pages of code.
It is not one product. It is a family of products that share data, security and connectors. Think of a well-equipped kitchen. The oven, the fridge, the mixer and the pantry each do one job. Together, they let you cook almost any meal. In Power Platform, each product does one job, and together they solve whole business problems.
Why it matters
Most organisations have hundreds of small problems that never get fixed. A form lives on paper. An approval waits in someone's inbox. Data sits in a dozen spreadsheets. IT departments rarely have time for these jobs, because they are busy with large systems.
Power Platform lets the people closest to the problem fix it themselves. A help desk coordinator can build a ticket app in days, not months. IT still stays in control. It decides which environments exist, who can use what data and which connectors are allowed.
The business value comes down to three things:
- Speed. Solutions are built and changed quickly.
- Reach. More people can build, not only professional developers.
- Control. Security, data policies and admin tools keep everything governed.
How it works
Each member of the family has one main job. Learn them as a set, because the exam often asks "which product should you use?"
| Product | Main job | Typical users | Key parts |
|---|---|---|---|
| Power Apps | Build apps | Staff and internal users | Canvas apps, model-driven apps, code apps |
| Power Automate | Automate processes | Anyone with repeated tasks | Cloud flows, desktop flows |
| Dataverse | Store business data securely | Apps, flows and agents behind the scenes | Tables, columns, relationships, security roles, business rules |
| Connectors | Link to other services | Apps, flows and agents | Standard, premium and custom connectors |
| Power Pages | Secure websites for external users | Customers, partners, the public | Sites with sign-in and Dataverse data |
| Copilot Studio | Build AI agents | Anyone who needs a conversational helper | Topics, knowledge, tools, channels |
Power Apps comes in three styles. Canvas apps start from a blank screen and give you full control over layout, like designing a slide. Model-driven apps start from your Dataverse data and generate forms and views for you. Code apps are for professional developers who write web apps in code but still want Power Platform hosting, sign-in and governance.
Power Automate builds flows. A flow starts with a trigger (the event that starts it) and runs actions (the steps). Cloud flows work with online services through connectors. Desktop flows copy what a person does with mouse and keyboard on a computer, which helps with old systems that have no API.
Dataverse is the shared data layer. It stores data in tables, like a database, but adds business features such as security down to the row, relationships and auditing. Because apps, flows and agents can all use the same Dataverse tables, they all see the same data.
Connectors are ready-made bridges to other services. A connector wraps a service's API, which is the technical door that software uses to talk to it. The connector exposes friendly triggers and actions, such as "When a new email arrives" or "Create a row". There are over 1,000 of them.
- Standard connectors cover common services such as Outlook, SharePoint and Teams.
- Premium connectors cover services such as Dataverse, SQL Server and Salesforce, and need a premium licence.
- Custom connectors wrap your own organisation's API so makers can use it like any other connector.
Power Pages builds secure websites for people outside your organisation, such as customers who sign in to check an order. It remains part of the family. The current PL-900 outline no longer tests how to build sites, but you should still recognise when it is the right product.
Copilot Studio builds agents: AI assistants that answer questions from knowledge sources and take actions using tools. They can be published to channels such as Teams or a website.
Around the products sit shared services. Power Fx is the Excel-like formula language used across the platform. The Power Platform admin center manages environments and data policies. Copilot, the built-in AI assistant, appears in every studio (lesson 1.2).
Who builds?
- A citizen developer is a business user who builds solutions without being a professional developer.
- A professional developer extends the platform with code, custom connectors or code apps.
- A fusion team mixes both, plus IT, working on one solution together.
Example: Campus Help Desk
The college IT office gets requests by email, phone and walk-in. Nothing is tracked. Here is how each family member helps.
- Dataverse stores two tables. Ticket holds Title, Description, Priority (Low, Medium, High), Status (Open, In progress, Closed), Due date and a Category lookup. Category holds values such as "Wi-Fi" and "Printing".
- Power Apps canvas app: students use a simple, phone-friendly screen to submit a ticket.
- Power Apps model-driven app "Help Desk Staff": staff see views of open tickets, filter by priority and update status.
- Power Automate cloud flow: when a new High priority ticket is created, the flow posts a message in the staff Teams channel using the Teams connector.
- Copilot Studio agent "Help Desk Assistant": answers common questions like "How do I connect to campus Wi-Fi?" and can create a ticket if the answer does not help.
- Connectors tie it together: Dataverse, Outlook and Teams.
A coordinator (citizen developer) builds the apps. A developer from IT writes a custom connector to the college's student records API. Together they are a fusion team.
Common mistakes
- Thinking Dataverse is an app. Dataverse stores data. Users never "open Dataverse" to do their work; they use apps and agents built on it.
- Using Power Apps for external customers. Power Apps is mainly for internal users. For customers or partners signing in to a website, the answer is Power Pages.
- Confusing a connector with a flow. A connector is the bridge to a service. A flow is the automated process that uses that bridge.
- Assuming low-code means no IT. IT still governs environments, security and data policies.
- Expecting Power BI questions. It is part of the wider Microsoft family but not on this exam.
How the exam asks about it
- "Which product should you use?" Match the verb. Build an app for staff points to Power Apps. Automate, approve or notify points to Power Automate. Store securely points to Dataverse. External users on a website point to Power Pages. Answer questions in conversation points to Copilot Studio.
- Connecting to a service. "Work with SharePoint or Salesforce" points to a connector. "Our own API" or "in-house web service" points to a custom connector.
- Old software on a computer. "No API" or "legacy desktop application" points to a desktop flow, not a cloud flow.
- Who builds. "Business user without coding skills" means citizen developer. "Makers and professional developers together" means fusion team.