The Free Tier’s Three Hard Ceilings
Teams ask: can the free tier handle real workloads? The answer depends entirely on what you connect. If your stack is pure Microsoft 365—Outlook, SharePoint, Teams, OneDrive, Excel, Forms, Planner—then yes, the free tier works. But the moment you touch Salesforce, Zendesk, or any non-Microsoft app, you hit one of three hard ceilings before you finish building your first flow.
The free tier (included with eligible Microsoft 365 licenses) covers cloud flows that use standard connectors only. That means no premium connectors, no custom connectors, no on-premises gateways, no desktop RPA, and no AI Builder. Microsoft enforces a daily action limit of 6,000 actions per day—and a monthly run limit that the company does not publish. A third-party estimate from Superblocks puts it at roughly 750 runs per month. I would treat that as a directional starting point, not a guarantee—you can verify your actual limits in the Power Platform admin center under “API usage.”
Ceiling #1: Premium Connectors
Every non-Microsoft connector—Salesforce, Zendesk, HubSpot—is classified as “premium.” To use it, each user who triggers a flow that uses that connector must have a Power Automate Premium license at $15 per user per month (billed annually). That looks cheap until you multiply. A five-person team costs $75/month. Compare that to Zapier’s Team plan at $69/month for up to 25 users. The crossover is stark: for a mixed-ecosystem team, Zapier’s task-based model is often cheaper because you pay by volume, not by headcount. Make’s pricing is even more granular: $9/month for 10,000 operations. The per-user model inflates cost the moment you add users who only occasionally trigger flows. If only two people on a ten-person team use premium connectors, you still need ten licenses if everyone else might need to access the same flows (because permission management often requires licensing all editors). That hidden math catches teams off guard.
Microsoft lists about 1,400 prebuilt connectors; Zapier claims 9,000+. The difference isn’t just quantity—it’s depth. Zapier’s lead is in niche and long-tail apps, while Power Automate’s connectors are deeper for Microsoft 365. If your workflow lives mostly inside Microsoft, you won’t need premium connectors. If it touches anything else, you’re paying per user.
Ceiling #2: Desktop RPA
Power Automate offers two kinds of robotic process automation: attended (human-triggered) and unattended (scheduled). Attended RPA is included in the Premium plan, but only as one bot per user. Unattended RPA requires the Process plan at $150 per bot per month. That “bot” means one concurrent run. If you need two unattended automations running simultaneously, you pay for two bots. This is competitive with dedicated RPA tools like UiPath, but it’s a real cost for any team that wants to automate legacy desktop apps without a human in the loop. For workflows that don’t require desktop interaction—cloud-to-cloud automation—you’re better off looking at task-based tools like Zapier or Make, which avoid RPA pricing entirely. The Zapier vs Make comparison dives deeper into the tradeoffs.
Ceiling #3: API Request Limits
Microsoft does not publish a simple “runs per month” figure for the free tier. The most common third-party estimate is ~750 runs per month, but this comes from a blog post, not Microsoft. The company does document a daily action limit of 6,000 actions per day for users with Microsoft 365 licenses. That may sound generous until you realise that a single flow with loops can burn through hundreds of actions per run. High-volume automation—polling a database every five minutes—can hit the daily cap in hours. Even paid plans have per-user API quotas; upgrading to Premium doesn’t remove the limits, it only raises them. My advice: check your actual usage in the admin center before committing to the free tier for anything beyond a few low-frequency flows.
Microsoft offers a 30-day free trial of the Premium plan that unlocks everything. No credit card required, but it resets per user. Use it to verify that premium connectors work with your exact Salesforce or Zendesk setup—don’t treat it as a permanent extension of the free tier.
Cost Comparison: Power Automate vs Zapier vs Make
The table below shows monthly costs for typical team profiles. Zapier’s Team plan includes premium apps and task pooling across all users. Make’s pricing is per-operation and does not limit the number of users. Power Automate’s per-user cost includes all cloud-flow capabilities but no unattended RPA.
| Scenario | Power Automate | Zapier | Make |
|---|---|---|---|
| Microsoft-only, low volume | Free (with M365) | $19.99/mo Professional (overkill) | $9/mo for 10K ops (overkill) |
| Mixed ecosystem, 5 users | $75/mo (Premium) | $19.99/mo Professional (1 user) or $69/mo Team (up to 25) | $9/mo for 10K ops (scales by volume) |
| Mixed ecosystem, 20 users | $300/mo (Premium) | $69/mo Team (up to 25 users) | $9/mo base, scales per operation |
Note: Microsoft’s published ROI figures—248% over three years, 200 hours saved per employee—come from a vendor-commissioned Forrester study. They are directional, not independent benchmarks. User reports on Reddit and in forums tell a different story: the hidden costs (premium licensing, API limits, per-user math) are the real story.
Process Mining and Hosted Process – Niche Add-Ons
Two higher tiers appear on the pricing page: Hosted Process ($215/bot/month) and Process Mining ($5,000/tenant/month). Hosted Process adds a Microsoft-managed virtual machine for your RPA bots—useful if you don’t want to run your own infrastructure. Process Mining is the outlier: $5,000 per tenant per month for process discovery and analysis. For most SMBs and small teams, this is a distraction. Ignore it.
When to Stay, When to Switch
After walking through the numbers, here’s the short version of what I tell teams:
- Stay on the free tier if your automations use only Microsoft 365 apps and your volume is low (a few runs per day). Check your admin center to confirm you’re within the ~750 runs/month ballpark.
- Consider Premium ($15/user/mo) if you need premium connectors but your team is small (under 5 people) and everyone actively builds flows. For larger teams, task-based pricing from Zapier or Make is almost certainly cheaper.
- Look at the Process plan ($150/bot/mo) only if you have a specific unattended desktop automation need that cannot be solved with cloud-only tools. Otherwise, you don’t need RPA.
- If your stack is mixed (Microsoft + non-Microsoft) and you don’t need desktop automation, compare Power Automate Premium’s per-user cost against Zapier (task-based) and Make (operation-based). The spreadsheet rarely favors Power Automate for mixed teams.
The free tier is not a trap—it’s a genuinely useful entry point for Microsoft-centric teams. But the moment your automation needs stretch outside that walled garden, the pricing model tilts in favor of task-based alternatives. Do the per-user math before you commit to a license.