How to Use Power Automate: A Beginner’s Guide for 2026

How to Use Power Automate: A Beginner’s Guide for 2026

Power Automate is Microsoft’s no-code automation platform. To use it, sign in to make.powerautomate.com with your Microsoft 365 account, pick a trigger (the event that decides when the flow runs), add one or more actions (what the flow actually does), then test and save. Most teams in Singapore start with a small cloud flow that connects Outlook, Teams or SharePoint, and quietly saves two or three hours a week.

That much you can read in any tutorial. What most of them skip is the part that costs beginners the most time. Power Automate is really three products sharing one name. The licensing has a quiet trap that turns a “free” flow into a $15-per-user flow the moment you pick the wrong connector. And the expression syntax breaks the first time your trigger returns data in a format you didn’t expect. After 24 years of training in Singapore, I see the same four or five things trip people up. This guide covers all of them, in the order you actually need them. If you want a structured, hands-on path through both Power Automate and its sibling Power Apps, our Power Apps and Power Automate Masterclass walks through it as a WSQ-funded 2-day course.

1. What Power Automate Is (and the Cloud vs Desktop Split Nobody Warns You About)

Power Automate is a workflow automation service from Microsoft. It used to be called Microsoft Flow. It connects apps and services so an event in one place (a new email, a row added to a sheet, a button pressed on a phone) can set off actions in another place automatically.

Here is the part that confuses every beginner. There is no single product called “Power Automate”. There are three:

• Cloud flows — run in the Microsoft cloud, connect to web-based services through connectors, and start either automatically (when an event fires), instantly (when you press a button) or on a schedule. This is what most people mean when they say “Power Automate”.
• Power Automate Desktop — runs on your Windows PC and automates things on the desktop itself. Legacy applications, websites without an API, screen-scraping, mouse-and-keyboard tasks. This is robotic process automation, or RPA.
• Business process flows — guided forms inside Dynamics 365 and model-driven Power Apps that walk a user through a multi-stage process. Most beginners will never touch these.

A helpful way to think about it: cloud flows are like courier services between web apps. Desktop flows are like a trained assistant sitting at your laptop, clicking the same buttons you would. Business process flows are like a checklist taped to the side of your screen. Three different jobs, three different tools.

A common waste of time is trying to do an RPA task with a cloud flow, or trying to do a cloud-to-cloud integration with Power Automate Desktop. Decide which of the three you need before you start clicking anything. It will save you an afternoon.

2. Power Automate Licensing: What’s Free, What Needs Premium, How to Check Yours

Power Automate has a free tier bundled with most Microsoft 365 plans. The free tier covers cloud flows that use standard connectors only. Outlook, OneDrive, SharePoint, Teams, Excel for the Web, Planner, Forms — the usual Microsoft stack.

You move out of the free tier the moment you touch a premium connector. SQL Server, Salesforce, ServiceNow, HTTP, custom connectors and the SFTP connector are all premium. The same goes for Power Automate Desktop run unattended, AI Builder and process mining.

Current Microsoft pricing (always check Microsoft’s official pricing page before buying — these numbers shift):

To check what you actually have: sign in to make.powerautomate.com, click the gear icon at the top right, then View My Licenses. The page tells you which licences are assigned to your account, when they expire, and which connectors they unlock. Do this before you start building a big flow with a premium connector. Otherwise you’ll spend a Friday afternoon designing something your account can’t run.

3. How to Set Up Your First Flow: 7 Steps from Blank to Running

The fastest way to understand Power Automate is to build a tiny working flow. The example below saves attachments from a specific sender into a OneDrive folder. Useful for invoices, weekly reports, or anything you currently drag-and-drop manually.

