Power Automate vs Azure Logic Apps: When to Move a Flow, and How Pay-as-You-Go Billing Works
A flow that started as one person's automation can end up running a business process: calling APIs all day and stopping when that person's license changes. We recently moved such a flow for a customer, first into its own Power Platform environment with pay-as-you-go enabled, then rebuilt as an Azure Logic App. This article covers the licensing on both sides at the September 2026 price list, how the metered billing works, and which engine a given automation belongs in.
Two engines, two licensing models
Power Automate is licensed through Microsoft 365 or Power Platform subscriptions. From the IT Partner price list, September 2026 (US, commercial):
- Power Automate Premium: $180 per user per year, or $18 per month month-to-month. It licenses the assigned user for cloud flows with premium connectors, custom connectors and attended desktop flows.
- Power Automate per flow plan: $1,200 per flow per year, or $120 per month. It licenses a specific automation rather than every person who benefits from it.
- Power Automate Process: $1,800 per year, and Hosted Process: $2,580 per year. These license a process or bot rather than a user; confirm the current assignment model on Microsoft Learn.
- Add-ons: Power Platform Requests at $600 per year, and the unattended RPA add-on at $1,800 per year.
Azure Logic Apps is an Azure resource with no user license. A Consumption logic app is billed per action and per connector execution, and Logic Apps Standard is billed by the hosting plan it runs on, per Microsoft's pricing documentation at the time of writing. The charges land on your Azure subscription, and like every Azure meter they are the customer's. Azure rates change, so read the current Logic Apps pricing page before you size anything.
What premium connector means for the license
The Power Automate rights seeded into Microsoft 365 plans cover standard connectors: SharePoint, Outlook, Teams, Approvals, OneDrive and the like. Connectors Microsoft classes as premium (HTTP, SQL, Salesforce, ServiceNow, custom connectors and most line-of-business systems, per Microsoft's connector reference at the time of writing) need a license that includes them: Premium for the user, the per flow plan for the flow, a process license, or pay-as-you-go on the environment.
The consequence that catches teams out: a flow with one HTTP action is a premium flow, and every user who owns or triggers it may need coverage. The license also does not grant access to the connected system, so the SQL database, the CRM or the API still needs its own licensing. Verify the seeded rights against your exact Microsoft 365 plan before you assume Premium is unnecessary.
The case: a flow that was never really a user's flow
The flow in question (details generalized) was built by one person on a Premium license. It polled an external API, transformed records and wrote them into a line-of-business system, dozens of times a day. It was an integration service that happened to be licensed to a person.
The symptoms that said it belonged elsewhere:
- Long-running and always on: it ran on a schedule and on triggers from the API, never waiting for a human.
- HTTP and API heavy: almost every action was a premium HTTP call; the Office connectors were incidental.
- Awkward retries and error handling, no run history over months, no alert on failure rates.
- Nothing in source control: changes were made in the browser, with no test copy and no deployment record.
- Ownership by license: if the maker left or the Premium seat moved, the flow stopped.
Step one was to move it into a dedicated environment with pay-as-you-go enabled. Its usage was then metered to the customer's Azure subscription and the maker's license could be reassigned. Step two was to rebuild it as a Logic App: the same connectors, native retry policies, run history and alerting through Azure Monitor, the definition in source control, and pipeline deployment. The flows that stayed in Power Automate were the ones that involved people: approvals in Teams, notifications, a form that feeds a SharePoint list.
How pay-as-you-go billing works on both sides
Power Platform pay-as-you-go links an Azure subscription to a Power Platform environment through a billing policy, and Microsoft meters that environment's usage to the subscription. It is set per environment, not per tenant.
Azure Logic Apps has no license to assign. A Consumption logic app charges per action executed and per connector call. Logic Apps Standard is billed for the hosting plan while it exists, whether or not workflows run, which suits steady high-volume integration and penalizes an idle app.
Three rules for both meters:
- Put a budget and an alert on the subscription before the first run. Our Azure cost optimization post covers budgets, tags and showback.
- Do not assume a reservation or savings plan discounts these meters. How Azure commitments work explains what each covers and why the charge is always yours.
- Give integration workloads a home in the subscription and resource-group structure of an Azure landing zone, with the same policy, logging and RBAC as everything else.
Environment strategy: dedicated environments, restricted makers, pay-as-you-go per environment
Most 20–500-seat tenants have one environment, the default, with every maker in it. The strategy we implement:
- Restrict the default environment. Rename it and limit who can create flows there.
- Create a dedicated integration environment for flows that run as services: system-to-system, scheduled, premium-connector flows with no human in the loop. Own it centrally and enable pay-as-you-go there, so nothing depends on a person's seat.
- Keep user-centric automation on assigned licenses in environments owned by the business teams: approvals, Teams notifications, Office connector flows built by the people who use them.
- Apply data loss prevention policies per environment, so premium connectors are allowed where the integration environment needs them and blocked where a personal flow should not reach them.
- Decide per flow, not per tenant, whether Power Automate or Logic Apps is the target, using the table below.
Power Platform Governance and Center of Excellence Setup ($4,950, three weeks) implements the environment model, DLP and inventory. Power Platform ALM and Pipelines Implementation ($3,950) adds development, test and production environments with pipelines and a Git binding for the flows that stay. Managed Power Platform Governance and Support ($750 per month) runs it afterwards. For the people-centric flows themselves, Business Process Automation Using Built-in Microsoft 365 Tools ($1,500 per project) builds approvals and notifications on standard connectors.
Frequently asked questions
Does an Azure Logic App need a Power Automate license?
No. A Logic App is an Azure resource billed to your Azure subscription per action and connector execution (Consumption) or per hosting plan (Standard), per Microsoft's pricing documentation at the time of writing.
What makes a flow a premium flow?
Any action or trigger from a connector Microsoft classes as premium: HTTP, SQL, Salesforce, ServiceNow, custom connectors and most line-of-business systems. Standard connectors such as SharePoint, Outlook, Teams and Approvals are covered by the rights seeded into eligible Microsoft 365 plans.
Can we move a flow to Logic Apps without rebuilding it?
Plan on a rebuild. The connectors and designer are similar, so the logic transfers quickly, but the resource is different, and the rebuild is the moment to add retry policies, monitoring and source control.
Who pays for pay-as-you-go?
You do. Power Platform pay-as-you-go and Logic Apps both meter to an Azure subscription in your tenant at Microsoft's rates; no partner resells or absorbs the charge.
Do we still need Power Automate Premium for approvals in Teams?
Usually not, if the flow uses only standard connectors and the users hold an eligible Microsoft 365 plan. Add a premium connector and the answer changes to Premium for the users, the per flow plan for the flow, or pay-as-you-go on the environment.
Sources
- IT Partner price list, September 2026 (US, commercial): Power Automate Premium, per user plan, per flow plan, Process, Hosted Process, Power Platform Requests add-on, unattended RPA add-on
- IT Partner engineering notes, September 2026 (the flow migration, anonymized; the Power Platform pay-as-you-go and Logic Apps billing models as stated there)
- IT Partner subscription pages: content/subscriptions/CFQ7TTC0LSGZ__Commercial.json (Premium); CFQ7TTC0LH13__Commercial.json (per flow plan); CFQ7TTC0LH3L__Commercial.json (per user plan); CFQ7TTC0MFT9__Commercial.json (Process)
- IT Partner blog: content/blog/new/azure-cost-optimization-10-ways-to-cut-your-bill.json; what-is-an-azure-landing-zone-and-why-you-need-one.json; azure-reservations-savings-plans-pay-as-you-go-how-commitments-work.json
- IT Partner service pages: content/services/ITPWW890IMPOT, ITPWW1050IMPOT, ITPWW450MSPRC, PRP-ALZ-001 and ITPWW020DEVOT
| Automation pattern | Keep in Power Automate | Move to Azure Logic Apps | Licensing note |
|---|---|---|---|
| Approvals, Teams notifications, Outlook and SharePoint triggers for the people who use them | Yes | No | Seeded Microsoft 365 rights for standard connectors; Premium ($180 per user per year) once a premium connector appears |
| Attended desktop automation that a person drives | Yes | No | Premium; runs without a signed-in user need the unattended RPA add-on ($1,800 per year) or a process license |
| One central flow serving a defined process for many beneficiaries | Yes, on the per flow plan | Consider it if the flow is API-heavy | Per flow plan $1,200 per year; check Microsoft's minimum purchase |
| System-to-system integration, scheduled or event-driven, no human in the loop | Staging only, in a dedicated environment | Yes | Pay-as-you-go environment first, then Logic Apps Consumption metered to your Azure subscription |
| High volume, enterprise connectors, retries and monitoring required | No | Yes; Consumption or Standard by volume | Standard bills the hosting plan whether or not workflows run |
| Anything that must live in source control and deploy through a pipeline | Only with ALM and pipelines in place | Yes | Deploys as infrastructure-as-code in your landing zone |
Key takeaways
- Power Automate is licensed per user ($180 Premium), per flow ($1,200) or per process ($1,800; hosted $2,580); Logic Apps is an Azure resource with no user license, metered per action or per hosting plan.
- A flow that runs as a service (API-heavy, scheduled, retrying, not owned by a person) belongs in a dedicated environment with pay-as-you-go first and, if it keeps growing, in Logic Apps.
- Pay-as-you-go on both sides is metered to an Azure subscription you own; Microsoft's metered charges are always the customer's, so set budgets, tags and alerts before the first run.
- Premium connector is the licensing trigger in Power Automate: one HTTP or SQL action makes a flow premium, and the connected system still needs its own license.
- Environment strategy decides the rest: restrict the default environment, create an integration environment with pay-as-you-go, keep people-centric flows on assigned licenses, and enforce DLP per environment.
If a flow in your tenant has become a service, the Power Platform Governance and Center of Excellence Setup puts the environment model and DLP in place in three weeks for $4,950, and Azure Landing Zone and Cloud Adoption Framework Implementation gives the rebuilt Logic Apps a governed subscription to run in. Power Automate licenses are CSP subscriptions at Microsoft's list price; Power Platform pay-as-you-go and Logic Apps are Azure meters billed to you.
Questions this article didn’t answer?
Thirty minutes with Mike — our CEO, not a sales rep. Bring the hard version of the question.