Setting Up Unattended RPA in Power Automate
Set up unattended RPA: register the machine, assign process capacity, and switch the cloud flow to unattended mode, no gateway required.
Attended, unattended, and hosted RPA compared: which Power Automate license is needed for which desktop flow use case.
As soon as a desktop flow in Power Automate needs to do more than run once at the push of a button, the licensing question inevitably comes up. Power Automate distinguishes three fundamentally different operating modes for desktop flows: attended, unattended, and hosted RPA, and each of them depends on its own license with its own logic. Anyone who doesn't clarify this in advance either buys too much or only discovers in production that the flow can't start automatically at all without an additional capacity license.
This article compares the three licensing models, explains what each of them is intended for, and shows what you should pay attention to when choosing. It is based on the current information from the official Microsoft documentation on Power Automate.
Attended RPA means that a desktop flow runs under human supervision: a person starts the flow on their own, already-in-use computer, and the bot performs the actions while the person watches or keeps working in parallel, for example in picture-in-picture mode. According to the Overview of Power Automate license types the Power Automate Premium user license is intended for this: a classic user license assigned to exactly one person. It comes with a supervised bot and covers almost everything needed for daily use:
It's important to understand the difference from the free Power Automate license: the free version also allows local, attended desktop flows, but without sharing with others and without access to premium features. So for every RPA developer who builds and maintains desktop flows in the portal, you need at least a Premium license, regardless of whether unattended or hosted RPA is used later on.
Unattended RPA lets a desktop flow run without human supervision. The bot signs in to the target machine on its own, performs the actions, and then signs out again, typically at night, at fixed times, or triggered by a cloud flow. The Premium license alone is not enough for this. An additional Power Automate Process license is required, which according to the documentation is a capacity license and is assigned not to a person but to a machine or a cloud flow.
A few points that often cause confusion in practice:
Historically, there was a separate unattended RPA add-on alongside the per-flow license for this. Both models were simplified in favor of the Process license, which since August 2023 covers both unattended RPA and digital process automation cloud flows and is available without a minimum purchase.
The third variant, hosted RPA, solves a different problem: the physical machine itself. Instead of providing and maintaining your own Windows computer, Microsoft provides the machine from its own Azure infrastructure. The Introduction to hosted Power Automate RPA describes two forms:
Both are licensed via the Power Automate Hosted Process license; the earlier name was the hosted RPA add-on. Since, according to the Licensing requirements for hosted machines is a superset of the normal Process license, every hosted bot automatically also covers unattended permission. Even so, it does not replace the Premium license: RPA developers still need a Premium license to create and manage desktop flows in the portal, and for hosted machines additional prerequisite licenses for Windows, Intune, and Microsoft Entra ID are required as well, because the machines are technically provisioned via Windows 365.
For practical purposes, this means: pure test automation on a single person's computer often gets by with just a Premium license. As soon as a flow needs to run at night or without a signed-in person, a Process license is added. And as soon as you no longer want to operate your own RPA machine, or the automation should grow and shrink depending on load, the Hosted Process license with hosted machines or machine groups is the right way to go. If you're unsure about the combination of licensing model, environments, and connectors, the Power Automate consulting from NordFlux helps you build a license structure that fits your actual automation needs. You retain control over which processes run under supervision and which run fully automatically.
No. The Premium license only provides an attended bot that works with a person signed in at the computer. For executions without human supervision, such as at night or on a schedule, the machine additionally needs a Process license with unattended permission.
A separate Process license is needed for each parallel unattended execution on the same machine. If only one desktop flow ever runs at a time on a computer, one license for that machine is enough.
No. The Hosted Process license licenses the hosted machine itself, not the person developing the flow. Anyone who creates and manages desktop flows in the Power Automate portal still needs their own Premium license.
Hosted machines are individual machines provided by Microsoft, well suited for development, testing, and operation by individual departments. Hosted machine groups bundle several such machines and scale them automatically as needed, which is intended especially for unattended automation at a larger scale.
Yes. Both the Process capacity for unattended RPA and the Hosted Process capacity for hosted machines are assigned per environment. If you use multiple environments for unattended or hosted RPA, you must set up the appropriate capacity separately in each individual environment.
Founder of NordFlux. Spent four years automating processes at enterprise scale at Dräger, and now brings that depth to the mid-market — pragmatic and with full data sovereignty.
Certifications
Set up unattended RPA: register the machine, assign process capacity, and switch the cloud flow to unattended mode, no gateway required.
Hosted RPA machines in Power Automate: Hosted Machines, Hosted Machine Groups, and how they differ from unattended RPA on-premises.
How to connect a legacy ERP without an API using RPA: MSAA selectors, attended/unattended modes, and the limits of Power Automate in SMEs.
Premium, Process and Hosted Process licenses differ sharply in price and use case, and picking the wrong one either overpays or bottlenecks the process. NordFlux maps your desktop flows to the right licensing model and plans the operations alongside it.