Share
ReportHi,
I would like to escalate an issue involving Power Automate cloud, Power Automate for Desktop, and machine runtime. The problem is broader than a single connection method and is currently preventing us from using desktop flows correctly.
We are facing two related issues:
First, when attempting to create the machine connection from Power Automate cloud, the machine is already registered and appears in the environment, but the connection does not work properly. This is not limited to one connection type. We have experienced the issue both when trying:
- Connect with sign in – Attended
- Connect with username and password
When using Connect with sign in – Attended, the error returned is:
Failed to create OAuth connection: ClientError: Test connection failed. Details: Connection failed: [Machine c2950854-4541-4294-b7b2-5f96d1fa2dd5] The machine is neither Microsoft Entra nor domain joined.
However, the issue is not only with Attended sign-in. Even when trying to connect using username and password, the setup still does not behave correctly overall.
The second issue is that on the desktop side, the machine can show as connected, the environment appears to be the same, and the connection appears to be in place, but no desktop flows are visible. In other words, the machine seems linked correctly, but the flows do not appear for use.
So this is not just an Attended sign-in problem. The overall issue is that:
- the machine is registered
- the machine shows as connected
- the environment appears to match
- the connection has been configured
- but the desktop flows still do not appear and cannot be used as expected
This suggests the problem may involve more than one layer, possibly including:
- machine identity or join status
- connection method compatibility
- account mismatch
- environment synchronization
- flow ownership or visibility
- licensing
- runtime or registration consistency
One point that also created confusion is that under Troubleshoot in machine runtime, the account shown is:
NT SERVICE\UIFlowService
At first, I thought this might be the username required for the machine connection, but it now appears to be only the internal runtime service account, not the actual Windows user account that should be used for authentication.
For context, the Power Automate / Microsoft 365 account being used is:
However, the Windows session on the machine may be tied to a different local, Microsoft, or personal account. Because of that, there may be a mismatch between:
- the Power Automate cloud account
- the machine runtime registration identity
- the Windows login account on the device
- and the account under which the desktop flows were created or are expected to appear
At this point, I need help determining whether these are separate issues or different symptoms of the same root cause.
Could you please review and confirm the following:
- Why the machine connection fails or does not work correctly across both connection methods
- Whether the machine identity or join status is affecting both authentication methods
- Which exact Windows credentials should be used for this machine
- Why the machine can appear connected while no desktop flows are visible
- Whether the flows were created in the same environment but under a different ownership, account, or unsupported setup
- Whether there is a synchronization issue between Power Automate cloud, machine runtime, and Power Automate for Desktop
- Whether licensing, runtime installation, machine registration, and environment selection are all correctly aligned
In short, the full issue is this:
The machine appears registered and connected, but the connection does not work properly through either Attended sign-in or username/password, and even when the environment and connection appear correct, no desktop flows are visible.
This is currently blocking us from using the machine reliably for cloud-to-desktop execution.
All responses (
Answers (
2,095
