Forum Discussion
PBI Desktop connect to Azure via Proxy
It didn't work for me, but perhaps i've done something wrong. This is the steps i took:
- Created a new empty file called Microsoft.Mashup.Container.exe.config
- Using Notepad++ i've copied in the code from your link into this config file and saved
- I've coped this config file into C:\Program Files\Microsoft Power BI Desktop\bin
- I've loaded up Power BI and opened a project file whose connections are to a database in Azure
- I have gone into Edit Queries to test the connection, recieving the usual error. (This file works on my Azure VM)
Ross73312, that process looks correct. The only potential gap I see: the solution I proposed assumes you are able to authenticate through your proxy via the Windows Active Directory credentials associated with the user session you're using Power BI Desktop on (which implies that Power BI Desktop reads those same credentials as the "default credentials".
If that's not the case in your environment, then I'd recommend:
A) Determing how you can authenticate through the proxy in your environment.
B) Using these docs to modify the proxy config file you created.
It's too bad Power BI doesn't yet have a front-end UI interface for configuring proxy awareness.
Thanks Anonymous Yes thats how our environment works, sadly the process doesn't work for me.
Hi,
I'm running into the same issue with PBI and the Big Query connector.
I created the Microsoft.Mashup.Container.exe.config file with no success...
My proxy is using NTLM.
I tried two solutions:
1:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.net>
<defaultProxy useDefaultCredentials="false">
<proxy
usesystemdefault="true"
proxyaddress="http://user:password@mycompanyproxyaddress:80"
/>
</defaultProxy>
</system.net>
</configuration>2:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.net>
<defaultProxy useDefaultCredentials="true">
<proxy usesystemdefault="true"/>
</defaultProxy>
</system.net>
</configuration>Where could I go now.... ?
Hi,
I'm running into the same issue. I think my company proxy is using NTML.
I tried 2 solutions:
1:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.net>
<defaultProxy useDefaultCredentials="true">
<proxy usesystemdefault="true"/>
</defaultProxy>
</system.net>
</configuration>2:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.net>
<defaultProxy useDefaultCredentials="false">
<proxy
usesystemdefault="true"
proxyaddress="http://user:password@mycompanyproxyaddress:80"
/>
</defaultProxy>
</system.net>
</configuration>Where can I go now... ?
Many thanks
Anonymous hi Ross, did you manage to resolve the proxy issue? We're experiencing the same here and still pondering our options. Thanks.
No. I use a VM RDP hosted in Azure for my data refreshing. Our network guys think they might be able to do a solution eventually but i'm not really across the details. Nothing positive has occured so far because i think the Azure IP address change frequently, which is what any networking solution would rely upon.
