Authentication error when trying to connect cloud flow to desktop flow

[skelecopter]

Power Automate Cloud is seeing my machine using the "Directly to machine" option of the desktop flows module, but I am trying to log in with my 365 username and password and getting this error:

Test connection failed. Details: Connection failed: [Machine (removed)] Connection error on the machine. Machine join type: NotJoined; Username type: (removed); Status: -1073741715; Details: The attempted logon is invalid.. Correlation id: 299c8a97-2376-47e5-bd97-eadaa3ebbbf7

When I try to use the "Connections" tab to create a new desktop connection, there is no "Create" button; it must be initiated from a flow, and I get the above error. I get the same error when I go into Connections to try to login there.

If I go into "Connections", delete the attempted connection and recreate the flow, it SOMETIMES presents me with the correct list of flows in my environment, and when I choose it, it shows me the correct variables I need to pass. But then it tells me that the connection is not authorized and go to into Connections and fix it, though there is no "Fix connection"; it just says "Connected" even though it clearly isn't.

This is on my personal laptop that is not fully part of the company domain, though I do have my 365 account linked. I have also tried to login using my local domain/username, but no dice with that either. I have no trouble connecting with any of our other 365 services remotely.

[Pstork1]

On the desktop open a command prompt and type Whoami.  That will show you the account your desktop is using.  Since you are on a personal machine it won't have your work or school account available to use when connecting a cloud flow to a desktop flow.  the Whoami command while you are logged in will show you the right account to use.

[skelecopter]

Thanks for the reply. I have tried to use my domain\username shown by whoami to login as well, but it just creates another broken connection that says "Connected" regardless. The only difference in the error is that the username type becomes domain\user

I'm out of ideas otherwise; I will be going into the office Monday to see if it works there with my work laptop that's fully part of the domain (and to active Virtual Desktop, haha)

[Pstork1 · Accepted solution]

Did you also double check in the Cloud Flow website under Monitor > Machines to make sure your machine is registered and Connected?  Also make sure you have an account that has a Per user flow license with RPA.

[skelecopter]

Okay, so I was using the trial, which may have been an issue. I added the RPA license to my account, and PAD popped up and said the license has been added, and now it is behaving differently.

I was able to complete the connection using my domain\username login, and it doesn't complain when using the Connections tab.

However, when I go to set up my flow, it now allows me again to select the desktop flow from my environment/machine, but it gives the same errors:

When I choose attended mode, that error disappears, but when I try to save the scenario, it is blocked with this message:

I can go back under "Connections" and update it again, and it seems to be successful, but I get the same errors in my flow again. I will also note that the second error is now appearing for other flows where it makes no sense:

This popped up once for a different flow that has existed for months, and even though I verified the Dropbox account it was asking about (that never changed), now it shows up every time I go to edit that flow. However, it doesn't block me from saving the flow in that case, and it works normally otherwise.

[Pstork1]

Not sure about the current error you are getting.  Normally that goes away after you approve the connections and save the flow one more time.  Are you trying to do attended or unattended?  

[skelecopter]

The license specified attended, so that's what I've been trying, though the result is the same with choosing unattended. My test flow is also just a manual trigger -> desktop flow, so there should be no other licensing complications with that either.

I also tried to open a second tab while building my flow to login again under the Connections tab, but I got the same.

I've sent this information to support too. The desktop flow will be running on my work laptop on site anyway, so I'm hopeful it will at least work then. I am also going to try again tomorrow just to make sure this isn't a symptom of just having registered for the license; maybe it takes some time to update fully?

[Pstork1]

When the cloud flow kicks off the desktop flow are you logged in as the WhoAmi account on the laptop?  That is the expectation for an Attended flow.  For unattended you would need to be logged out of the laptop.

[skelecopter]

Yes, I only have the one personal Microsoft account on this machine. I have my company 365 account linked in my user settings for Office apps, etc., but my machine is not managed by them (not joined to AAD)

[skelecopter]

Just wanted to follow up. Adding the full RPA license and giving it the weekend to think about it seems to have worked. I now have my cloud flow connected to my desktop flow from my personal laptop, and it is working as desired so far. I didn't have to let my machine be taken over by the organization or use my work laptop; I only had to link my work account in the user settings. Thank you so much for your help!

[jcam]

How did you solve it? By buying the full RPA license? I'm trying it first, so I got the free trial. I'm still unable to get past that test connection error. I'm wondering how did you manage to get it worked.