Power Automate for Small Business: Costs and 5 Flows

Power Automate is Microsoft’s tool for building automated workflows, called flows, between apps. Most Microsoft 365 business licenses include a limited version: cloud flows that use standard connectors such as Outlook, SharePoint, Teams, Forms, Planner, and Approvals, with 6,000 actions per user per day. Premium connectors, custom connectors, and desktop automation need Power Automate Premium, listed at $15 per user per month as of September 2026.

What Is Power Automate?

A flow has a trigger (the event that starts it) and one or more actions (what happens next). “When a form response arrives, ask the manager to approve it, then record the answer in a list” is a typical flow. You build it in a browser at make.powerautomate.com by choosing steps from menus, not by writing code.

Each app a flow talks to is reached through a connector. Microsoft sorts connectors into two classes, and that split decides what you pay:

• Standard connectors include Office 365 Outlook, SharePoint, Microsoft Teams, Microsoft Forms, Planner, Excel Online (Business), OneDrive for Business, and Approvals.
• Premium connectors include SQL Server, Microsoft Dataverse, HTTP requests to arbitrary web services, and many third-party business systems. Each connector’s page in Microsoft’s connector reference shows its class.

Flows come in three kinds: automated (started by an event), scheduled (started by the clock), and instant (started by a person pressing a button). Separately, desktop flows automate clicks and keystrokes in Windows programs, which Microsoft calls robotic process automation, or RPA.

What Is Included with Microsoft 365, and What Costs Extra?

Microsoft’s Power Automate licensing FAQ spells out what the use rights bundled with Microsoft 365 and Office 365 licenses cover.

	Included with Microsoft 365	Power Automate Premium
Automated, scheduled, and instant cloud flows	Yes	Yes
Standard connectors	Yes	Yes
Premium and custom connectors	No	Yes
Desktop flows (RPA), attended	No	Yes
Daily action limit	6,000 per user	40,000 per user
Flows switched off for inactivity	Possible after 90 days without a trigger	Exempt

Limits are per user and do not pool across the company. Microsoft notes that higher transition-period limits currently apply, and advises building to the official numbers.

Current List Prices

From Microsoft’s Power Automate pricing page, as of September 2026, paid yearly:

• Power Automate Premium: $15.00 per user per month. Cloud flows with premium connectors, attended desktop flows, and process mining for one person.
• Power Automate Process: $150.00 per bot per month. Licenses a single flow or an unattended desktop automation instead of a person.
• Power Automate Hosted Process: $215.00 per bot per month. The same, running on a virtual machine Microsoft hosts.

The five flows described below need only the included rights. Premium becomes relevant when a flow has to reach a system outside Microsoft 365 through a premium connector.

Who Needs the Premium License?

The same FAQ explains the rule. Automated and scheduled flows run under the flow owner’s license, so if one uses a premium connector, only the owner needs Premium. Instant flows run under the license of whoever presses the button, so every person who runs an instant flow with a premium connector needs Premium.

Two Limits That Catch People Out

Microsoft’s limits page lists two that matter for small offices:

• A flow that is not triggered for 90 days may be turned off, unless its owner has a premium license. Owners are notified 30 days ahead. A once-a-year flow built on included rights needs someone to watch for that email.
• A flow run can last at most 30 days. An approval nobody answers for a month times out.

A flow whose trigger or actions fail continuously is also turned off after 14 days.

Five Practical Flows for a Small Office

All five use only standard connectors, so they work with the rights included in Microsoft 365. Trigger and action names are as they appear in the Power Automate designer.

1. Time-Off or Purchase Request with Approval

1. Build the request form in Microsoft Forms.
2. Create a SharePoint list to act as the log, with columns that match the form.
3. Trigger: When a new response is submitted (Microsoft Forms). Pick your form.
4. Action: Get response details (Microsoft Forms), which pulls in the answers.
5. Action: Start and wait for an approval (Approvals). Choose an approve or reject approval type where the first response decides, assign it to the manager, and put the form answers in the details. The manager can respond from email or the Approvals app in Teams.
6. Add a Condition that checks whether the outcome equals Approve.
7. In both branches: Create item (SharePoint) to record the request and decision, then Send an email (V2) (Office 365 Outlook) to tell the requester.

Plan for the 30 day run limit by telling managers that unanswered requests expire.

2. Shared Mailbox Alert and Task

For an info@ or billing@ mailbox that several people watch.

1. Trigger: When a new email arrives in a shared mailbox (V2) (Office 365 Outlook). Enter the shared mailbox address. Optionally filter by subject or sender.
2. Action: Post message in a chat or channel (Microsoft Teams) with the sender, subject, and a link.
3. Action: Create a task (Planner) in the plan your staff use, due in one business day.

The flow owner needs access to the shared mailbox.

3. Save Emailed Attachments to SharePoint

Useful for supplier invoices that arrive by email.

