Prepstellar
Get the app

PL-900 · Getting started

21 cards

Microsoft Power Platform Solution Journey

Swipe, scroll or use ← →

  1. Understand what the platform is

    A first question worth settling: is Power Platform an application you open, or something larger? Microsoft Power Platform is a low-code platform for rapidly building customized end-to-end business solutions. It addresses business goals that involve AI-powered agents, analytics, process automation, or data-driven productivity applications.

    Power Platform is a platform, not one application. That single distinction shapes everything else here: you do not learn the Power Platform screen, you learn which of its areas answers which business goal.

    1 / 21

  2. Understand what the platform is

    The low-code approach is also a statement about who builds. Its low-code approach enables people across an organization, from frontline workers to professional developers, to participate in solution development. Professional developers can also collaborate with citizen developers and extend solutions with code.

    Who What they contribute
    Frontline and business staff The problem, the process knowledge, often the first working app
    Citizen developers Low-code apps, flows, and data structures
    Professional developers Collaboration with citizen developers, plus extensions written in code
    2 / 21

  3. Quick check

    A manager proposes to "install Power Platform and train one specialist on it". What is wrong with that framing?

    1. ANothing: it is a single application with one specialist role

      Power Platform is a platform, not one application, so there is no single product to install and learn.

    2. BIt is a reporting engine, so only analysts can use it

      Analytics is only one of the areas: Power BI sits alongside apps, automation, websites and agents.

    3. CIt is a low-code platform of several areas, and its low-code approach is meant to let frontline workers, citizen developers and professional developers all take part in building solutions

      Right. It is a low-code platform of several product areas, and its approach is designed for people across an organization, from frontline workers to professional developers.

    3 / 21

  4. See the five product areas at a glance

    It consists of five product areas: Copilot Studio, Power Apps, Power Automate, Power BI, and Power Pages. Each area can be used individually or together.

    Product area The outcome it owns
    Copilot Studio Agents and agent flows
    Power Apps Internal business applications
    Power Automate Automated tasks and orchestration across services
    Power BI Interactive business analytics
    Power Pages External-facing business websites

    One familiar name is missing from that list on purpose. Microsoft Dataverse is the underlying technology that unites the product areas for a connected experience. Dataverse is not listed as a sixth product area in this overview: it sits underneath them.

    4 / 21

  5. Quick check

    Which list names the product areas of Microsoft Power Platform?

    1. ACopilot Studio, Power Apps, Power Automate, Power BI, and Power Pages

      Right. Those are the five product areas, and each of them can be used individually or together.

    2. BCopilot Studio, Power Apps, Power Automate, Power BI, Power Pages, and Dataverse as a sixth area

      The first five are correct, but Dataverse is the underlying technology that unites them rather than a sixth product area.

    3. CPower Apps, Power Automate, Power BI, Dataverse, Azure Functions, and Microsoft Teams

      Dataverse is the foundation rather than a product area, and Azure Functions and Microsoft Teams are not part of this list at all.

    5 / 21

  6. Look inside Power Apps and Copilot Studio

    Power Apps creates internal business applications that can run in a browser or on a mobile device. Inside it there are two ways to build. Canvas apps give the maker control over screen content and navigation, while model-driven apps are data-driven applications built on Dataverse.

    App style Who drives the design
    Canvas The maker, screen by screen
    Model-driven The Dataverse data model

    The choice is not cosmetic: it decides whether the work goes into arranging an experience or into shaping a data model.

    6 / 21

  7. Look inside Power Apps and Copilot Studio

    Copilot Studio is the graphical, low-code area for building agents and agent flows. Its agents can connect to other data sources through prebuilt or custom connectors, so an agent is not limited to what it was told at design time.

    Copilot Studio answers a different question from Power Apps. Power Apps produces a screen a person operates; Copilot Studio produces an agent a person converses with.

    7 / 21

  8. Quick check

    A maker needs precise control over each screen of an internal app. What should they build?

    1. AAn agent in Copilot Studio, because agents are how internal screens get designed and navigated

      Copilot Studio builds agents and agent flows; it is not the area for designing an app's screens.

    2. BA canvas app in Power Apps, where the maker controls screen content and navigation

      Right. Canvas apps give the maker control over screen content and navigation inside Power Apps.

    3. CA model-driven app, whose screens come from Dataverse

      Model-driven apps are data-driven applications built on Dataverse, so the model rather than the maker shapes the screens.

    8 / 21

  9. Keep your progress in the app

    That’s 3 of 8 quick checks. In the app they stay answered, and every lesson remembers where you left off.

    Get the app Keep reading here

  10. Look inside Power Automate, Power BI and Power Pages

    Power Automate automates tasks and orchestrates activities across services through integrated or custom connectors. It comes in two forms, and the difference is where the work happens. Cloud flows can start manually, respond to an event, or run on a schedule; desktop flows automate repetitive interactive work on the web or desktop.

    Flow type How it starts What it drives
    Cloud flow Manually, from an event, or on a schedule Services, through connectors
    Desktop flow Repetitive interactive work A web or desktop interface, as a person would

    If a requirement says when a record is created, that is an event — and an event is a cloud-flow start.

    9 / 21

  11. Look inside Power Automate, Power BI and Power Pages

    The last two areas own the two audiences. Power BI provides interactive business analytics for visualizing and sharing data and insights. Power Pages creates, hosts, and administers external-facing business websites.

    The word external carries the whole distinction. Power Apps applications are shared with internal users; Power Pages publishes sites for people outside the organization.

    10 / 21

  12. Quick check

    A process must begin the moment a record is created and then work across several services, with nobody operating a screen. What matches?

    1. AA desktop flow, replaying the interactive steps a person would perform

      Desktop flows automate repetitive interactive work on the web or desktop, which is exactly the dependency the requirement rules out.

    2. BA Power Pages site, publishing the record externally so downstream services can pick it up

      Power Pages creates external-facing websites; it is a publishing surface, not a way to start and orchestrate a process.

    3. CA cloud flow, started by the event and orchestrating services through connectors

      Right. Cloud flows can respond to an event, and Power Automate orchestrates activities across services through connectors.

    11 / 21

  13. Understand Dataverse as the data foundation

    Dataverse is a cloud-scale data store that securely stores and manages business-application data in tables. Role-based security can control access to tables and individual records, so the protection travels with the data instead of being rebuilt inside every app.

    That is what makes it the connective tissue between the areas rather than a competitor to them: a canvas app, a cloud flow, a Power Pages site and a model-driven app can all read and write the same governed tables.

    12 / 21

  14. Quick check

    Why is Dataverse described as uniting the product areas rather than competing with them?

    1. ABecause it replaces Power Apps and Power Automate

      It stores and manages the data those areas work with; it does not stand in for building apps or automating work.

    2. BBecause it stores and secures business data in tables that apps, flows, sites and agents can all share

      Right. It securely stores and manages business-application data in tables, with role-based security over tables and individual records, which is what gives the areas one connected experience.

    3. CBecause it is the sixth product area of the platform

      This overview does not list Dataverse as a sixth product area: it is the underlying technology beneath the five.

    13 / 21

  15. Follow the solution journey

    The journey has four steps, and the first one is not technical. Begin with the business goal and identify the outcome that people need.

    Use Power Apps when the outcome is an internal app, Power Automate when work must be automated, Power BI when users need analytics, Power Pages when the outcome is an external-facing website, and Copilot Studio when the outcome is an agent.

    The outcome people need Where to start
    An internal application Power Apps
    Work that runs itself Power Automate
    Insight from data Power BI
    A site for people outside the organization Power Pages
    An agent Copilot Studio
    14 / 21

  16. Follow the solution journey

    Next, identify the data. Use Dataverse when the connected solution needs its business data securely stored and managed in tables. Connectors let canvas apps work with data and services, let Power Automate orchestrate activities across services, and let Copilot Studio agents connect to data sources.

    Then combine only the areas the goal requires. A service-request solution might use a Power Apps interface, Dataverse tables, and a Power Automate cloud flow. An external self-service solution might use Power Pages with Dataverse. The product areas can remain separate or participate together in one connected experience.

    15 / 21

  17. Follow the solution journey

    Finally, deliver the experience through the selected product surface. Power Apps applications can be shared with internal users and run in browsers or on mobile devices. Power Pages publishes external-facing sites across browsers and devices. Power BI shares visualized insights, while Copilot Studio supplies an agent experience.

    Notice what the journey never does: it never starts from the product catalogue. Starting from the goal keeps a solution down to the areas it actually needs.

    16 / 21

  18. Quick check

    Where should the design of a connected Power Platform solution start?

    1. AWith the business outcome people need, and then the data

      Right. Begin with the business goal and the outcome people need, then identify the data, then combine only the areas the goal requires.

    2. BWith the full product catalogue, selecting all five areas and then finding a goal that uses them

      The areas can be used individually or together, so a solution should include only what the goal requires.

    3. CWith custom code, deciding afterwards whether a low-code capability would have been enough

      Extension with code addresses complex requirements, but the introductory decision is about the outcome and the shared data.

    17 / 21

  19. Recognize the extension boundary

    Low-code does not mean code is forbidden. Professional developers can use platform extension capabilities and Azure integration to address complex requirements.

    The introductory decision is therefore about the required outcome and shared data, not about assuming that every solution must use every product area — and not about assuming that a low-code start rules out code later.

    18 / 21

  20. Quick check

    A requirement turns out to be too complex for the low-code designers alone. What does the platform allow?

    1. ANothing: a solution that starts low-code must remain entirely low-code from beginning to end

      Low-code does not mean code is forbidden; professional developers can also collaborate with citizen developers and extend solutions with code.

    2. BExtension capabilities and Azure integration, used by professional developers

      Right. Professional developers can use platform extension capabilities and Azure integration to address complex requirements.

    3. COnly dropping the requirement, since complex needs sit outside every Power Platform area

      Complex requirements are precisely what extension capabilities and Azure integration exist to address.

    19 / 21

  21. Key takeaways

    • Power Platform is a low-code platform for customized end-to-end business solutions.
    • Its five product areas are Copilot Studio, Power Apps, Power Automate, Power BI, and Power Pages.
    • Dataverse supplies the connected data foundation rather than being a sixth product area.
    • Choose and combine product areas according to the business outcome, data, and delivery experience.
    • Low-code is a starting point, not a ceiling: extension capabilities and Azure integration remain available.
    20 / 21

  22. Quick check

    Which summary of the platform is accurate?

    1. AFive product areas over a Dataverse foundation, combined according to the outcome

      Right. Five product areas sit on the Dataverse foundation and are chosen according to the business outcome, the data, and the delivery experience.

    2. BSix product areas including Dataverse, all of them used together in every solution whatever the goal

      Dataverse is the foundation rather than a sixth area, and the areas are combined according to what the goal requires.

    3. COne application for internal apps, with reporting and websites added on by Azure

      Power Platform is a platform of five areas, not a single application extended by Azure.

    21 / 21

  23. 8 quick checks · then the test

    In the app, finishing the quick checks opens this lesson’s 10-question test, and the ones you miss come back exactly when you’re about to forget them.

    Take this lesson’s test → Next lesson: PL-900 Exam OverviewGet the app
← Previous Keep your progress · Get the app Next card →

The whole course, on your phone

Lessons you can read, audio you can listen to on the way to work, and practice that remembers what you got wrong.

Get the app