An automated cloud flow is a set of instructions that runs automatically when a specific event happens, like a new email arriving or a row being added to a Microsoft Dataverse table. This matters for your PL-900 exam because Microsoft wants you to understand how business users can save time by automating repetitive tasks without writing any code. Instead of manually moving files, sending approval emails, or updating spreadsheets, a cloud flow handles it the same way every time.
Jump to a section
A simple way to picture Creating Automated Cloud Flows
A typical supermarket self-checkout area.
You scan your shopping, bag it, and tap your card to pay. That is a manual process — you do every step yourself. Now imagine this: the moment you walk through the supermarket door, your phone automatically syncs your shopping list, the fridge at home senses you are out of milk and adds it to your list, and the checkout machine charges your account the second the last item is scanned. That sequence of automatic actions, triggered by a single event (you walking in), is exactly what an automated cloud flow does in Power Automate.
In our analogy, the "trigger" is you entering the store. The "actions" are the phone syncing the list, the fridge adding milk, and the checkout charging your card. The whole chain runs without you pressing any buttons once it is set up. In the real Power Platform, a trigger might be a new email arriving in a shared inbox. The actions that follow could include saving the email's attachment to OneDrive for Business, posting a message to a Microsoft Teams channel to tell the team, and creating a task in Microsoft To Do for follow-up. Just like the self-checkout sequence, the cloud flow runs automatically every time that trigger happens — no human hands needed after the initial setup.
This analogy cannot describe any other IT concept because it specifically mirrors the trigger-actions architecture of Power Automate cloud flows. A router, a database, or a virtual machine all lack this cause-and-effect automation sequence.
An automated cloud flow is a type of automation that runs in the cloud — on Microsoft's servers — without you opening any app or clicking any button to start it. The key idea is "if this happens, then do that." Microsoft Power Automate lets you build these flows using a visual designer, not programming code.
At the heart of every automated cloud flow are two main parts: a trigger and one or more actions.
A trigger is the event that starts the flow. For example, "When a new email arrives in my Outlook inbox" is a trigger. The flow sits and waits for that event. The moment it happens, Power Automate wakes up and runs the flow. Triggers can come from hundreds of different services: Microsoft 365 apps like Outlook, Teams, and SharePoint, but also third-party services like Twitter, Gmail, or Salesforce.
An action is something the flow does after the trigger fires. For a new email trigger, an action might be "Save the attachment to OneDrive for Business" or "Send a notification to my phone." You can add multiple actions in order. The output of one action can feed into the next action. For instance, the file name saved to OneDrive could be used in a Teams message.
Automated cloud flows replace boring, repetitive manual work. Imagine a salesperson who receives fifty order emails per day. Without a flow, they would manually open each email, download the PDF, rename the file, save it to a folder, and reply to confirm. With an automated cloud flow, this all happens in seconds, every time, with no mistakes.
To build an automated cloud flow, you start in the Power Automate maker portal at make.powerautomate.com. You select a template or start from blank. The designer shows a canvas where you drag and connect steps. Each step is either a trigger or an action. You configure each step by filling in simple fields, like which folder to save a file to or what message text to send.
There are three main types of flows in Power Automate, and you need to know the difference for the exam:
Automated cloud flows: triggered by an event, no human intervention needed.
Instant cloud flows: started by a user clicking a button in an app or on a mobile device.
Scheduled cloud flows: run at a specific time every day, week, or month.
Automated cloud flows are the most common and the most powerful for eliminating manual work. They are the focus of PL-900 objective 4.2.
When you create a flow, Power Automate stores it in the cloud, inside a Microsoft Dataverse environment. This means the flow keeps running even if your computer is turned off. It runs on Microsoft's infrastructure, which handles reliability, scaling, and security.
For beginners, the most important technical term to grasp is "connector." A connector is a pre-built wrapper that lets Power Automate talk to a service like Outlook, SharePoint, or Twitter. Each connector comes with its own set of triggers and actions. There are hundreds of connectors. When you pick a trigger or action, you are actually using a connector behind the scenes.
Another essential concept is "dynamic content." When a trigger fires, it captures information about that event, like the email subject line or the sender's address. Dynamic content lets you use that captured data in later actions. For example, you can insert the email subject line into a Teams message so the message reads "New order received: [subject line here]." The square brackets get replaced with the actual subject when the flow runs.
An automated cloud flow can also include conditions (if-then logic), loops (repeat an action for each item in a list), and parallel branches (run multiple actions at the same time). These advanced features let you build fairly complex logic without writing any code.
The exam tests whether you can identify what an automated cloud flow does, when to use one instead of an instant or scheduled flow, and how triggers and actions relate. You will also need to recognise common connectors like Outlook, Teams, SharePoint, and Microsoft Dataverse.
Sign in to the Power Automate maker portal
Go to make.powerautomate.com and sign in with your work or school Microsoft account. This is the web interface where you create, manage, and monitor all your flows. Without signing in, you cannot access any Power Automate features.
Create a new automated cloud flow
Click 'Create' in the left navigation menu, then select 'Automated cloud flow.' This tells Power Automate that you want a flow that starts when an event happens, not a flow that requires a button click or runs on a schedule. The flow type is selected at this step and cannot be changed later without creating a new flow.
Choose a trigger
A list of thousands of triggers appears. Search for or select the service that contains your trigger event. For example, choose 'Outlook' and then the trigger 'When a new email arrives.' This is the event that will start the flow. You must configure any required fields, like which mailbox to monitor or a specific subject filter. The trigger defines the flow's starting point.
Add an action
After the trigger is set, click 'New step' to add an action. Search for the service and action you need. For a new email trigger, you might add 'Get attachment' to retrieve files from the email. Each action requires configuration: you pick the file to get, the folder to save it to, etc. Actions do the actual work of the flow.
Test and turn on the flow
Before using the flow in production, click 'Test' to run a trial. You can send yourself a test email or use sample data. If the flow runs without errors, save it and turn the toggle to 'On.' Once on, the flow will trigger automatically whenever the trigger event occurs. Testing prevents mistakes that could cause incorrect actions in the real world.
Consider Lisa, a human resources coordinator at a mid-sized company. Every week, she receives twenty to thirty new employee onboarding requests from managers. Each request comes as an email with a PDF attachment containing the new hire's details. Until she automated the process, Lisa would do the following manual steps for each email:
Open the email.
Download the PDF attachment to her Downloads folder.
Manually rename the PDF to the new employee's name and start date.
Upload the renamed file to a specific SharePoint folder for onboarding documents.
Send a confirmation email back to the manager who submitted the request.
Create a new employee record in Microsoft Dataverse so the IT team knows to set up a laptop.
These six simple steps took Lisa roughly three to four minutes per request. Multiply that by twenty-five requests per week, and she was spending nearly two hours on a chore that added zero strategic value. Worse, she sometimes forgot to rename a file or accidentally uploaded it to the wrong folder.
Lisa used Power Automate to build an automated cloud flow. She chose the trigger "When a new email arrives in a shared mailbox" and configured it to watch for emails with a specific subject line containing "New Hire." The flow then expanded into these actions:
Action 1: Get the attachment from the email (using the Outlook.com connector).
Action 2: Create a file in a SharePoint document library with the file name set to dynamic content: the new hire's name from the email body plus the date.
Action 3: Send a confirmation email back to the original sender with a link to the uploaded file.
Action 4: Create a new row in a Microsoft Dataverse table called "New Hires" with columns for name, department, start date, and manager email.
Lisa tested the flow by sending herself a mock email. It worked perfectly. After that, she never manually processed another new hire request. The flow ran every time a matching email arrived, twenty-four hours a day, seven days a week.
The real-world impact: Lisa saved over an hour and a half per week. Errors dropped to zero. The IT team started receiving new hire records in Dataverse immediately instead of waiting for Lisa to manually create them. Managers got faster confirmation emails. The business saved money because Lisa could focus on more important work, like improving the onboarding experience for new employees.
For the PL-900 exam, this scenario illustrates exactly what an IT professional does with automated cloud flows: identify a repetitive, rules-based manual process, then build a flow that automates it using triggers, actions, connectors, and dynamic content. You do not need to know how to build a flow from scratch on the exam, but you do need to recognise which type of flow fits a given scenario and understand the basic components.
The PL-900 exam tests objective 4.2 in several specific ways. You will get scenario-based questions that present a business problem and ask which type of flow or which component to use. Here is exactly what you need to know:
Exam topics that appear most often:
Distinguishing between the three flow types: automated, instant, and scheduled. The exam loves to describe a situation and ask you to pick the right type. If the scenario says "when a new tweet is posted," the answer is automated cloud flow. If it says "every Monday at 9 AM," the answer is scheduled cloud flow. If it says "user clicks a button in a SharePoint list," the answer is instant cloud flow.
Identifying the trigger in a given description. The question might say "An order form is submitted. This starts the flow." The trigger is the form submission event.
Identifying an action in a given description. For example, "After the form is submitted, an email is sent to the manager." The send-email step is an action.
Recognising connectors as the bridge between Power Automate and a service. Questions will list services like Outlook, Teams, and SharePoint and ask what enables the flow to talk to them — the answer is connectors.
Understanding that an automated cloud flow runs in the cloud without needing a user to be logged in.
Knowing that flows can use conditions, loops, and parallel branches, though the exam will not ask you to write them.
Common traps Microsoft sets in the exam:
They will try to confuse an instant cloud flow (needs a user click) with an automated cloud flow (runs automatically). If the description mentions someone pressing a button, it is instant, not automated.
They will include a distractor answer like "business process flow" which is a different type of automation in Power Automate, used for guiding users through a multi-step process manually. Automated cloud flows do not require user interaction.
They will write a scenario where a flow should run at a specific time. The correct answer is scheduled cloud flow, but they might phrase it to sound like an automated flow. Watch for keywords: "every day at 5 PM" means scheduled.
They might test the difference between a trigger and an action. A classic question: "What starts the flow?" That is the trigger. "What happens next?" Those are actions.
Key definitions to memorise for the exam:
Trigger: The event that starts an automated cloud flow.
Action: A step that runs after the trigger, doing something like sending a message or creating a file.
Connector: A wrapper that allows Power Automate to interact with a service.
Dynamic content: The data captured from the trigger or previous actions that can be reused in later steps.
Automated cloud flow: Runs when a specific event occurs, no user interaction required.
Instant cloud flow: Runs when a user presses a button.
Scheduled cloud flow: Runs on a set schedule.
You will not be asked to memorise specific connector names outside of major ones like Outlook, Teams, SharePoint, Dataverse, and OneDrive for Business. Focus on understanding the concept, not the exact configuration steps.
An automated cloud flow runs automatically when a trigger event occurs, with no human interaction required.
A trigger starts the flow; actions are the steps that follow the trigger.
Connectors are the bridges that let Power Automate communicate with services like Outlook, Teams, SharePoint, and Twitter.
Dynamic content lets you reuse data from one step in later steps, making flows adaptable to each trigger event.
Automated cloud flows run in the Microsoft cloud, so your computer does not need to be on or logged in.
The three main flow types are automated (event-driven), instant (button-click), and scheduled (time-based).
These come up on the exam all the time. Here's how to tell them apart.
Automated Cloud Flow
Starts automatically when a trigger event occurs (e.g., new email)
No user interaction needed after setup
Runs even when the user is not logged in
Instant Cloud Flow
Starts only when a user clicks a button (e.g., in a mobile app)
Requires a human to actively start it
Cannot run automatically without a user action
Automated Cloud Flow
Runs in response to an event
Can run many times a day if events occur
Best for reactive processes like responding to form submissions
Scheduled Cloud Flow
Runs at a fixed time or interval (e.g., every Monday at 9 AM)
Runs on a schedule regardless of events
Best for periodic tasks like daily data cleansing or report generation
Trigger
The event that starts the flow
There is exactly one trigger per flow
Examples: new email, new row in Dataverse, tweet posted
Action
A step that runs after the trigger
A flow can have many actions
Examples: send email, save file, create record
Connector
A bridge between Power Automate and a service
Examples: Outlook connector, SharePoint connector, Twitter connector
Each connector provides its own set of triggers and actions
Dynamic Content
Data captured from the trigger or previous actions
Used to insert values into later steps (e.g., subject line in an email)
Available as a dropdown in the flow designer after the trigger is configured
Automated Cloud Flow
Runs automatically in the cloud
No manual steps required after trigger
Designed for complete automation of digital tasks
Business Process Flow
A guided manual workflow that users follow in an app
Requires user interaction at each stage
Designed for processes that need human decisions, like approvals or data entry
Mistake
Automated cloud flows require me to keep my computer turned on and logged in for them to run.
Correct
Automated cloud flows run entirely in the Microsoft cloud. They execute on Microsoft's servers, so your personal computer can be switched off or asleep. The flow only stops if you turn it off or delete it.
People are used to macros or scripts they run locally on their own machines, so they naturally assume a similar dependency. The cloud aspect is abstract to beginners.
Mistake
An automated cloud flow is the same thing as a business process flow.
Correct
An automated cloud flow runs automatically based on a trigger and requires no human interaction. A business process flow is a guided step-by-step experience that a user navigates manually in an app like Dynamics 365 or a canvas app. They are two distinct features in Power Automate.
Both contain the word 'flow,' and the official Microsoft documentation sometimes lists them under the same Power Automate umbrella. Beginners conflate them because of the shared vocabulary.
Mistake
I need to know how to write code to create an automated cloud flow.
Correct
Power Automate uses a visual, no-code designer. You drag and drop actions, configure them with dropdowns and text fields, and use dynamic content. No programming language is required. The exam does not test code.
Most automation tools historically required scripting or programming. Beginners assume any automation tool is technical, but Power Automate specifically targets business users without coding skills.
Mistake
An automated cloud flow can only use Microsoft services like Outlook and SharePoint.
Correct
While Microsoft services are common, Power Automate has hundreds of connectors for non-Microsoft services such as Twitter, Salesforce, Gmail, Dropbox, Google Drive, and many more. The trigger or action can come from any service that has a published connector.
Microsoft markets Power Platform as part of the Microsoft ecosystem, so beginners assume it only works inside that ecosystem. The breadth of third-party connectors is not obvious until you explore the connector gallery.
Mistake
Once I create an automated cloud flow, I cannot edit it without breaking it.
Correct
You can edit a flow at any time after creation. Power Automate saves your changes as a new version. You can also turn the flow off, edit it, and turn it back on. The exam does not test versioning, but it is safe to know flows are editable.
People think of flows like static scripts that must be perfect from the start. In reality, Power Automate is designed to be iterative and easy to modify.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
You can create and run a limited number of automated cloud flows with a free Microsoft Power Automate license. For unlimited runs or premium connectors, you need a paid plan (Power Automate Per User or Per Flow). The PL-900 exam does not require you to memorise licensing details.
Yes, a flow can perform actions that delete or modify data. That is why testing is important before turning a flow on. Power Automate does not have an undo button for actions already executed, so always test with sample data first.
A trigger is the event that starts the flow. An action is a step that the flow performs after the trigger fires. Every flow has exactly one trigger, but can have many actions.
Yes, as long as a connector for that service exists in the Power Automate connector gallery. Gmail has a connector that provides triggers (like 'When a new email arrives') and actions (like 'Send an email').
The flow will not run. Trigger events that occur while the flow is off are not queued or replayed. You must have the flow set to 'On' for it to respond to events. Enable the flow first, then future events will trigger it.
You can share a flow by adding co-owners from the flow's details page. Co-owners can edit and manage the flow. If the flow uses connections (like your Outlook account), those connections are owned by you and may not work for others unless they add their own accounts.
You've finished Creating Automated Cloud Flows. Continue through the PL-900 study guide to build a complete picture of the exam.
Done with this chapter?