When WAC is installed as the Gateway Service on a server it doesn't seem to be able to reach the internet via a locally configured proxy? I haven't tested connecting to Azure but the issue I have is I cannot connect to the Extensions feed and get this error: Feed is not available: 'https://aka.ms/sme-extension-feed'.
I tried configuring a machine proxy as well as in my local profile, but that also didn't work. In the end the only way I could get WAC to work via a proxy was to configure the proxy on the Network Service account that the WAC Gateway Service runs under (by default). Then WAC was able to connect to the Extensions feed.
Obviously this is not ideal and so I am wondering if we could have a way of configuring proxy settings in the Settings section within WAC in future? Or will this not be supported for some reason? Or should we run the WAC Gateway Service under a different account (e.g. gmsa) and set the proxy on that?
Proxy support is needed as the hack to provide the network service with proxy settings is not secure. Currently extensions installs/updates and Azure tools are affected by this lack of support. You can run the service as another account however this changes how Kerberos Resource Delegation is setup and also seems to break the remote powershell function. A supported mechanism for the admin center to work with a forward proxy for any internet access would be great.