1. Trigger: When a new email arrives (V3) (Office 365 Outlook). Set the trigger options so it fires only for mail with attachments and includes the attachment content, and filter on a folder or sender so the flow does not process all mail.
2. Add an Apply to each loop over the Attachments.
3. Inside the loop: Create file (SharePoint). Choose the library and folder, use the attachment name as the file name (prefixing the received date avoids duplicates), and the attachment content as the file content.
4. Optional: Post message in a chat or channel to tell the bookkeeper.

Email signatures often contain small images that arrive as attachments. Add a condition on the file name ending in .pdf to skip them.

4. Tell the Channel When a File Lands in a Folder

1. Trigger: When a file is created (properties only) (SharePoint). Choose the site, library, and folder, for example “Signed Contracts”.
2. Action: Post message in a chat or channel (Microsoft Teams) with the file name, who added it, and the link.

This is a good first flow: two steps, visible results, and nothing breaks if it fails. Our SharePoint guide covers setting up libraries that suit this.

5. Weekly Reminder of Upcoming Renewal Dates

For licenses, insurance policies, domain names, equipment leases, or certifications that expire.

1. Create a SharePoint list with columns for Title, Expiry Date, and Owner.
2. Trigger: Recurrence (Schedule), weekly on Monday morning.
3. Action: Get items (SharePoint) with a filter query that returns items whose Expiry Date falls within the next 30 days.
4. Add an Apply to each loop over the results: Send an email (V2) to the item’s Owner with the name and date.

Because this one is triggered by the schedule every week, it never goes 90 days without a trigger.

Governance: Keeping Flows from Becoming a Problem

Any licensed user can build flows, and flows move data. A little structure prevents most trouble.

Decide who owns business-critical flows. A flow runs on its owner’s connections. If that person leaves and the account is disabled, the flow stops. For anything the business depends on, add a second owner (see Microsoft’s guide to sharing a cloud flow) and add “reassign flows” to your offboarding checklist.

Set a data policy. In the Power Platform admin center, administrators can create data policies that group connectors into business, non-business, and blocked. Connectors in different groups cannot be used in the same flow. A simple policy that keeps Microsoft 365 connectors in the business group and consumer services out of it stops a flow from copying company files to a personal storage account. This is the automation side of shadow IT.

Know what the default environment is. Every tenant gets one default environment where everyone is a maker. Microsoft describes it as unsuitable for production workloads. A small office will usually still build there, which is another reason to keep the next item.

Keep an inventory. A short list of each flow, what it does, who owns it, and what it connects to. Review it twice a year and delete what is no longer used.

Watch failures. Flow owners get failure emails. Make sure those go to someone who reads them, and check run history after changing a form, list column, or folder name, because renames break flows.

Mind what flows carry. A flow that emails form responses containing health or financial details is moving sensitive data. If your office works under HIPAA or similar rules, include flows in that review.

When Power Automate Is the Wrong Tool

• The task happens a few times a month. Building and maintaining a flow can take longer than doing the task.
• The process is not settled. Automating a process people still argue about locks in the argument. Agree on the steps first.
• The software you use already does it. Accounting, practice management, and CRM systems often have built-in approvals and reminders that are better supported than a custom flow.
• It needs judgment. Flows are for steps with clear rules.
• It needs a premium connector for many people. Price it before you build. An instant flow with a premium connector used by ten people is ten Premium licenses, or one Process license.

Common Mistakes

• Building an important flow under one person’s account with no second owner.
• Leaving a trigger unfiltered so the flow runs on every email or file, which burns through the daily action limit.
• Renaming a list column or form question without checking the flows that use it.
• Forgetting the 90 day inactivity rule for seasonal flows.
• Adding a premium connector to a flow that many people run, without budgeting for the licenses.

Common Questions

Is Power Automate free with Microsoft 365?

A limited version is included at no extra charge with most Microsoft 365 business licenses. It covers automated, scheduled, and instant cloud flows using standard connectors, up to 6,000 actions per user per day. Premium connectors, custom connectors, and desktop automation are not included. Those require Power Automate Premium at $15 per user per month as of September 2026.

What is a premium connector?

It is a connector Microsoft has classed as Premium, which means a flow using it needs a paid Power Automate license. Examples are SQL Server, Dataverse, and the HTTP connector for calling arbitrary web services. Standard connectors cover the main Microsoft 365 apps. Each connector’s documentation page on Microsoft Learn shows its class.

Do we need a developer to build flows?

Not for flows like the five above. They are assembled from menus and templates, with no code. Help is worth having for flows that loop over large amounts of data, need error handling, touch sensitive information, or will be relied on daily.

What happens to flows when the person who built them leaves?

Flows keep running until the owner’s account or connections stop working, then they fail. Before disabling a departing employee’s account, add another owner to each of their flows and have that owner re-create the connections. An administrator can see all flows in the Power Platform admin center.

How We Can Help

Coastal Growth Co. can look at the repetitive tasks in your office, tell you which are worth automating and which licenses they need, build and document the flows, and set up a basic data policy and ownership plan. Scope and price are agreed before any paid work. See our cloud, email, and Microsoft 365 services, read how flows fit with Microsoft Teams, or get in touch.