PL-900 · Domain 4 of 5

PL-900 Domain 4: Demonstrate the capabilities of Power Automate

Automating work with Power Automate: when to use cloud or desktop flows, common approval, Teams, Outlook, SharePoint, Forms and document scenarios, how triggers and actions fit together, and how Copilot drafts and edits flows.

Exam weight
20–25%
Official functional groups
2
Estimated questions estimate
~10
Suggested study time estimate
5–8 hrs

About 11 min read Reviewed October 2026

Overview

Domain 4 carries 20–25% of PL-900, an increase in the July 2026 revision, and has two functional groups. Describe Power Automate use cases and capabilities covers cloud and desktop flows plus scenarios for approvals, Microsoft Teams, Outlook, SharePoint, Forms and document automation.

Describe how to build basic flows by using Power Automate covers connector triggers and actions for cloud flows and using AI to create and modify both cloud flows and desktop flows. The emphasis is recognizing the right flow type and its building blocks, not memorizing every expression or action setting. Older material on process mining and detailed flow building predates the current wording.

How it's tested

Expect business automation scenarios that describe an event, the steps that follow and the systems involved. You choose a flow type, identify the trigger, or select the action that completes the process. A few items ask how Copilot helps a maker build or change a flow. Read whether the target system has an API or only a screen.

  • Cloud or desktop

    Whether the system exposes a connector or only a user interface decides between a cloud flow and a desktop flow.

  • Name the trigger

    An event such as a new email, a submitted form or a schedule identifies the flow's trigger and type.

  • Microsoft 365 chain

    A process moves through Forms, SharePoint, Outlook, Teams and Approvals, and you pick the missing step.

Reasoning it through

Finance staff copy invoice totals from emailed PDFs into a decades-old desktop accounting program that has no API. A cloud flow can save the attachment and extract fields with document processing, but entering data into the old program requires interacting with its screens. A desktop flow handles that part, and the cloud flow can call it. Choosing only a cloud flow would leave the final step manual.

Functional groups 2

Official functional groups from the Microsoft outline, in outline order.

