Microsoft Power Automate free access is not one universal permanent plan. The clearly defined no-cost starting route is a 30-day trial that includes premium features. For ongoing use, coverage depends on the licence assigned to the user or process and on the workflow’s connectors and automation type. The main paid option starts at a displayed equivalent of $15 per user per month, paid yearly.
What Microsoft Power Automate Free Access Means
The confirmed free starting point is a 30-day trial. Microsoft describes this trial as including premium features and supporting UI-based cloud flows and standard connectors. It is suitable for evaluating how a trigger, connected actions and workflow data behave before committing to a subscription.
A trial is not the same as a permanent free plan. It provides time-limited evaluation access and does not establish what will remain available afterward. Likewise, having Microsoft 365 should not be treated as automatic proof that every Power Automate workflow is included. Microsoft licensing can vary by assigned entitlement, connector classification and the kind of automation being run.
During an eligible trial, a user can evaluate cloud flows that respond to events, run on schedules or carry out connected actions. For example, a flow could collect values from a supported service, select or transform fields and pass the result to another connected system. Power Automate also supports approvals, templates and run monitoring, although access to a platform-wide capability does not mean every licence includes every implementation of it.
Desktop automation must be considered separately. Power Automate for desktop requires a supported Windows 10 or Windows 11 machine, suitable permissions and reliable interface selectors. Attended and unattended robotic process automation have licensing dependencies, while unattended execution also requires suitable machine capacity and compatible Windows session conditions.
Microsoft Power Automate Pricing and Plan Differences
Microsoft Power Automate pricing uses different licensing units for users, bots and tenants. The United States prices below were verified on September 24, 2026. They are displayed in USD as monthly rates with annual payment required. Actual checkout pricing can vary by country, currency, region and organization.
| Option | Displayed price | Billing and relevant scope |
|---|---|---|
| Power Automate Premium | $15 per user per month | Paid yearly, equivalent to $180 per user per year |
| Power Automate Process | $150 per bot per month | Paid yearly; supports one unattended run per bot at a time |
| Power Automate Hosted Process | $215 per bot per month | Paid yearly; unattended flows run on a Microsoft-managed Azure-hosted virtual machine |
| Process Mining add-on | $5,000 per tenant per month | Paid yearly; requires Power Automate Premium and includes 100 GB of process-mining storage |
Power Automate Premium is licensed per user, so its cost scales with the number of people who need that user-based entitlement. The Process options are licensed per bot instead. Power Automate Process is relevant to unattended execution, but each bot supports only one unattended run at a time. Workloads needing simultaneous unattended runs therefore need capacity planning rather than a simple user count.
Power Automate Hosted Process adds a Microsoft-managed Azure-hosted virtual machine for unattended flows. That can reduce the need to supply the execution machine yourself, although the organization remains responsible for workflow design, credentials, permissions, monitoring and business rules.
The Process Mining add-on serves a more specialized requirement. Its $5,000 monthly tenant rate is paid yearly, requires Power Automate Premium and includes 100 GB of process-mining storage. It is not a necessary upgrade for an ordinary notification or data-transfer flow.
Connector and capability requirements still need to be checked independently of the plan names. Premium connectors, attended and unattended RPA, hosted machines, process mining and additional capacity all have licensing dependencies. AI-assisted authoring and AI-based document or image processing are also platform capabilities, but their presence does not prove that a specific licence supplies every required entitlement or usage allowance.
When Free Access Is Enough
The trial can be enough when the goal is to evaluate a workflow, validate field mappings and determine whether Power Automate fits an existing process. It provides a practical way to build a small cloud flow, examine its run details and identify licensing dependencies before production deployment.
Use the following decision path for longer-term use:
- Simple personal cloud workflow — Check whether the assigned licence covers every connector and action. A workflow is not automatically free merely because it has only a few steps.
- Premium connector or capability — Expect a paid licensing decision when a required connector is classified as premium or the workflow uses a capability outside the assigned entitlement.
- Workflow used by a team — Identify who owns, edits and runs the flow. Compare a per-user licence with the per-bot process options according to the actual execution model rather than the number of people who receive its output.
- Attended desktop automation — Confirm the required RPA entitlement and ensure the user has a supported Windows machine, suitable permissions and a stable desktop environment.
- Unattended automation — Plan for process capacity, available machines and compatible Windows sessions. Choose a hosted process only when a Microsoft-managed Azure virtual machine fits the deployment requirement.
Also consider operational ownership. A flow connected only through one employee’s account can stop when that person changes role, loses access or leaves. Production automations should have deliberate ownership, controlled credentials and a process for handling failed runs.
Example of Checking a Workflow Before Buying
Consider an illustrative workflow that takes each new form response, records selected answers in a spreadsheet and notifies a team channel.
- Define the trigger — A new response arrives through a supported form-service connector.
- Identify the input — The flow receives fields such as a request ID, requester name, category and submission time.
- Map the data — Select the required values and align them with the destination spreadsheet columns. Check required fields and date formats before writing the row.
- Configure the actions — Add the row to the spreadsheet, then send a notification through the team communication connector.
- Check the result — Submit controlled test data, confirm that one correctly mapped row appears, verify that one notification arrives and inspect the run details for failed or skipped steps.
Before deployment, list every connector in the flow and check its classification and licence requirement. Confirm that the connected accounts can read the response, edit the spreadsheet and post to the intended channel. This matters because a simple business outcome can still cross several services, and one premium connector or unsupported entitlement can change the licensing requirement for the complete workflow.
Choose the Licensing Route from the Workflow
Start with the 30-day trial if you need to prove that the automation works. Before the trial ends, document the connectors, flow type, execution identity, desktop or machine requirements and expected ownership model. That inventory will show whether an existing entitlement covers the production flow, a $15-per-user Premium licence is relevant, or the automation needs a per-bot Process option instead.
Explore more technology guides on Techistuff.
Frequently Asked Questions About Microsoft Power Automate free access and pricing
Is Power Automate free with Microsoft 365?
Microsoft 365 ownership alone does not establish that every Power Automate workflow is covered. Entitlements can depend on the assigned licence and the connectors and automation type used. Check the licence assigned to the person or process rather than assuming that access to another Microsoft service covers the entire flow.
Are premium connectors included with free access?
Premium connectors have licensing dependencies and should not be assumed to be part of ongoing no-cost access. The 30-day trial includes premium features, making it useful for evaluation, but a production workflow may require paid licensing after the trial.
Is the 30-day trial the same as a free plan?
No. A trial provides temporary evaluation access, whereas a free plan would provide an ongoing entitlement under its stated limits. The confirmed no-cost offer is a 30-day trial; it should not be treated as proof of permanent free access.
What should I check before upgrading Power Automate?
List every connector, identify whether the workflow is cloud-based or desktop-based, and determine who or what will run it. Also check connection permissions, unattended execution needs, Windows machine requirements, capacity dependencies and whether a Microsoft-hosted virtual machine is required.