1. Sign in to make.powerautomate.com with your work or school Microsoft 365 account.
2. Confirm the environment in the top-right corner. If your organisation has more than one (production, sandbox, dev), pick the one you’re allowed to build in. A flow created in the wrong environment cannot be easily moved later. This trips up more people than you’d think.
3. Click Create in the left navigation, then Automated cloud flow.
4. Name the flow (“Save invoice attachments to OneDrive”) and search for the trigger When a new email arrives (V3) under Office 365 Outlook. Click Create.
5. Configure the trigger. Under Show advanced options, set From = the sender you want to filter (for example accounts@yourvendor.com), Has Attachment = Yes, Include Attachments = Yes.
6. Add an action. Click + New step, search for OneDrive for Business, choose Create file. Set Folder Path = /Invoices/2026, File Name = Attachments Name, File Content = Attachments Content. Both fields come from the dynamic content panel on the right.
7. Click Save. Run Flow checker at the top right to catch errors. Then click Test → Manually, send yourself a test email matching the filter, and watch the run history. Green tick means it worked. Do try it.

A successful run shows up under My flows → Cloud flows with a 28-day run history at the bottom. Anything that fails shows a red cross and a clickable error message telling you exactly which step broke and why. That error panel is the most useful thing in the whole product.

4. Cloud Flows: Triggers, Actions, and the 900+ Connectors That Do the Work

A cloud flow is built from three building blocks. A trigger, one or more actions, and the connectors that supply them.

• Triggers start the flow. Three sub-types: automated (an event fires somewhere — a new email, a new row, a new file), instant (you press a button in the mobile app, in Teams, or on the web), and scheduled (every weekday at 8am, every first of the month, every 15 minutes).
• Actions are what the flow does once it starts. Send an email. Create a file. Post in Teams. Update a row. Call an HTTP endpoint. Refresh a Power BI dataset.
• Connectors are the bridges to apps. Power Automate ships with more than 900 of them, split into standard (included with most M365 plans) and premium (paid Power Automate licence required). Each connector exposes its own set of triggers and actions.

Real flows usually have more than one action. A typical onboarding flow looks like this: trigger (new row in a SharePoint list called “New Joiners”) → action 1 (create a Planner task for IT to provision the laptop) → action 2 (post a welcome message in the team’s Teams channel) → action 3 (send the new joiner a welcome email with the onboarding handbook attached). Each step uses dynamic content from the step before — the new joiner’s name from the SharePoint row becomes part of the email subject, and so on.

A flow is a bit like a recipe. The trigger is the bell that says “start cooking”. Connectors are the ingredients. Actions are the steps. Get the order wrong and you still get food, just not the food you wanted.

5. Power Automate Desktop: When Cloud Flows Aren’t Enough

Cloud flows are powerful. They only work when there’s a connector. If your job involves a Windows-only legacy app with no API, a website that doesn’t expose its data, or a process that ends with someone copying numbers out of a PDF, you need Power Automate Desktop instead.

Power Automate Desktop is a free download for Windows 10 and Windows 11. It records the things you do on screen — clicking buttons, typing in fields, copying data, switching windows — and replays them on a schedule or on demand. Under the hood it uses UI automation, image recognition and OCR, so it can work even when the application has no programmable interface.

If you’re new to it, see our deeper walkthrough on installing Power Automate Desktop on Windows. Once you have a desktop flow running, the next pain point is sharing a Power Automate Desktop flow with the rest of your team without breaking permissions. We see this in every batch of clients — the build is the easy half, the sharing is the half that bites.

A common pattern in Singapore companies that still run a mix of old and new systems: a desktop flow pulls data out of a legacy app, drops it into Excel or a SharePoint list, and a cloud flow then takes over for the integration with everything else. That hybrid pattern handles most real-world automation in mixed-system environments. Banks, manufacturers, and government-linked organisations all use it.

6. The First Five Flows Worth Building

If you’re starting out, build small. The goal of your first month with Power Automate is to save yourself two or three hours a week, not to build an enterprise automation platform. These five give the best return for the time invested:

