How to configure a proxy server for Windows Azure Tools in Visual Studio 2013

Question

Hi Visual Studio/Azure Tools team
I would like to use the Windows Azure tools in Visual Studio 2013 to manage my Azure Web sites (Server Explorer -> Windows Azure -> Web Sites) from within my corporate network which is secured using a proxy server. Unfortunately, I am not able to use
the Windows Azure tools since the required HTTPS connection to windows azure is not going through the default configured proxy. Instead, Visual Studio tries directly to connect to port 443 which is blocked by our corporate firewall (and yes: there is no way
around using our proxy server). Other visual studio features like NuGet, updates, etc. work fine and use the configured proxy server. 
So my question: How can I configure visual studio respective its Azure tools to use a proxy server instead of a direct connection? I already tried configuring the proxy server within the file devenv.exe.config but this doesn't show any effect for Windows Azure
tools.
Regards
tschaena

Answer 1

As we have very similar problems I consider the found solution a work arround an existing problem which will not work if corporate FW policy does not allow such changes.
In my mind, any tools in charge of dealing with some sort of FW protocols should deliver the following information, should make it absolute clear how to setup that the request packages are setup rigth at the first time.
a) proxy server
b) proxy port
c) proxy user
d) proxy users-password
e) proxy.auth.Preference="BASIC"
And for moste tools (including Visual Studio and AZUR Tools) it is absolut unclear
a) how to setup that on a per tools basis
b) OR who inherits this information from whom    i.e. use the same as IE does, what if we use FireFox or any other browsers?
I understand that developers requested to cure such problem areas will often have difficulty to gain all required elemenst used to realy test the solution.
But I can tell you: I loos more time figthing down the FW setups for my clients. WHat I do at home in a sniff, takes ages to be realised by all the various clients on the market where each has to deliver the same sort of information but actually does not,
or has it just somewhere, but not in the vicinity of the demanding user.
Good examples i.e. NetBeans IDE where the Option Menu shows very clearly what information is required to pass through a FW/Proxy; but even there, the hint to start with a BASIC authentication schema is not part of this OPTION menu and must be added a JAVA
environment value. But at least, it works.
Sepp