This chapter covers Power Automate, Microsoft's cloud-based workflow automation service within the Microsoft 365 ecosystem. For the MS-900 exam, understanding Power Automate is essential as it tests your knowledge of how to automate repetitive tasks and integrate various Microsoft 365 apps and third-party services. Approximately 10-15% of exam questions in Domain 2.4 (Productivity Solutions) relate to Power Automate capabilities, licensing, and common use cases. This chapter will equip you with the technical depth needed to answer scenario-based questions confidently.
Jump to a section
Imagine a factory that produces custom gift baskets. Without automation, a worker receives an order, walks to the shelves to pick items, packs them, prints a label, and calls a courier. This is manual, slow, and error-prone. Now, imagine an automated assembly line: when an order arrives (trigger), a conveyor belt (Power Automate) moves the order to a robotic arm that picks items based on a checklist (condition), then another machine wraps the basket and prints a shipping label (action), and finally a signal alerts the courier's system to pick up (integration). The entire process runs without human intervention, following a precise sequence of steps defined in a flowchart. Power Automate works the same way: it listens for events (triggers), evaluates conditions (e.g., if email contains 'urgent'), and executes actions (e.g., create a task in Planner, send a Teams message). Each step is a connector to a service (SharePoint, Outlook, Salesforce), and the flow runs in the cloud on Microsoft's infrastructure, handling retries, errors, and parallel branches automatically. Just as a factory can have multiple assembly lines for different products, you can have multiple flows for different business processes, all running concurrently.
What is Power Automate?
Power Automate (formerly Microsoft Flow) is a SaaS offering that enables users to create automated workflows between apps and services to synchronize files, get notifications, collect data, and more. It is part of the Microsoft Power Platform, alongside Power Apps and Power BI. The core value proposition is to eliminate manual, repetitive tasks by defining triggers, conditions, and actions in a visual designer. The exam focuses on understanding the types of flows, licensing, and integration capabilities.
How It Works Internally
Each flow consists of three core components: a trigger, one or more actions, and optional conditions. When a trigger event occurs (e.g., a new email arrives, a SharePoint item is created), Power Automate's cloud service evaluates the flow definition and executes the actions sequentially or in parallel. The flow definition is stored as a JSON document in the Common Data Service (now Microsoft Dataverse) or in the flow creator's personal context. The runtime engine is hosted in Azure and uses connectors to interact with external services. Each connector is a wrapper around the service's API, handling authentication, rate limiting, and data transformation. For example, the SharePoint connector uses OAuth 2.0 to authenticate and then calls SharePoint REST APIs to perform CRUD operations. Power Automate also includes a built-in AI Builder for processing forms, text, and images.
Key Components, Values, Defaults, and Timers
Triggers: Types include automated (event-based), instant (button), scheduled (recurrence), and trigger conditions. Common triggers: 'When a new email arrives' (Outlook), 'When an item is created' (SharePoint), 'When a HTTP request is received' (custom API).
Actions: Over 400 connectors including Microsoft 365 (Outlook, Teams, SharePoint, OneDrive, Dynamics 365), third-party (Salesforce, Twitter, Dropbox), and custom connectors.
Conditions: Use 'Condition' control to branch logic based on expressions (e.g., equals, greater than). Also supports 'Switch' for multiple cases.
Loops: 'Apply to each' iterates over arrays; 'Do until' repeats until condition met.
Concurrency: Default concurrency is 1 (sequential), but can be increased up to 50 for parallel execution (affects throttling).
Retry policy: Default retry count is 4 with exponential backoff (interval increases by factor of 2, starting at 10 seconds). Max retry count is 90.
Timeout: HTTP request timeout is 120 seconds for synchronous calls; for asynchronous patterns, use 'Response' action with a 1-minute timeout.
Run history: Retained for 28 days (default) but can be changed to 7, 30, or 90 days.
Limits: Max flow run duration is 30 days (including retries). Max number of actions per flow is 250. Max size of request/response payload is 100 MB.
Licensing: Power Automate is included with Microsoft 365 Business Basic and above (limited flows). Premium connectors require a Power Automate Plan 1 or 2 (or per-user/per-flow licenses). The exam tests the distinction between standard and premium connectors.
Configuration and Verification
Flows are designed via the Power Automate web portal (make.powerautomate.com) or mobile app. To verify a flow: use the 'Run history' tab to view each execution's status (Succeeded, Failed, Cancelled). Each run shows input/output for every action, with error messages. For debugging, use the 'Peek code' feature to view the underlying JSON definition. To test a flow manually, use the 'Test' button in the designer, which runs the flow with sample data. For scheduled flows, set the recurrence interval: minute (1-1440), hour (1-24), day (1-365), week (1-52). Example recurrence expression: {'interval': 1, 'frequency': 'Day'}.
Integration with Related Technologies
Power Automate integrates deeply with the Power Platform: flows can be triggered from Power Apps (via 'When a button is clicked' trigger) and can write data to Dataverse. It also integrates with Microsoft Teams (adaptive cards, approvals), SharePoint (list item operations), Outlook (email, calendar), and Azure services (Logic Apps, Functions). For advanced scenarios, use the 'HTTP with Azure AD' connector to call any REST API. The exam may ask about the relationship: Power Automate handles workflow automation, while Power Apps builds custom apps, and Power BI provides analytics.
Exam-Specific Technical Details
Flow types: Automated (triggered by event), Instant (manual trigger, e.g., button), Scheduled (time-based), and Business Process Flow (guided process with stages and steps). Business Process Flows are part of Dynamics 365 but are considered a type of flow in Power Automate.
Approvals: Power Automate includes a built-in approval action that creates an approval request in the Approvals center (accessible in Teams, mobile, web). Approvals can be sequential or parallel, with options for 'Approve', 'Reject', and custom responses.
AI Builder: Allows adding AI models (form processing, object detection, text classification) to flows without coding. Requires AI Builder credits (included in some Power Automate plans).
Desktop flows (RPA): Power Automate Desktop enables robotic process automation for legacy applications. Requires a separate license (Power Automate Process plan).
Co-authoring: Flows can be shared with other users who can edit (requires co-owner permission) or only run (run-only permissions).
Data Loss Prevention (DLP) policies: Admins can restrict which connectors can be used together (e.g., prevent data from SharePoint being sent to non-Microsoft services).
Common Exam Traps
Confusing Power Automate with Logic Apps: Power Automate is for business users (citizen developers) with a low-code designer; Logic Apps is for professional developers with more advanced features (e.g., integration accounts, enterprise integration). Both use similar connectors but different pricing and governance.
Assuming all connectors are included with Microsoft 365: Many premium connectors (e.g., Salesforce, SQL Server, custom connectors) require a separate Power Automate license.
Misunderstanding trigger types: A 'scheduled' flow does not require a trigger condition; it runs at specified times. An 'automated' flow always starts with a trigger that waits for an event.
Forgetting about run history retention: Only 28 days by default; for compliance, export run history using Azure Log Analytics or export to CSV.
1. Identify the Trigger Event
Every flow begins with a trigger. In the Power Automate designer, you select a trigger from hundreds of connectors. For example, 'When a new email arrives' (Outlook) triggers on any new email in the specified folder. You can add trigger conditions (e.g., only if subject contains 'Invoice'). The trigger polls the source service at intervals (typically every 1-5 minutes for most connectors, but can be as low as 15 seconds for some premium connectors). When the event occurs, the trigger fires and passes a payload (e.g., email subject, body, attachments) to the next step.
2. Add Conditions and Loops
After the trigger, you can add 'Condition' controls to branch logic. For example, check if the email's priority is 'High'. Under the condition, add actions for the 'Yes' branch (e.g., send a Teams message) and 'No' branch (e.g., ignore). For iterating over items (e.g., all attachments), use 'Apply to each' loop. Each loop runs sequentially by default, but you can configure concurrency. The loop variable (e.g., attachment name) is available in actions inside the loop. Use 'Do until' to repeat actions until a condition is met (e.g., wait for approval status).
3. Configure Actions with Connectors
Actions are the actual work done by the flow. Each action uses a connector to interact with a service. For example, 'Create item' in SharePoint requires the site address, list name, and field values. Authentication is handled automatically if the connector uses the flow creator's credentials (or a service account for some triggers). You can use dynamic content from previous steps (e.g., email subject as the SharePoint title). Some actions are premium (e.g., 'Send an email with options' for approvals) and require a Power Automate Plan license.
4. Handle Errors and Timeouts
Power Automate automatically retries failed actions up to 4 times by default (configurable up to 90). You can also configure 'Configure run after' settings to define alternative actions on failure, timeout, or skipped. For example, if a SharePoint update fails, send an email notification. Timeout for an action is 120 seconds by default (for HTTP requests). For long-running operations, use asynchronous patterns with a 'Response' action that returns a URL to check status. The flow itself can run up to 30 days (including retries).
5. Test and Monitor the Flow
Use the 'Test' button to run the flow with sample data or a previous run. The designer shows step-by-step execution with input/output for each action. After saving, the flow runs automatically based on its trigger. Monitor runs via the 'Run history' page: each run shows status (Succeeded, Failed, Cancelled), duration, and errors. For failed runs, click to see error details (e.g., 'BadRequest' with HTTP status code). Export run history to CSV or send to Log Analytics for long-term retention. Use alerts to notify admins on failure (e.g., send an email when a flow fails).
Enterprise Scenario 1: Automated Invoice Processing
A large manufacturing company receives hundreds of invoice PDFs via email daily. They built a Power Automate flow triggered by 'When a new email arrives' with a condition checking the subject contains 'Invoice'. The flow then uses AI Builder to extract key fields (invoice number, date, amount) from the PDF attachment. It creates a record in a SharePoint list for tracking and sends an approval request to the finance manager via Teams adaptive card. If approved, it updates the ERP system (a premium connector) and archives the email. If rejected, it sends a rejection email. This flow saves 20 hours of manual data entry per week. Key considerations: AI Builder consumes credits (500 per user per month in some plans), and the flow must handle attachments up to 100 MB. Common misconfiguration: not setting a trigger condition for 'has attachments' — causing errors when emails without PDFs trigger the flow.
Enterprise Scenario 2: Employee Onboarding Automation
An IT department uses a scheduled flow that runs daily to check a SharePoint list of new hires. For each new hire, it creates a user account in Azure AD (via a custom connector), assigns licenses (using Graph API), sends a welcome email with temporary password, creates a Teams channel, and adds the user to relevant distribution groups. The flow uses parallel branches to speed up operations. If any step fails (e.g., license assignment fails due to quota), it sends an alert to the IT helpdesk. This flow reduces onboarding time from 2 days to 30 minutes. Pitfall: exceeding API rate limits for Azure AD (2,000 requests per minute per app) — solved by adding 'Apply to each' with concurrency set to 10 and using a 1-second delay between actions.
Scenario 3: Social Media Monitoring
A marketing team uses an automated flow triggered by 'When a new tweet is posted' (Twitter connector) containing a specific hashtag. The flow checks sentiment using AI Builder, and if positive, it posts the tweet to a Teams channel for sharing. If negative, it sends an email to the social media manager. The flow also logs all tweets to a SharePoint list for analytics. Common issue: Twitter API rate limits (900 requests per 15-minute window per app) — the flow must include a 'Do until' loop with a delay if rate limit is hit. Misconfiguration: not handling deleted tweets (trigger still fires, but tweet may be unavailable) — solved by adding a condition to check if tweet still exists.
MS-900 Objective 2.4: Describe automation capabilities of Microsoft 365
This section specifically tests Power Automate functionality, licensing, and integration with other M365 services. Expect 2-3 questions on this topic. The exam will present scenarios requiring you to identify the correct type of flow, connector, or license needed.
Common Wrong Answers and Traps
Choosing 'Business Process Flow' for a simple notification: Business Process Flows are for guided stages (like a sales pipeline), not for simple event-driven automation. Candidates often pick this because the name sounds 'business-like'. Correct: Use an automated flow for event-driven tasks.
Selecting 'Power Apps' instead of 'Power Automate' for workflow: Power Apps builds custom apps; Power Automate automates workflows. The exam may describe a need to 'send an email when a SharePoint item is updated' — the correct answer is Power Automate, not Power Apps.
Assuming all connectors are free with M365 E5: Only standard connectors (e.g., SharePoint, Outlook, Teams) are included. Premium connectors like Salesforce, SQL Server, or custom connectors require a Power Automate Plan 1 or 2 license. The exam may ask: 'You need to integrate with a third-party CRM. What license is required?' Answer: Power Automate Plan.
Confusing trigger types: A scheduled flow runs at a set time; an instant flow runs when a user clicks a button. A scenario: 'Send a report every Monday at 8 AM' — scheduled flow, not automated.
Specific Numbers and Terms on the Exam
Run history retention: 28 days (default).
Max actions per flow: 250.
Default retry count: 4.
Max flow run duration: 30 days.
Connector categories: Standard vs. Premium (know examples: SharePoint standard, Salesforce premium).
Flow types: Automated, Instant, Scheduled, Business Process Flow.
Approvals: Available in Power Automate (not just Dynamics 365).
Desktop flows: For RPA, requires Power Automate Process license.
Edge Cases and Exceptions
Co-ownership vs. run-only: If a user leaves the organization, flows owned by that user stop working unless shared with a service account. The exam may ask: 'What happens to a flow when the creator's account is disabled?' Answer: The flow fails.
DLP policies: If a DLP policy blocks a connector, the flow cannot be saved or run. The exam may present a scenario where a flow fails due to a policy violation.
AI Builder credits: Not all plans include AI Builder; some require add-on credits.
How to Eliminate Wrong Answers
Read the scenario carefully: Is it event-driven? -> Automated. Is it time-based? -> Scheduled. Is it manually triggered? -> Instant. Is it a guided process with stages? -> Business Process Flow.
Identify if premium connectors are mentioned: If yes, then the answer must include a Power Automate Plan license or per-flow license.
Look for keywords like 'automatically', 'when a new item is created', 'send an email' — these point to Power Automate, not Power Apps or Power BI.
For approval scenarios: Power Automate includes approval actions, not just Dynamics 365.
Power Automate is a cloud-based workflow automation service that uses triggers, conditions, and actions to automate tasks between apps and services.
There are four types of flows: Automated (event-driven), Instant (manual), Scheduled (time-based), and Business Process Flow (guided stages).
Standard connectors (e.g., SharePoint, Outlook, Teams) are included with Microsoft 365; premium connectors (e.g., Salesforce, SQL Server) require a Power Automate Plan license.
Default run history retention is 28 days; maximum flow run duration is 30 days; maximum actions per flow is 250; default retry count is 4.
Approvals are built into Power Automate and can be sent via Teams, email, or mobile app.
AI Builder enables adding AI models (form processing, text classification) to flows, but requires AI Builder credits.
Desktop flows (RPA) require a separate Power Automate Process license.
Data Loss Prevention (DLP) policies can restrict connector usage to prevent data leakage.
Power Automate is part of the Microsoft Power Platform alongside Power Apps and Power BI.
Common exam traps: confusing flow types, assuming all connectors are free, and misidentifying Power Automate vs. Logic Apps.
These come up on the exam all the time. Here's how to tell them apart.
Power Automate
Designed for business users (citizen developers) with a low-code visual designer.
Hosted in Microsoft's multi-tenant cloud (SaaS).
Billing based on flow runs (per month) or per-user license.
Limited to 250 actions per flow.
Integrated with Microsoft Power Platform (Dataverse, AI Builder).
Azure Logic Apps
Designed for professional developers with advanced integration scenarios.
Hosted in Azure as a PaaS service (single-tenant or integration service environment).
Billing based on consumption (action executions) or fixed plan.
Supports up to 500 actions per workflow (with higher limits via premium).
Supports enterprise integration (BizTalk, AS2, EDIFACT, X12) and VNet connectivity.
Mistake
Power Automate is only available with Dynamics 365 licenses.
Correct
Power Automate is included with many Microsoft 365 subscriptions (Business Basic and above), though with limited standard connectors. Premium connectors require a separate Power Automate Plan license.
Mistake
All connectors are free and included with any Microsoft 365 plan.
Correct
Only standard connectors (e.g., SharePoint, Outlook, Teams) are included. Premium connectors (Salesforce, SQL Server, custom connectors) require a Power Automate Plan 1 or 2 license.
Mistake
Power Automate flows can run indefinitely without limits.
Correct
Flows have a maximum run duration of 30 days (including retries), a maximum of 250 actions, and a default retry count of 4. Run history is retained for 28 days by default.
Mistake
Business Process Flows are the same as automated flows.
Correct
Business Process Flows provide a guided experience with stages and steps (like a sales pipeline) and are part of Dynamics 365. Automated flows are event-driven and do not enforce stages.
Mistake
Power Automate Desktop (RPA) is included with all Power Automate licenses.
Correct
Power Automate Desktop requires a separate Power Automate Process license (per-user or per-machine) and is not included with standard Power Automate plans.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Power Automate is a low-code SaaS solution for business users to automate workflows with a visual designer, while Azure Logic Apps is a PaaS service for professional developers requiring advanced integration, enterprise features (like B2B messaging), and more control over hosting and scaling. Power Automate is billed per flow run or per user, whereas Logic Apps is billed per action execution. For the MS-900 exam, remember that Power Automate is for citizen developers and Logic Apps for IT pros.
Yes. Standard connectors (SharePoint, Outlook, Teams) are included with Microsoft 365 subscriptions (Business Basic, Standard, Premium, and E3/E5). Premium connectors (Salesforce, SQL Server, custom connectors) require a Power Automate Plan 1 or 2 license (per user) or a per-flow license. The exam may ask which license is needed for a specific connector scenario.
The flow will stop working because the flow's connections rely on the owner's credentials. To prevent this, flows should be shared with a service account or use a connection reference with a service principal. On the exam, a scenario might describe a flow failing after an employee leaves — the solution is to reassign ownership or use a service account.
Yes, you can use the 'HTTP with Azure AD' connector to call any REST API, or create a custom connector that wraps your API. Custom connectors can be shared within your organization or published to the connector gallery. For the exam, know that custom connectors are premium and require a Power Automate Plan license.
The default retention period is 28 days. This can be changed to 7, 30, or 90 days in the flow settings. For long-term archiving, you can export run history to Azure Log Analytics or export to CSV. The exam may test this default value.
Power Automate has built-in approval actions (e.g., 'Start and wait for an approval') that create an approval request in the Approvals center (accessible via Teams, mobile, web, or email). Approvals can be sequential (one approver after another) or parallel (multiple approvers simultaneously). Each approver can approve, reject, or provide custom responses. The flow waits for a response before proceeding. The exam may ask about the types of approvals available.
An automated flow runs when a specific event occurs (e.g., new email arrives, SharePoint item created). A scheduled flow runs at a specified time or interval (e.g., every Monday at 8 AM, every hour). The trigger is the key difference: automated uses event triggers, scheduled uses a recurrence trigger. The exam will present scenarios requiring you to choose the correct flow type.
You've just covered Power Automate: Workflow Automation — now see how well it sticks with free MS-900 practice questions. Full explanations included, no account needed.
Done with this chapter?