4.1 Describe Power Automate use cases and capabilitiesCloud and desktop flow use cases, plus approvals, Teams, Outlook, SharePoint, Forms and document automation scenarios.
What it means
This group asks you to describe when to use cloud flows and desktop flows, and to describe Power Automate use cases for approvals, Microsoft Teams, Outlook, SharePoint, Forms and document automation.
What to understand
Cloud flows run in the cloud and come in three main kinds: automated flows started by an event, instant flows started by a user, and scheduled flows started on a recurrence. Desktop flows, built in Power Automate for desktop, automate Windows and web interfaces through robotic process automation and can run attended or unattended. Typical Microsoft 365 scenarios include routing approvals with the Approvals connector, posting adaptive cards in Teams, handling Outlook email and attachments, creating or updating SharePoint items and files, and acting on Forms responses. Document automation extracts data from invoices and forms with AI Builder and passes it to other systems.
How it shows up
Expect a process description where you pick the flow type or the Microsoft 365 service that completes it.
Common confusion
Believing desktop flows are for scheduled cloud tasks; they automate user interfaces, while cloud flows use connectors.
4.2 Describe how to build basic flows by using Power AutomateConnector triggers and actions in cloud flows, and using AI to create and modify cloud and desktop flows.
What it means
This group covers how flows are assembled and how AI speeds that up. It includes connector triggers and actions for cloud flows, using AI to create and modify cloud flows, and using AI to create and modify desktop flows.
What to understand
Every cloud flow has exactly one trigger and one or more actions. Connectors supply both: for example, the Microsoft Forms connector offers a trigger when a new response is submitted, and the SharePoint connector offers an action to create an item. Conditions, loops and dynamic content link steps together. In the cloud flow designer, Copilot can generate a flow from a natural language description, set up connections and then change steps through chat. In Power Automate for desktop, Copilot can help generate and edit desktop flow actions from descriptions, and makers can record steps, then review and test what was produced.
How it shows up
Expect items that ask which part is the trigger, which connector supplies an action, or what Copilot does in each designer.
Common confusion
Thinking a cloud flow can have several triggers; it has one trigger followed by actions.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Cloud flow

    A flow that runs in the cloud using connectors.

    Remember
    Kinds are automated, instant and scheduled.
    Tested as
    The default answer for API-based automation across services.
    Trap
    Choosing it for an application that has no connector or API.

  • Automated cloud flow

    A cloud flow started by an event in a connected service.

    Remember
    Examples: new email arrives, item created, form submitted.
    Tested as
    Scenarios beginning with when something happens point here.
    Trap
    Confusing it with a scheduled flow that runs on a timer.

  • Instant cloud flow

    A cloud flow started manually, for example from a button or a selected item.

    Remember
    Users trigger it from Power Automate mobile, Teams, SharePoint or an app.
    Tested as
    Chosen when a person decides when the flow runs.
    Trap
    Assuming instant means faster processing.

  • Scheduled cloud flow

    A cloud flow that runs on a recurrence.

    Remember
    Useful for daily reports, reminders and cleanup.
    Tested as
    Questions mentioning every Monday or nightly point here.
    Trap
    Using an automated trigger when no event exists.

  • Desktop flow

    Robotic process automation of Windows and web interfaces.

    Remember
    Built in Power Automate for desktop; can run attended or unattended.
    Tested as
    The answer for legacy apps with no API.
    Trap
    Thinking desktop flows only run when a user is signed in.

  • Trigger

    The event that starts a flow.

    Remember
    A cloud flow has exactly one trigger.
    Tested as
    Items ask you to identify which step starts the process.
    Trap
    Treating the first action as the trigger.

  • Action

    A step a flow performs after the trigger.

    Remember
    Actions come from connectors or built-in operations like conditions and loops.
    Tested as
    Missing-step questions ask for the right action.
    Trap
    Picking a trigger where an action is needed.

  • Approvals

    Built-in capability to request and record sign-offs.

    Remember
    Approvers respond in Outlook, Teams or the Power Automate portal.
    Tested as
    Common in purchase, leave and document approval scenarios.
    Trap
    Assuming approvals need a custom app.

  • Dynamic content

    Outputs of earlier steps reused in later steps.

    Remember
    Lets a flow pass an email subject or form answer into the next action.
    Tested as
    Explains how data moves between steps.
    Trap
    Typing static values where step output is needed.

  • Document automation

    Extracting data from documents such as invoices with AI Builder models.

    Remember
    Extracted fields can feed approvals, Dataverse or other systems.
    Tested as
    Named explicitly in the current use case bullet.
    Trap
    Thinking document automation means storing files only.

  • Copilot in cloud flows

    Natural language creation and editing in the cloud flow designer.

    Remember
    It drafts the trigger and actions, then edits steps on request.
    Tested as
    Matches the bullet on AI creating and modifying cloud flows.
    Trap
    Assuming Copilot finishes connections and testing for you.

  • Copilot in desktop flows

    AI help in Power Automate for desktop to generate and change actions.

    Remember
    Makers describe a task and review the generated steps.
    Tested as
    Matches the bullet on AI for desktop flows.
    Trap
    Believing AI removes the need to test against the real application.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Flow types

ConceptMeaningKey differenceCommon trap
Automated cloud flow Starts on an event in a service. No user action needed to start. Using it for timed reports.
Instant cloud flow Starts when a user triggers it. User controls start time. Assuming it runs on events.
Scheduled cloud flow Starts on a recurrence. Time-driven, not event-driven. Choosing it for every-new-email scenarios.
Desktop flow Automates user interfaces with RPA. Works where no API exists. Picking it for SharePoint or Outlook tasks with connectors.

Attended versus unattended desktop flows

