πŸ”’ Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided PL-900 Domain 4
Domain 4 β€” Module 4 of 6 67%
20 of 26 overall

PL-900 Study Guide

Domain 1: Business Value of Microsoft Power Platform

  • Welcome to Power Platform Free
  • Connectors & Dataverse: Your Data Foundation Free
  • Copilot & AI in Power Platform Free
  • Power FX: Formulas, Not Code Free
  • Power Platform + Microsoft 365: Better Together Free

Domain 2: Manage the Microsoft Power Platform Environment

  • What is Dataverse?
  • Tables, Columns, and Relationships
  • Building Tables with Copilot and Data Management
  • Environments and Security
  • Admin Centers and Governance

Domain 3: Demonstrate the Capabilities of Power Apps

  • Canvas Apps: Pixel-Perfect Apps from Scratch
  • Model-Driven Apps: Data-First Design
  • Connecting to Data Sources
  • Controls, Responsive Design, and Copilot
  • Sharing Canvas Apps
  • Building and Sharing Model-Driven Apps

Domain 4: Demonstrate the Capabilities of Power Automate

  • Cloud Flows: Automate Without Code
  • Desktop Flows and Process Mining
  • Approvals and Business Scenarios
  • Loops and Branching in Cloud Flows
  • Building a Cloud Flow
  • Testing and Sharing Cloud Flows

Domain 5: Demonstrate the Capabilities of Power Pages

  • Power Pages: External Websites Made Easy
  • Power Pages Security
  • Design Studio and Building Pages
  • Components, Themes, and Publishing

PL-900 Study Guide

Domain 1: Business Value of Microsoft Power Platform

  • Welcome to Power Platform Free
  • Connectors & Dataverse: Your Data Foundation Free
  • Copilot & AI in Power Platform Free
  • Power FX: Formulas, Not Code Free
  • Power Platform + Microsoft 365: Better Together Free

Domain 2: Manage the Microsoft Power Platform Environment

  • What is Dataverse?
  • Tables, Columns, and Relationships
  • Building Tables with Copilot and Data Management
  • Environments and Security
  • Admin Centers and Governance

Domain 3: Demonstrate the Capabilities of Power Apps

  • Canvas Apps: Pixel-Perfect Apps from Scratch
  • Model-Driven Apps: Data-First Design
  • Connecting to Data Sources
  • Controls, Responsive Design, and Copilot
  • Sharing Canvas Apps
  • Building and Sharing Model-Driven Apps

Domain 4: Demonstrate the Capabilities of Power Automate

  • Cloud Flows: Automate Without Code
  • Desktop Flows and Process Mining
  • Approvals and Business Scenarios
  • Loops and Branching in Cloud Flows
  • Building a Cloud Flow
  • Testing and Sharing Cloud Flows

Domain 5: Demonstrate the Capabilities of Power Pages

  • Power Pages: External Websites Made Easy
  • Power Pages Security
  • Design Studio and Building Pages
  • Components, Themes, and Publishing
Domain 4: Demonstrate the Capabilities of Power Automate Premium ⏱ ~13 min read

Loops and Branching in Cloud Flows

Make your flows smart with conditions, loops, and parallel branches. Learn how Power Automate handles decisions, repeating actions, and running steps side by side.

Why flows need logic

β˜• Simple explanation

Think of it like driving directions.

”Go straight until you reach the roundabout. If you are going to the hospital, take the second exit. If you are going to the shops, take the third exit.”

Without logic, your flow can only go in a straight line. With conditions and loops, it can make decisions, repeat steps, and handle different situations β€” just like real driving directions handle different destinations.

Most business processes are not simple straight lines. They involve decisions (if this, then that), repetition (do this for every item in the list), and parallel work (do these two things at the same time).

Power Automate provides built-in controls for all of these: Condition, Switch, Apply to each, Do until, and Parallel branches. These controls transform a simple linear flow into a smart workflow that handles real-world complexity.

Conditions (If/Then/Else)

A Condition action checks whether something is true or false, then runs different actions based on the result.

Structure:

  • If yes (true): Run these actions
  • If no (false): Run these actions

Carlos’s conditional routing

When a patient feedback form is submitted at Greenleaf Health, Carlos wants different things to happen based on the rating:

  • If the rating is 4 or 5: Send a thank-you email to the patient
  • If the rating is 1, 2, or 3: Send an alert to the clinic manager and create a follow-up task in Planner

One flow, two different paths. The condition decides which path to take.

πŸ’‘ Nesting conditions

You can put a condition inside another condition β€” this is called nesting. For example:

  • If rating is 5: Send thank-you and ask for a Google review
  • Else if rating is 4: Send thank-you only
  • Else if rating is 3: Send to manager
  • Else: Send to manager AND director

While nesting works, too many levels make flows hard to read. For multiple specific values, use a Switch instead.

Switch

A Switch action checks a value and runs different actions based on which case it matches. Think of it as a more organised version of multiple nested conditions.

