Configure a Power Automate Desktop flow to run unattended on a schedule without an active console session
domain: learn.microsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Allocate unattended RPA/process capacity to the target machine or machine group in the Power Platform admin center
Register the machine, or use a hosted machine group that Microsoft provisions automatically, and connect it with a dedicated unattended run-as account
Create a cloud flow trigger (scheduled or event-based) that calls Run a flow built with Power Automate for desktop, selecting the machine/machine group and the unattended connection
Ensure no active or locked Windows session exists for the run-as account on the target machine, since Windows 10/11 block unattended runs while any session, including a locked one, is present
Monitor runs in the desktop flow run history and use the built-in unattended-execution troubleshooting diagnostics for sign-in or session errors
Known gotchas
A leftover locked RDP or console session under the run-as account is one of the most common unattended-run failures — the machine must have no active session at all, not merely a locked one
Unattended execution requires a higher hardware bar than attended runs (Microsoft recommends four or more cores), so undersized VMs that work fine attended can fail or time out unattended
Machines removed from a machine group keep that group's settings rather than reverting to defaults, which can produce confusing behavior differences versus a similarly-configured standalone machine
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?