We use a company proxy. Unfortunately, Power Automate Desktop seems to completely ignore the proxy stored in Windows. Is there a way to get PAD to use the proxy when logging in?
There might be something wrong with your Windows proxy settings or your proxy configuration blocking requests. It works fine for me with a proxy.
https://docs.microsoft.com/en-us/power-automate/desktop-flows/setup#prerequisites
https://docs.microsoft.com/en-us/power-automate/ip-address-configuration
No, I haven't found a workaround. I solved the problem by not using this product. 😉
I do not believe that. The proxy does not even receive requests.
The your proxy configuration in Windows is the source of the problem.
update
still not working , tried today in office without VPN and its still not working. I checked network traffic and I see the request from PAD to login and the response from proxy to authenticate. Offering three options. After this there is no more request from PAD and the error message appear . Looks for me the PAD client has a bug in the proxy authentication and get stuck.
Solved Fiddler showed that dns cloud not be resolved for login.microsoftonline.com...Looks like my cisco vpn client in version 4.7 didnt resolve the hostname proper after updating to cisco vpn version 4.9 dns resolution is working fine and I can also connect with my proxy (with Kerberos auth)
Hi,
I see that you get error 407 proxy "authentication". This is already the proxy reply, so you are calling it but without authenticated credentials. We had the same issue and we fixed it with setting the proxy settings to the Power Automate config files:
C:\Program Files (x86)\Power Automate Desktop\PAD.Console.Host.exe.config
C:\Program Files (x86)\Power Automate Desktop\PAD.Designer.Host.exe.config
This code has to be added to the PAD.Console.Host.exe.config and PAD.Designer.Host.exe.config:
<system.net>
<defaultProxy useDefaultCredentials="true" enabled="true">
<proxy usesystemdefault="True" proxyaddress="http://YourProxyDNS:PORT" bypassonlocal="True" />
</defaultProxy>
</system.net>
Wehre to put? Find this part of code:
(before)
...
<setting name="DataCollectionActiveFileDeletionInterval" serializeAs="String">
<value>00:05:00</value>
</setting>
</PAD.Console.Host.Properties.Settings>
</userSettings>
</configuration>
insert the <system.net> after the </userSettings>:
(after)
...
<setting name="DataCollectionActiveFileDeletionInterval" serializeAs="String">
<value>00:05:00</value>
</setting>
</PAD.Console.Host.Properties.Settings>
</userSettings>
<system.net>
<defaultProxy useDefaultCredentials="true" enabled="true">
<proxy usesystemdefault="True" proxyaddress="http://proxy:8080" bypassonlocal="True" />
</defaultProxy>
</system.net>
</configuration>
@Anonymous , thanks a lot . Creating the config file and enable use of default credentials fixed the problem .
it seem there is file named PAD.Designer.Host.exe.config, do I need to create it?
sorry, I mean there isn't file PAD.Designer.Host.exe.config
Hi, I'm facing this problem as well.
Does anyone recommend any proxy I can use to bypass?
now it works , I got proxy IP address from network team, and change 2 configuration file as previous document:
PAD.Designer.exe.config/PAD.Console.Host.exe.config, and create a new configuration file named PAD.Designer.Host.exe.config, with following content:
<system.net>
<defaultProxy useDefaultCredentials="true" enabled="true">
<proxy usesystemdefault="True" proxyaddress="http://[Your Company Proxy IP]:8080" bypassonlocal="True" />
</defaultProxy>
</system.net>
Hi,
first of all, thanks for the helpfull comments. It helped alot.
The only question i have is, where did you copy the <system.net> part into the C:\Program Files (x86)\Power Automate Desktop\PAD.Designer.exe.config ?
i cant find the /usersettings part
There are some registry entries one can use to configure Power Automate for desktop to interact with a corporate proxy server - Governance in Power Automate - Power Automate | Microsoft Docs
I hope that helps 🙂
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Announcing a new way to share your feedback with the Power Automate Team.