Power Automate Desktop Licensing

This is a comprehensive guide to licensing Microsoft Power Automate for Desktop. The licensing model for this product has undergone significant changes, particularly with the shift towards "Attended RPA" inclusion in standard Microsoft 365 licenses. Below is a detailed breakdown of the current licensing architecture, the difference between Attended and Unattended scenarios, the 2023 licensing updates, and practical cost calculations.

The Comprehensive Guide to Power Automate Desktop Licensing Microsoft Power Automate Desktop (PAD) is a robust tool for automating desktop and web-based processes. However, its licensing structure is distinct from other Microsoft services because it bridges the gap between standard office productivity and advanced Robotic Process Automation (RPA). Understanding the licensing requires distinguishing between who triggers the automation and where the automation runs. 1. The Core Distinction: Attended vs. Unattended The entire licensing model for Power Automate Desktop hinges on two primary modes of operation. Before analyzing costs or subscriptions, you must define the use case. Attended RPA

Definition: The automation runs on a user’s machine, and it is typically triggered by the user (though it can be triggered by events, cloud flows, or schedules). The user is present and interacting with the machine. Analogy: A personal assistant sitting next to you. You tell them to do a task, and they do it on your computer while you watch or do other things. Licensing Mechanism: This is tied to the User . If a user has the right license, they can run desktop flows on their own machine.

Unattended RPA

Definition: The automation runs on a dedicated virtual machine (VM) or a server, usually in a headless environment (without a monitor). It is triggered by an event, a schedule, or an API call, often without any human intervention. Analogy: A factory robot. It works in the background 24/7, processing high volumes of work independently of any specific user. Licensing Mechanism: This is tied to the Machine (the environment). You purchase "Process Mining & Unattended RPA" licenses to register a machine as an automation host.

2. The Microsoft 365 Inclusion (The 2023 Update) Historically, running desktop automation required a premium "Power Automate Per User" license (approx. $15/user/month). However, in late 2023, Microsoft made a landmark change to democratize RPA. The Rule: Most standard Microsoft 365 business and enterprise licenses now include the rights to run Attended RPA via Power Automate Desktop. If a user holds one of the following licenses, they are already licensed to use Power Automate Desktop in an attended capacity on their own device:

Microsoft 365 E3 Microsoft 365 E5 Microsoft 365 F3 (Frontline Worker) Microsoft 365 Business Premium Microsoft 365 Business Standard power automate desktop licensing

The "Use Rights" Limit While the license is included, it comes with a "Power Platform Request" limit (formerly called "Power Automate Runs").

E3 / Business Standard: Typically includes 2,000 – 5,000 Power Platform requests per user per day. E5: Typically includes higher limits (often 10,000+ or unlimited depending on the specific SKU).

What this means: If an employee wants to create a macro to scrape a website once a day and save it to Excel, they can do this with their standard E3 license at no extra cost. This effectively turned Power Automate Desktop into a free tool for most enterprise knowledge workers for day-to-day productivity tasks. This is a comprehensive guide to licensing Microsoft

3. Premium Licensing: When the Standard Inclusion Isn't Enough If you do not have a qualifying Microsoft 365 license (e.g., you have E1, E3 basics, or Office 365 E3), or if you need to exceed the standard usage limits, you must purchase Premium licenses. Power Automate Per User Plan

Cost: Approximately $15.00 USD per user/month. Scope: This is an "Attended" license. It allows a user to run unlimited desktop flows (no daily cap on runs) and access premium connectors (SQL, SAP, Custom APIs). Use Case: Power users or developers who are building and testing complex desktop flows constantly and are hitting the daily run caps of their standard M365 licenses.