Attended vs Unattended RPA: Which Power Automate Desktop Mode Do You Need?
Deciding between attended and unattended automation modes is the most critical architectural choice you will make when building desktop bots. While attended robots work alongside you on your local machine with human supervision, unattended bots run autonomously on locked machines overnight. Understanding their distinct requirements, licensing costs, and operational limits ensures you choose the right approach for your workflows.
Key Takeaways
- Attended RPA runs alongside a human user on their PC, providing supervision and complete control over the automated tasks.
- Unattended RPA runs autonomously on locked, dedicated virtual machines or servers without human intervention, often working overnight.
- Attended mode is supported on the free tier of Power Automate Desktop, while unattended mode requires paid licensing and specific machine setups.
- Unattended workflows require a clean machine session and strict management of screen resolutions to prevent desktop element failures.
- Choosing the right mode depends on task frequency, supervision needs, and budget constraints for bot infrastructure.
Understanding Attended RPA and Human Supervision
Attended automation is designed for processes that benefit from human oversight, intervention, or manual triggers. When you operate an attended desktop flow, you hit 'go' and watch the software robot navigate through applications, populate form fields, and manage local files right beside you on your personal Windows workstation. This mode acts as a powerful productivity multiplier, taking over tedious copy-pasting or multi-step data entry tasks while keeping you firmly in control.
One of the standout features of attended automation is 'Picture-in-Picture' mode. This clever capability allows the automation to run inside its own isolated virtualized window that mirrors your desktop environment. As a result, the robot can execute its step-by-step instructions in the background while you continue working on emails, documents, or other applications on the primary screen. Because the free version of the Windows app fully supports attended execution, it serves as the ultimate zero-cost on-ramp for individuals and small teams looking to eliminate daily friction.
Unattended RPA: Automating While You Sleep
While attended bots require a human to kick off processes during the workday, unattended automation operates entirely behind the scenes. In this mode, the software robot securely signs into a dedicated machine or virtual server on your behalf, executes complex operational workflows, and signs out when finished—all while the physical screen remains locked and dark. It is the quintessential 'runs while you sleep' engine that converts nightly or batch chores into seamless background operations.
Organizations deploy unattended bots for heavy, structured data processing like processing hundreds of supplier invoices, synchronizing legacy enterprise resource planning (ERP) records, or generating daily financial statements. However, unlocking this capability requires careful planning around infrastructure and licensing. Unattended automation is not included in standard Microsoft 365 enterprise subscriptions; it demands paid capacity such as Power Automate process plans or hosted process plans.
Navigating Hidden Pitfalls in Unattended Deployments
Deploying unattended desktop flows introduces strict technical constraints that frequently catch developers off guard. Understanding these system rules prevents unexpected automation failures and wasted troubleshooting hours.
The Clean Machine Rule
An unattended flow cannot execute if any user session is actively open on the target machine, even if that session is locked. The operating system must be completely free of active local logins. When the schedule triggers, the automation engine creates an automated remote desktop session to perform its work.
Resolution and Element Matching
Because unattended flows initiate a remote desktop session behind the scenes, the resulting display resolution may differ from the screen dimensions you used when designing and recording the flow in your local environment. If the remote display is smaller than expected, critical buttons, input fields, or navigation menus can fall off the visible edge of the screen, causing the robot to fail when it cannot locate its target UI elements.
Managing Administrator Privileges
Unattended flows run under strict security boundaries and generally cannot execute tasks requiring elevated administrator-level rights. Any underlying legacy application or command-line utility that demands continuous security prompts must be re-evaluated and configured to run within standard user permission thresholds.
Comparing Costs and Licensing Realities
Budget planning is often the deciding factor when organizations choose between attended and unattended automation strategies. Relying on incorrect assumptions about what is included in existing software agreements can derail an implementation timeline.
Standard Microsoft 365 commercial licenses include cloud flows with standard connectors, but they do not cover desktop RPA bots or premium connectors. Consequently, expanding your automation footprint requires mapping out financial tiers:
- Free Tier: Enables local attended execution on your personal PC and cloud flows with standard connectors at zero cost. Ideal for personal productivity gains.
- Power Automate Premium: Priced around $15 per user per month, adding premium cloud connectors and attended desktop automation capabilities.
- Power Automate Process Plan: Priced around $150 per bot per month, providing one dedicated unattended bot instance for autonomous background processing.
- Hosted Process Plan: Priced around $215 per bot per month, where Microsoft fully manages and hosts the virtual machine hardware infrastructure for your unattended bots.
For teams hesitant to commit capital upfront, Microsoft offers a 90-day trial period supporting unattended execution. This trial window provides a risk-free opportunity to test unattended scripts and evaluate whether the operational time savings justify the transition to paid bot infrastructure.
Conclusion
Choosing between attended and unattended Power Automate Desktop modes comes down to balancing human supervision needs with infrastructure investment. Attended flows provide a frictionless, free entry point to streamline daily individual tasks right on your workstation. Unattended flows offer enterprise-grade scalability and autonomous overnight execution, but demand dedicated licensing, clean machine states, and careful resolution management.
To dive deeper into how desktop flows interact with cloud triggers, recorders, and pricing structures, Listen to the full episode of the podcast for an expert-led, jargon-free breakdown of Microsoft's powerful robotic process automation tool.
Frequently Asked Questions
Can I run unattended Power Automate Desktop flows on my personal laptop while I work?
No. Unattended flows require the target machine to be completely free and unlocked by any user session, as the robot creates its own isolated remote desktop session. If you are actively using the PC, you should use attended mode.
Is attended mode completely free to use in Microsoft Power Automate Desktop?
Yes, the free Windows app supports running desktop flows locally in attended mode on your own machine, allowing you to automate personal tasks without paying for a premium license.
What is the primary license requirement for running unattended desktop bots?
Unattended automation requires a paid tier such as the Power Automate process plan or hosted process plan, which covers the cost of the unattended bot and automated machine orchestration.
Why do unattended Power Automate Desktop flows sometimes fail unexpectedly?
Failures often happen due to screen resolution mismatches. When an unattended flow runs, it launches a remote session that may have a different resolution than your design environment, causing UI elements to shift off-screen.