1. Save Outlook attachments to OneDrive or SharePoint. Filter by sender (your vendor, your bank, your client) and drop the attachments into a dated folder. Removes the daily drag-and-drop.
2. Get a Teams notification when an email arrives from your boss or a key client. A cloud flow that watches your inbox and posts a Teams message when the sender matches. Stops you missing the one email that mattered in 400. Your boss will be quietly pleased.
3. Daily Power BI dataset refresh + summary email. Schedule a flow at 7am. Refresh the dataset, wait for completion, then send an email with Power Automate using the key numbers from the report pinned in the body. A useful daily flash report. (This is also what people usually mean when they ask “how to automate a Power BI report”.)
4. Approval flow with a manager fallback. When someone submits a leave form (Microsoft Forms → SharePoint list), send an approval to their manager. If no response in 48 hours, escalate to the manager’s manager. Approvals is a first-class action type in Power Automate.
5. Scheduled file moves between SharePoint libraries. Useful for archiving. Every Friday at 6pm, move any file older than 90 days from the “Active” library to “Archive”.

Each of these is achievable in a single afternoon and pays back the time spent within two or three weeks of use. Start with one. Get it working. Then add the next.

7. Expressions and Functions: Where Most Beginners Break Their Flow

Dynamic content (the blue tiles you click to insert “Subject” or “Sender” into a field) handles the easy 80% of flows. The remaining 20% is where expressions come in. Expressions are small functions you type into the Expression tab of the dynamic content picker.

The handful of expression functions you actually need at the start:

• take(string, n) — first n characters of a string. Useful for trimming a long email subject into a short Teams notification preview. Example: take(triggerOutputs()?['body/subject'], 80).
• first(array) — the first item in an array. Often used after a “Get items” action that returns a list when you only want one row.
• if(condition, valueIfTrue, valueIfFalse) — inline branching without a Condition control. Example: if(equals(triggerBody()?['Status'], 'Approved'), 'Yes', 'No').
• formatDateTime(value, format) — convert the messy ISO timestamp you get from Outlook (“2026-05-20T08:14:33.0000000Z”) into something readable. Example: formatDateTime(utcNow(), 'dd MMM yyyy') returns “20 May 2026”.
• length(value) — counts characters in a string or items in an array. Useful in conditions (“only run if there’s at least one attachment”).

The single most common beginner mistake is mixing single and double quotes inside an expression. Power Automate’s expression editor demands single quotes around string literals. 'Approved', not "Approved". If a flow fails with the error InvalidTemplate. Unable to process template language expressions, look for a misplaced quote first. Nine times out of ten that’s it.

When an expression fails, open the failed run, click the broken action, and look at the INPUTS panel. Power Automate shows you exactly what the expression resolved to before it errored. That panel is your fastest debugging path. Read it like a forensic report — it tells you the value, the type, and where Power Automate stopped understanding.

8. Sharing Flows with Teammates Without Breaking Permissions

A flow that only one person can edit is a bus-factor problem waiting to happen. To share, open the flow, click Share in the top bar, then add a colleague as either an Owner (can edit and run) or Run-only user (can press the button on an instant flow but cannot see the design).

A few things that catch people out:

• The connections, not just the flow, are shared. If your flow uses your personal Outlook connection, the co-owner will need to swap that for their own connection or a shared service account before they can fully maintain it.
• Desktop flows are shared differently. They live inside a Power Platform environment and are shared through the Solutions area, with their own permission model. The full walkthrough is in our guide on sharing desktop flows.
• When the original owner leaves the company. If a flow has only one owner and that account is disabled, the flow gets orphaned. Quietly. Often nobody notices until the daily report stops arriving. Always add a second owner — ideally a shared service account or a team admin — before someone changes jobs.

For team-built automations, the safer pattern is to put flows inside a Power Platform Solution with a shared service account as the owner. Solutions also make it possible to move flows between environments cleanly — from dev to test to production — without rebuilding by hand. Managers can be quite demanding about audit trails. Solutions help.

9. Where to Learn More: Microsoft Learn vs Hands-On Courses

There are three honest paths from “I built a small flow” to “I can build automations my team relies on”:

