Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 38 ยท Getting Started

The Power Platform Ecosystem

See how Power Apps, Power Automate, Power BI, Copilot Studio, Power Pages and Dataverse fit together, and learn which product solves which problem.

Power Apps is one member of a family. The Microsoft Power Platform groups several products that share a data layer, a library of connectors and a common admin center. Knowing which product to reach for saves you from forcing everything into an app.

This lesson introduces each product in plain terms, shows how they cooperate, and gives you a simple way to choose.

The products

  • Power Apps: user interfaces. Canvas apps, model-driven apps and the maker tools around them.
  • Power Automate: automation. Cloud flows run when something happens (a record is created, an email arrives, a button is pressed) or on a schedule. There are also desktop flows (robotic process automation) that click through legacy software.
  • Power BI: analytics. Dashboards, reports and semantic models. A Power BI tile can be embedded in an app.
  • Copilot Studio: conversational agents and chatbots that can call flows and connectors.
  • Power Pages: external-facing websites with sign-in for customers and partners, backed by Dataverse.
  • Dataverse: the relational data platform with tables, security roles and business logic.
  • AI Builder: prebuilt and custom AI models, such as form processing and text classification, usable from apps and flows.
  • Connectors: a catalog of wrappers for services. Both apps and flows use them.

The Power Platform

Power Apps Screens people use
Power Automate Work that runs by itself
Power BI Charts and reports
Copilot Studio Chat agents

Four products, one shared platform

1 / 2

How they work together

A realistic scenario: a company wants an expense process.

  1. An employee opens a canvas app on a phone, photographs a receipt and submits it.
  2. The app writes a row to a Dataverse table.
  3. A cloud flow triggers on the new row, asks a manager for approval in Teams, and updates the row.
  4. AI Builder can read the receipt amount automatically.
  5. Finance opens a Power BI report that reads the same table.
flowchart TD
  App["Canvas app: submit expense"] --> DV[("Dataverse: Expenses table")]
  DV --> Flow["Cloud flow: approval"]
  Flow --> DV
  DV --> BI["Power BI report"]
  Flow --> Teams["Teams approval message"]

One table is the shared source of truth. The app, the flow and the report each use it for a different job.

Choosing the right product

A rule of thumb: apps are for people, flows are for processes, reports are for decisions. The stand-in below is a tiny chooser that encodes this rule. It is a teaching aid, not an official tool.

JS Stand-in: which Power Platform product fits?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Dataverse versus other data sources

Power Apps can use a SharePoint list or an Excel file, but Dataverse adds relationships, field-level security, auditing, business rules and richer data types. A common path is to prototype on SharePoint and move to Dataverse when the app grows. The trade-off is licensing: Dataverse tables are a premium capability in most plans (see Licensing, plans and environments).

Where things live

Everything you build lives in an environment, a container for apps, flows, tables and connections. You switch environments from the top bar in the maker portal. Related items are often packaged together in a solution so they can move from development to production, which you will study in the Components and ALM chapter.

The next stand-in lists a small "inventory" of a solution and groups it by component type, which is exactly what the Solutions area of the portal shows.

JS Stand-in: grouping solution components

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Common mistakes

  • Building everything inside the app, including long-running logic. Move heavy or scheduled work to a flow.
  • Skipping the data design and using a spreadsheet as a database.
  • Forgetting that each product can have separate licensing requirements.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which product is best for a process that runs automatically when a record is created?

    Cloud flows in Power Automate are triggered by events and run without a user interface.
  2. 2. What is Dataverse?

    Dataverse stores data in tables with relationships, security and business logic.
  3. 3. Which product builds sign-in websites for external customers?

    Power Pages is for external-facing portals backed by Dataverse.
  4. 4. What groups related apps, flows and tables so they can move between environments?

    Solutions package components for transport and ALM.

Summary

  • The Power Platform includes Power Apps, Power Automate, Power BI, Copilot Studio, Power Pages, Dataverse, AI Builder and connectors.
  • Apps are for people, flows for processes, reports for decisions.
  • A shared Dataverse table can serve all products at once.
  • Components live in environments and travel in solutions.

Next: Licensing, plans and environments