ConceptMeaningKey differenceCommon trap
Attended Runs on a machine with a signed-in user present. Good for helping staff during their work. Assuming it suits overnight batch work with no one present.
Unattended Runs on a machine without a user present. Good for back-office batch jobs. Forgetting it needs specific licensing and machine setup.

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. RPA for everything

    What candidates pick
    A desktop flow to copy SharePoint items to Outlook
    Why it looks right
    RPA sounds powerful and general.
    Why it's wrong
    SharePoint and Outlook have connectors, so a cloud flow is simpler, more reliable and needs no machine.

    Clue to watch for Named services with standard connectors.

  2. Cloud flow for a legacy screen

    What candidates pick
    A cloud flow to enter data into an old desktop app
    Why it looks right
    Cloud flows are the default automation type.
    Why it's wrong
    Without an API or connector, only a desktop flow can drive the application interface.

    Clue to watch for Phrases like legacy, no API, terminal or desktop application.

  3. Scheduled instead of automated

    What candidates pick
    A scheduled flow that checks for new form responses each hour
    Why it looks right
    Polling feels safe and predictable.
    Why it's wrong
    Forms offers an event trigger for new responses, so an automated flow reacts immediately without polling.

    Clue to watch for When a response is submitted or when an item is created.

  4. Custom app for approvals

    What candidates pick
    Build a Power Apps app to collect manager approvals
    Why it looks right
    Apps are familiar for collecting input.
    Why it's wrong
    The Approvals capability already sends requests to Outlook and Teams and records responses.

    Clue to watch for Sign-off, approve or reject wording.

  5. Multiple triggers

    What candidates pick
    Add a second trigger to the same cloud flow
    Why it looks right
    Some processes start from more than one event.
    Why it's wrong
    A cloud flow allows only one trigger; separate flows or a different design are needed.

    Clue to watch for Two different starting events in the stem.

  6. Copilot as autopilot

    What candidates pick
    Let Copilot build and deploy the flow without checks
    Why it looks right
    Generated flows look complete.
    Why it's wrong
    Makers must confirm connections, review steps and test before relying on the flow.

    Clue to watch for Mentions of reviewing, testing or production use.

Answer framework

Use these steps to choose and describe a Power Automate solution in a Domain 4 scenario.

  1. Ask whether every system involved has a connector; if one only offers a user interface, plan a desktop flow for that part.
  2. Identify how the process starts: an event means an automated flow, a person pressing a button means instant, and a time means scheduled.
  3. Name the trigger connector and the action connectors in order, such as Forms trigger, Approvals action, SharePoint action and Teams message.
  4. Check for document or AI needs, such as extracting invoice fields with AI Builder, and place that step before the data is used.
  5. If the scenario mentions building faster, describe how Copilot drafts the flow from natural language and how the maker reviews and tests the result.

Practice question

When an employee submits a Microsoft Forms equipment request, the request must go to their manager for a decision, and approved requests must be added to a SharePoint list. What should start this cloud flow?

Want more like this? The PL-900 practice test has questions for every domain.

Checklist

0 of 11

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Build three small cloud flows in a developer environment: an automated flow from a Forms response that creates a SharePoint item, an instant flow from a button that posts to Teams, and a scheduled flow that sends a weekly Outlook summary. Add an approval step to the first and watch the request arrive in Outlook and Teams. Recreate one of them by describing it to Copilot and compare the result with your manual version.

Next, install Power Automate for desktop on a Windows machine and record a simple task such as copying values into a spreadsheet. Try the Copilot help in the desktop designer and note what you had to correct. Read the overview of attended and unattended runs and of document processing models.

Wrap up by listing ten business processes and labelling each with flow type, trigger and main actions. That habit mirrors how questions in this domain are written.

FAQ

How much of PL-900 does Demonstrate the capabilities of Power Automate cover?

Demonstrate the capabilities of Power Automate is weighted at 20–25% of PL-900, an increase in the July 24, 2026 revision. Expect around ten questions.

Do I need to know expressions for PL-900?

No. Understand dynamic content and that expressions exist, but the exam describes flows at a capability level rather than testing expression syntax.

Is process mining still on the exam?

Process mining is not named in the current Power Automate bullets. Focus on cloud and desktop flows, Microsoft 365 scenarios, triggers and actions, and AI-assisted building.

What is the difference between attended and unattended desktop flows?

Attended flows run while a user is signed in and present, often started by that user. Unattended flows run on a machine with no one present and need extra licensing.

Which Microsoft 365 services should I know for flows?

The outline names approvals, Teams, Outlook, SharePoint and Forms, plus document automation. Know a typical trigger or action for each.

Can Copilot change an existing flow?

Yes. In the cloud flow designer you can ask Copilot to add, remove or change steps, then review the result. Similar help exists for desktop flows.

Other CRM & Business Applications certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 4 knowledge

Test whether you can pick the right flow type, trigger and actions for common business processes before you continue.

Take the PL-900 practice test Check your PL-900 readiness

Keep going