Error while signing in Power Automate Desktop

[parfotis]

Hello,

My cloud flows were having trouble connecting to a Windows machine used for running Desktop Flows.

I installed the latest update of Power Automate Desktop on the server, and when I restarted the application, the following error came up:

Some Microsoft Power Automate cloud services couldn't be resolved during startup. Run the Windows internet connections troubleshooter and if the issue persists contact your network administrator.

Internet connection seems to be working fine (via proxy), and of course the troubleshooter could not find any issues.

Unfortunately there is no hint as to which is the Microsoft service that cannot be connected. How can I approach this issue?

Thanks in advance,

Fotis

[Anonymous]

Hi,

I am in trouble because of the same problem.

I will describe the details of the error, so please help.

=======================================
I'm using "Power Automate Desktop" on Windows 10.
Last week I changed the version of "Power Automate Desktop" to "2.18.146.22083".

After that, I was asked to sign in to Microsoft Power Automate.
I signed in to Microsoft Power Automate. However, "Power Automate Desktop" prints a connection error and fails to sign in.

The following ID was displayed in the error message.
"078ae0c4-08d2-4c14-8971-f755815232be"

I have uninstalled "Power Automate Desktop". And I installed version "2.16.215.22020" of "Power Automate for Desktop".
As a result, "Power Automate Desktop" worked fine.
=======================================

Thank you.

[gtksi]

Hi,

Try to add ProxyServer key to registry.

https://docs.microsoft.com/en-us/power-platform-release-plan/2021wave1/power-automate/power-automate...

[Anonymous]

Hi, gtksi.

I am very grateful for your advice.

I followed the advice. As a result, Power Automate Desktop worked fine.

Thank you!!

[parfotis]

Hi gtksi,

Thank you very much for your input.

Unfortunately, adding "ProxyServer" registry key and restarting Power Automate Desktop, did not work in my case.

[gtksi · Accepted solution]

In my environment, "ProxyServer" value is "http://{proxyhost}:{port}".

ex. "http://myproxy.com:3128", not "myproxy.com:3128".

or, using proxy authentication? then, try to set "http://{username}:{password}@{proxyhost}:{port}".

[PetrosF-MSFT]

Hi all, 

Please note that if you are signing into Power Automate for desktop version released in March 2022 (version: 2.18) and you use Windows proxy settings, you may encounter a connection error on sign in.
To resolve that, please set the registry key as described in this article to configure Power Automate for desktop to interact with a corporate proxy server.
Thank you!

[parfotis]

Hello again,

It was the "http://" prefix that was missing from the registry value.

Adding it solved the issue.

Thanks for the help!

[cnitinpower]

Hi @gtksi 

Thanks for suggestion.

I have added proxyserver key details in registry. Before adding power automate desktop was not in hive 'HKEY_LOCAL_MACHINE'; so added and then made changes by renaming key and updated value.

Still getting same error.  Further do I need to do changes? Please help.

Regards,

Niti

[_Priyanka_125]

Hi,

I installed power automate desktop (version-2.23.114.22217) on my local system and power automate virtual agent for desktop (version-2.22.182.22184).I tried syncing both but its showing error.

Could you please help me with this issue...

Queries i have-->

1.why am I facing this issue

2.Do i need to downgrade the version of power automate.(If yes could you tell me how can I downgrade this      from)

3.I don't have a microsoft premium account...So do i need the premium account to downgrade this?

4.I am using windows 10 Enterprise version.

5.You said in your reply that you installed a lower version...

Could you help me with this...it would be very grateful 

Thankyou

[Anonymous]

I had a similar issue, after some google diving  i came about this article: 

https://powerusers.microsoft.com/t5/Power-Automate-Desktop/Cannot-sign-into-Power-Automate-Desktop-a...

which led me to this:

https://github.com/MicrosoftDocs/power-automate-docs/blob/main/articles/desktop-flows/governance.md#...

Regedit:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Power Automate Desktop\

Create DWORD UseMsalWindowsBroker, set value to 1.

Values

• 1: Power Automate for desktop will authenticate users using the WAM functionality.

And now i can log in properly.

[Lurker2]

Thank you. Had problem logging onto PAD on a AWS EC2 instance. After trying a plethora of different approaches and possible fixes, adding in this registry key fixed my issue.