If you do not understand Power Automate, you will waste hours every week doing the same manual tasks over and over — copying data from one system to another, sending repetitive emails, and chasing approvals. This chapter introduces Power Automate, Microsoft's tool for automating routine digital work. For the PL-900 exam, you need to know the different types of flows it offers and when to use each one.
Jump to a section
A simple way to picture Introduction to Power Automate
Every weekday morning at 7:15 AM, your personal assistant receives a text from your calendar app reminding them of your 10:00 AM dentist appointment. They immediately check your location on your phone and see you are at home. They text you: "Traffic on the M1 is heavy today. Leave by 9:00 AM to reach SmileCare Dental on time." At 9:30 AM, they send another text: "Your appointment is in 30 minutes. Don't forget the parking voucher in your wallet."
This is exactly how Power Automate works. Your assistant is the flow, triggered by the calendar event (a trigger). They check your location data (a condition) and send you tailored messages (actions). Before this assistant existed, you had to manually check your calendar, guess traffic, and remember to leave early. Power Automate does this for digital tasks — automatically moving data between apps like Microsoft Outlook, SharePoint, and Teams, and making decisions based on conditions you set. The assistant never sleeps, never forgets, and follows your rules perfectly every time.
The key parts map precisely: the calendar notification is the "trigger" (what starts the flow), checking your location is a "condition" (a decision point), and sending the text is an "action" (what the flow does). Unlike a human assistant, Power Automate can handle thousands of these workflows simultaneously, across hundreds of different software applications, without ever taking a coffee break.
Power Automate is a cloud-based service from Microsoft that lets you create automated workflows between your favourite apps and services. A "workflow" is simply a series of steps that happen automatically — like when you receive an email, save an attachment to OneDrive, and then send a Slack message to your team. Before Power Automate, you would do all those steps yourself. Now, the machine does them for you.
To understand Power Automate, you need to know its four main types of flows. Each type is designed for a different kind of automation scenario. The exam (PL-900) will ask you to match a business problem to the correct flow type. Let us break them down.
Automated flows (also called "trigger-based flows") start when an event happens in a connected app. For example: when a new email arrives in your Outlook inbox with an attachment, an automated flow can save that attachment to a SharePoint document library and send you a confirmation text. The flow runs automatically without you pressing a button. The "trigger" is the incoming email. The "actions" are saving the attachment and sending the text. Automated flows are ideal for repetitive tasks that happen on a schedule or when a specific event occurs.
Instant flows start when you manually press a button. They are designed for one-click automations. For example, you could create a button on your mobile phone that, when tapped, sends your current location to your manager via Teams message and logs the time in a spreadsheet. The flow does not run until you tell it to. Instant flows are perfect for tasks you want to trigger on demand, like approving a purchase order or logging a support ticket.
Scheduled flows run at a specific time or on a recurring schedule. You set the day and time — for example, every Monday at 9:00 AM — and the flow performs its actions. A common use is a weekly report: on Friday at 5:00 PM, a scheduled flow collects data from a SharePoint list, builds a summary in Excel, and emails it to your team. Scheduled flows are great for routine, time-based tasks that happen daily, weekly, or monthly.
Business process flows (BPFs) are different from the others. They do not automate actions in the background. Instead, they guide a person through a series of steps that must be completed in a specific order. For example, when a customer submits a support request, a BPF ensures the support agent first reads the issue, then escalates it to a manager, then sends a response — and cannot skip steps. BPFs enforce consistency and compliance in human processes.
Power Automate connects to hundreds of apps through "connectors". A connector is a pre-built bridge between Power Automate and another service, like Microsoft Teams, Salesforce, Twitter, or Gmail. Each connector provides a set of triggers and actions you can use in your flows. For example, the Microsoft Entra ID connector lets you manage user accounts; the Outlook connector lets you send email.
Why does all this matter? Because automation saves time, reduces errors, and frees you up for higher-value work. Instead of copying and pasting data for an hour, you build a flow once and let it run forever. For the PL-900 exam, you must be able to identify which flow type fits a given business requirement. The exam questions often describe a scenario and ask: "Which type of flow should be used?"
Identify the Trigger
The trigger is the event that starts the flow. For an automated flow, this could be 'When a new email arrives' or 'When a new item is created in SharePoint'. Without a trigger, the flow cannot start. In the designer, you pick a trigger from the chosen connector's list.
Add Actions
Actions are the steps the flow performs. For example, after a trigger fires, you may add an action to send an email, create a file, or update a record. Actions are also provided by connectors. You can add multiple actions in sequence.
Add Conditions and Loops
You can add decision points using conditions (e.g., 'If the amount is over £500, send to manager'). You can also add loops to repeat actions for multiple items, like processing every row in a spreadsheet.
Test the Flow
Before going live, you test the flow using sample data. Power Automate shows you a real-time log of each step — whether it succeeded, failed, or skipped. This helps you debug errors without affecting real business data.
Turn On and Monitor
Once tested, you turn the flow on. It runs automatically (for automated flows) or on demand (for instant flows). You monitor its health using the run history page, where you can see every execution, any failures, and re-submit failed runs.
An IT professional at a mid-sized company called "GreenLeaf Logistics" uses Power Automate to solve a real problem. Every day, the sales team receives hundreds of new customer orders via email. Each order needs to be entered into a SharePoint list for processing, and the customer should receive a confirmation email. Doing this manually takes a sales assistant three hours each morning.
The IT professional builds an automated flow. Here is how it works step by step:
Step 1: The flow uses an Outlook connector with a trigger: "When a new email arrives". The trigger is set to only fire when the email subject contains the word "Order" and the email has an attachment.
Step 2: An action parses the email body and attachment (a PDF order form) to extract the customer name, order ID, product list, and total amount. This uses a "Compose" action with a formula to read the PDF content.
Step 3: Another action creates a new row in a SharePoint list called "OrderProcessing". It maps the extracted data to columns: Customer Name, Order ID, Products, Amount, Status (set to "New").
Step 4: A condition checks if the order total is over £1,000. If yes, a Teams message is sent to the finance manager for approval. If no, the flow continues to the next step.
Step 5: An action sends a confirmation email to the customer using an Outlook connector. The email body is dynamically generated from the extracted data, including the order ID and expected delivery date.
Step 6: Finally, an instant flow button is added to the sales team's mobile app so they can manually trigger a summary report at any time, pulling all orders from the last 24 hours.
The IT professional also sets up a scheduled flow that runs every Sunday at midnight to archive old orders (over 90 days old) from the SharePoint list to an Excel file stored in OneDrive. This keeps the main list fast and manageable.
What was a three-hour manual job now takes zero human effort. The IT professional monitors the flow using the Power Automate run history, which shows every execution, any errors, and how long each step took. If an email arrives with a corrupted attachment, the flow fails and sends an alert. The IT professional can then manually intervene.
The PL-900 exam loves testing your ability to distinguish between the four flow types. Expect at least 2-3 questions on this topic. The question format is almost always a scenario followed by "Which type of flow should they use?"
Here are the specific concepts the exam tests:
Automated vs. Instant vs. Scheduled vs. Business process flows - The exam gives you a business problem. You must pick the correct flow type. Traps include describing a trigger that sounds like an instant flow but is actually automated, or describing a step-by-step human process that is actually a business process flow.
Key definitions to memorise: - "Trigger" — an event that starts a flow (e.g., new email, new row in Excel). - "Action" — a step that does something (e.g., send email, create file). - "Connector" — a pre-built link to a service (e.g., Outlook, SharePoint, Twitter). - "Run history" — a log of every execution of a flow, including success/failure. - "Dynamic content" — values that change per run (e.g., the subject line of the email that triggered the flow).
Common traps on the exam: - They may describe a flow that runs every morning at 8:00 AM and ask which type it is. The answer is "scheduled flow", but some candidates mistake it for an automated flow because it runs automatically. Remember: "scheduled" means time-based; "automated" means event-based. - They may ask about a flow that a user starts by pressing a button in Teams. That is an instant flow, not automated. - They may describe a "business process flow" as something that automatically sends an email — that is wrong. BPFs guide human steps, they do not automate actions in the background.
Scenario patterns to watch: - "Every time a new file is added to SharePoint" — automated flow. - "Every week on Monday at 9 AM" — scheduled flow. - "When a customer submits a complaint, ensure the agent completes three steps in order" — business process flow. - "When I press this button in my mobile app" — instant flow.
The exam also tests whether you know that Power Automate is part of the Microsoft Power Platform, alongside Power Apps (for building apps), Power BI (for data visualisation), and Power Virtual Agents (for chatbots). Flows can connect to all of these.
Power Automate has four flow types: automated, instant, scheduled, and business process flows — each designed for a different automation scenario.
An automated flow is triggered by an event (like a new email), not by a clock or a human pressing a button.
A scheduled flow runs at a specific time or on a recurring schedule, regardless of other events.
An instant flow requires a human to manually start it, for example via a button in Microsoft Teams or a mobile app.
A business process flow guides a person through a series of required steps, it does not automate background tasks.
Connectors are pre-built bridges to apps like Outlook, Salesforce, and Twitter — they provide the triggers and actions you use in flows.
These come up on the exam all the time. Here's how to tell them apart.
Automated Flow
Triggered by an event like new email or new file
Runs continuously as events occur
No human interaction needed to start
Scheduled Flow
Triggered by a clock (time of day or recurring interval)
Runs at fixed times regardless of events
No human interaction needed to start
Instant Flow
Started manually by a human pressing a button
Runs only when someone triggers it
Used for on-demand tasks like approvals
Automated Flow
Started automatically by an event
Runs without human input
Used for continuous background automation
Business Process Flow
Guides a human through steps
Does not automate background actions
Enforces order of human tasks
Automated Flow
Automates digital actions
Runs in the background without human interaction
Performs tasks like sending emails or updating records
Power Automate
Creates automated workflows
No user interface for end users
Runs in the background or on button click
Power Apps
Creates custom apps with buttons, forms, and screens
End users interact directly with the app
Requires a canvas or model-driven app design
Mistake
Power Automate can only work with Microsoft apps like Outlook and SharePoint.
Correct
Power Automate connects to hundreds of third-party apps like Gmail, Salesforce, Twitter, Dropbox, and many more through connectors. It is not limited to Microsoft ecosystem.
Beginners assume Microsoft's product only talks to other Microsoft products, but the Power Platform is designed to integrate with everything.
Mistake
All flows run on a schedule, like a cron job.
Correct
Automated flows run based on events (like a new email), instant flows run on demand, and scheduled flows run on a time-based schedule. Only one of the four types uses time triggers.
People hear 'automation' and think 'scheduled'. They miss the event-driven nature of automated flows.
Mistake
You need to know how to write code to create a flow.
Correct
Power Automate uses a drag-and-drop designer. You do not write code. You select triggers, actions, and conditions from dropdowns and form fields.
Many beginners come from a traditional programming background or have only used scripting tools. They fear automation means coding.
Mistake
A business process flow automates actions like sending emails and creating records.
Correct
A business process flow guides a human through a series of steps. It does not perform automated actions. It ensures consistency in human-driven processes.
The name 'flow' is misleading — people think all flows automate tasks. BPFs are for guidance, not automation.
Mistake
Once a flow is created, it runs forever with no management needed.
Correct
Flows can fail due to errors (e.g., a connector is down, data format changes). You need to monitor run history and fix issues. Flows also use licenses and may have run limits.
People think automation is 'set and forget'. In reality, business data changes, and flows need maintenance.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Yes, a Microsoft 365 license includes basic Power Automate capabilities, but advanced features like robotic process automation (RPA) and premium connectors require a per-user or per-flow license (Power Automate Plan 1 or 2).
Yes, using the on-premises data gateway. This is a software component you install on a local server that allows Power Automate to connect to databases like SQL Server and file shares inside your company network.
A connector is a pre-built wrapper that lets Power Automate talk to a specific app or service. It provides triggers (events) and actions (operations) for that service. For example, the Outlook connector gives you triggers like 'When a new email arrives' and actions like 'Send an email'.
Power Automate automates workflows and processes (tasks that happen automatically or on demand). Power Apps is for building custom apps with user interfaces. They often work together: a Power Apps button can trigger a Power Automate flow.
A desktop flow (also called robotic process automation or RPA) automates tasks on a Windows desktop, like opening a legacy application, clicking buttons, and entering data. This is different from cloud flows, which work with cloud apps via connectors.
Yes, you can share a flow by adding other users as owners or co-owners. They can then edit or manage the flow. You can also share flows as templates so others can create their own copies.
You've finished Introduction to Power Automate. Continue through the PL-900 study guide to build a complete picture of the exam.
Done with this chapter?