Rating ValueAction
Case: 5Send thank-you, request review
Case: 4Send thank-you
Case: 3Alert clinic manager
Case: 2Alert manager, create task
Case: 1Alert manager and director, create urgent task
DefaultLog an error (unexpected value)

Switch vs Condition: Use a Condition when you have a true/false check. Use Switch when you have multiple specific values to match against. Switch keeps your flow cleaner than deeply nested conditions.

Apply to Each (Loops)

Apply to each repeats a set of actions for every item in a list or array.

Example: Carlos sends personalised emails

Carlos gets a list of 20 patients who have appointments tomorrow. He needs to send each one a reminder email with their specific appointment time.

Instead of building 20 separate email actions, he uses Apply to each:

  1. Get items from the Appointments SharePoint list (returns 20 rows)
  2. Apply to each item in the list:
    • Action: Send an email to the patient with their name and appointment time

The flow runs the email action 20 times β€” once for each patient. If there are 5 patients tomorrow, it runs 5 times. If there are 100, it runs 100 times. The loop adapts automatically.

ℹ️ Concurrency in Apply to Each

By default, Apply to Each processes items one at a time (sequentially). You can enable concurrency to process multiple items in parallel β€” up to 50 at a time.

This is useful when the actions inside the loop are independent of each other (like sending emails). It makes the flow run faster but the items may not process in order.

Enable concurrency in the settings of the Apply to Each action.

Do Until

Do until repeats actions until a condition becomes true. Unlike Apply to Each (which loops through a list), Do Until keeps running until you tell it to stop.

Example: waiting for a response

Carlos sends an approval request and needs to check every hour whether the approver has responded. He sets up:

  • Do until the approval status equals β€œCompleted”
    • Action: Wait 1 hour
    • Action: Check the approval status

The loop runs repeatedly until the condition is met. To prevent infinite loops, you set a count limit (maximum iterations) and a timeout (maximum duration).

Loop TypeIterates OverStops When
Apply to eachA list of itemsAll items are processed
Do untilNothing specific β€” just repeatsA condition becomes true (or limits are hit)

Parallel branches

Parallel branches let you run two or more sets of actions at the same time within a flow.

Example: Carlos’s onboarding

When a new hire is added at Greenleaf Health, Carlos needs to:

  • Branch 1: Create an account in the HR system and assign training
  • Branch 2: Order equipment and set up the workstation
  • Branch 3: Send welcome email and add to Teams channels

These three branches run simultaneously because they do not depend on each other. The flow is faster because it does not wait for Branch 1 to finish before starting Branch 2.

After all parallel branches complete, the flow can continue with a final step β€” like posting a summary message to the HR channel.

All flow controls at a glance

Flow Control Actions
ControlPurposeWhen to Use
ConditionIf/then/else branchingTrue or false decisions β€” two paths
SwitchMatch a value against multiple casesMultiple specific values β€” cleaner than nested conditions
Apply to eachLoop through a list of itemsProcess every item in a collection one by one
Do untilRepeat until a condition is metWait for something to happen or retry an action
Parallel branchesRun actions side by sideIndependent tasks that do not depend on each other

🎬 Video walkthrough

🎬 Video coming soon

Loops and Branching β€” PL-900 Domain 4

Loops and Branching β€” PL-900 Domain 4

~9 min

Flashcards

Question

What is a Condition action in Power Automate?

Click or press Enter to reveal answer

Answer

An if/then/else control that checks whether something is true or false, then runs different actions for each path. Every condition has a Yes branch and a No branch.

Click to flip back

Question

When should you use Switch instead of a Condition?

Click or press Enter to reveal answer

Answer

Use Switch when you have multiple specific values to check (like a rating of 1, 2, 3, 4, or 5). It is cleaner than nesting many conditions inside each other. Use Condition for simple true/false checks.

Click to flip back

Question

What does Apply to Each do?

Click or press Enter to reveal answer

Answer

It loops through a list of items and runs the same set of actions for each item. If there are 20 items, it runs 20 times. The number of iterations adapts to the list size automatically.

Click to flip back

Question

How is Do Until different from Apply to Each?

Click or press Enter to reveal answer

Answer

Apply to Each iterates over a list of items. Do Until repeats actions until a condition becomes true β€” it has no list. Do Until needs a count limit and timeout to prevent infinite loops.

Click to flip back

Question

What are parallel branches?

Click or press Enter to reveal answer

Answer

A flow control that runs two or more sets of actions at the same time. Used for independent tasks that do not depend on each other. The flow waits for all branches to finish before continuing.

Click to flip back

Knowledge Check

Knowledge Check

Carlos has a list of 50 patients and needs to send each one a personalised appointment reminder. Which flow control should he use?

Knowledge Check

What must you configure on a Do Until loop to prevent it from running forever?

Knowledge Check

Carlos needs to check a patient rating value and take different actions for ratings of 1, 2, 3, 4, and 5. Which flow control is the BEST choice?


Next up: Time to build a cloud flow from scratch. We will walk through creating instant, automated, and scheduled flows β€” including using Copilot to describe a flow in plain English.

← Previous

Approvals and Business Scenarios

Next β†’

Building a Cloud Flow

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.