• Microsoft Learn — free, well-structured modules and learning paths, with an official certification path at the end. Best if you’re self-paced and disciplined. The “Get started with Power Automate” learning path is a sensible starting point.
• Community forums and the Power Automate Community blog — gold for specific error messages. When a flow throws a weird HTTP 502 from a SharePoint connector at 11pm on a Tuesday, this is where the answers live.
• Structured hands-on training — a 2-day in-person course with a trainer pays off if you’re being asked to build flows for your team and you don’t want to spend three months learning the gotchas one painful flow at a time.

If you fit the third category and you’re based in Singapore, our Power Apps and Power Automate Masterclass is a hands-on, WSQ-funded course that walks you through both products together, with live business examples and SkillsFuture-eligible pricing. Once you have the basics, the natural next step is the create agentic AI automations without coding course — where Power Automate becomes the runner for AI-driven workflows — or the broader digital transformation with AI tools programme if you’re driving change at organisation level.

I hope you’ll find this useful. Do try the small starter flow in section 3 first; once it runs successfully, the rest of Power Automate stops feeling intimidating. Give it a try — the worst that happens is a red cross and a clear error message telling you exactly what to fix.

{{COURSE_CTA}}

{{AUTHOR_BIO}}

Frequently Asked Questions

Is Power Automate free?

There is a free tier included with most Microsoft 365 plans. It covers cloud flows that use standard connectors only — Outlook, OneDrive, SharePoint, Teams, Forms, Planner and the rest of the Microsoft stack. The moment a flow needs a premium connector (SQL Server, Salesforce, ServiceNow, HTTP, custom connectors) or unattended RPA, you need a paid plan. Most teams start free and upgrade only when a specific flow demands a premium connector. That’s a sensible way in.

What is the difference between Power Automate and Power Automate Desktop?

Power Automate (cloud) runs in the Microsoft cloud and connects to web-based services through 900+ connectors. Power Automate Desktop runs on your Windows PC and automates things happening on the desktop itself — legacy applications, websites without APIs, mouse-and-keyboard tasks. This is robotic process automation, or RPA. A common pattern is to use both together: a desktop flow pulls data from a legacy app, and a cloud flow then takes over for everything web-based. Many real-world automations are this hybrid.

Do I need a license for Power Automate?

You need a Microsoft 365 account to access Power Automate at all. Most M365 plans include a “seeded” Power Automate licence that covers cloud flows with standard connectors. For premium connectors, attended RPA, unattended RPA or AI Builder, you need a paid Power Automate licence: Per User ($15/month), Per Flow ($500/month for 5 flows), Attended RPA ($40/user/month) or Unattended RPA ($150/bot/month). To check what you have, click the gear icon at make.powerautomate.com and choose View My Licenses.

Can Power Automate replace Zapier?

For Microsoft-heavy environments, yes. Power Automate is more powerful than Zapier and is often already paid for through your M365 subscription. It has more connectors, deeper Microsoft 365 integration, RPA built in, and AI Builder. Where Zapier still wins is breadth of niche SaaS connectors, simpler pricing, and a gentler learning curve. If your stack is 80% Microsoft, choose Power Automate. If your stack is a wide spread of consumer and indie SaaS tools and you want minimum complexity, Zapier may still be a better fit. Use the tool that matches your stack, not the one with the better marketing.

How long does it take to learn Power Automate?

You can build a useful first cloud flow in your first hour. A working grasp of triggers, actions, connectors, conditions and basic expressions takes 8–12 hours of hands-on practice spread over a couple of weeks. Confidence with the trickier parts — expressions, error handling, sharing, solutions, environments — takes another 20–30 hours of building real flows. A focused 2-day classroom course compresses those 30–40 hours considerably because a trainer points out the gotchas before you trip over them. Practice beats theory every time. Read less, build more.

How do I change Power Automate’s display language?

Power Automate uses your Microsoft 365 language setting by default. To change it independently: sign in to make.powerautomate.com, click the gear icon at the top right, then View all Power Automate Settings. Under Languages, choose your preferred display language and time zone, then click OK. Refresh the browser and the new language kicks in. Note: this changes the UI labels only. Flow names, action names you typed, and dynamic content from your data stay in whatever language they were created in.

{{RELATED_POSTS}}