09-20-2018 08:47 AM
09-20-2018 08:47 AM
Does anybody know what proxy setting Teams is using?
I am in corporate environment, behind a web proxy, and Teams works fine up to the point I want to attend an audio meeting. I figured out that at the time I am attempting to join, there are requests to *.relay.teams.microsoft.com and *.tr.teams.microsoft.com that are going through our proxy and this fails.
I figured out that if the connection goes through hosts in these domains directly (bypassing the proxy), audio meetings work fine.
As I don't have control over this corporate proxy and proxy auto configuration (PAC) file, I configured my Internet proxy settings to a specific web proxy, bypassing these domains, and I validated that my web browser is well taking into account such bypass configurations.
However, Teams persists in connecting through our web proxy for such domains, and even after restarting, rebooting...
Therefore, what proxy settings is Teams using? How can I configure it to bypass our web proxy for these domains?
09-21-2018 06:32 AM
Which browser settings though? Being an electron app, I imagine Teams would look at the Chrome settings, if installed, but I haven't actually bothered to check. My point being, configure them in both Chrome and IE, and if that fails, also change the WinHTTP ones via netsh.
09-21-2018 06:48 AM
@Vasil Michev, thanks for your answer.
Edge, MSIE and Chrome are all using my Windows system Internet settings. WinHTTP is configured for Direct access. It looks like that Teams is using some of the system proxy settings, e.g. use the configured proxy server, but not all of them, especially not settings about bypassing my proxy for specific domains. I also monitored Teams using SysInternals ProcMon and saw it reading system proxy setting from registry.
When I monitor all proxy accesses (WireShark configured to display "CONNECT" requests to my proxy server), I can see my web browsers honoring proxy settings (bypass or not), but not Teams.
10-02-2018 03:55 AM
We are seeing this too in our environment:
PAC file in use, Teams very slow to open, drops calls etc.
Proxy set in proxy options, Teams opens normally, but we are limited in the size of the bypass list so not a solution.
Need to know how to pass proxy settings directly to Teams / electron app.
10-02-2018 02:36 PMSolution
You really shouldn't be sending teams calls via a proxy, the ip addresses listed as optimize in this list need to have directly, unrestricted connection
For a quality experience with audio calls Teams needs to be sending UDP/STUN traffic directly, as it's not HTTP it has nothing to do with proxy settings or pac. Only if these ports are being blocked Teams will attempt to use HTTPS but the reliability and latency suffer. I can't really explain the difference you see, but maybe you've got some elements in your pad which take a long time to respond, for example using isInNet(), isResolvable(), and dnsResolve() are generally unacceptably slow.
10-03-2018 12:47 AM
Thanks for your answer.
Even if I understand that it would be better if traffic isn't converted to use HTTPS, in case it does because ports aren't open, it would be good if we could control how proxy settings are used (or not), as traffic may be allowed to go through directly on port 443, without going through a web proxy (what adds another layer of quality degradation).
10-03-2018 12:49 AM
I am fully aware of the recommendation to NOT use a proxy / bypass a proxy for the 365 et al IPs/URLs.
My point is:
1. if I use a PAC file to control the bypass, TEAMs breaks.
2. if I use set a proxy in the browser's proxy settings fields (and then bypass at the proxy level itsself), TEAMs works.
the result is: TEAMs does not function as expected when a PAC file is in use.
We are running Symantec SmartConnect (SSC) locally on the end points. I can (successfully) dictate the bypasses directly to SSC, so traffic IS bypassed before it leaves the device.
However, even with the SSC level Bypass set, if there is ANY form of PAC in use, TEAMs is troublesome. I have tested with a single item in the PAC file... still takes 5 mins for TEAMs to open/login. Calls still drop. If I remove the PAC file entry and set localhost in the Proxy settings field (SSC listens locally), the bypass works correctly (based on it being done by SSC, rather than the browser).
So, the issue here is that TEAMs does not consistently/correctly use the OS/Browser configured proxy settings if a PAC file is configured.
10-03-2018 07:31 AM - edited 10-03-2018 07:34 AM
@Marc Panton a pac file only defines what happens to HTTP traffic, it's not at all relevant or considered by UDP, so by definition you can't get teams UDP media to bypass your proxy through a pac. It relies on your network edge firewalls and DNS allowing traffic to resolve. Anyway, that was more an answer toyour comment about unreliable calls.
Your specific startup scenario sounds different, HTTPS traffic is used for authentication from the Teams client and should be ok to follow your proxy route. I've used the same setup in previous organisations without issue. I would suggest using a tool like Fiddler to see what happens. My complete guess would be that a proxy is refusing to respond until a timeout is reached. It's certainly not something I've seen before here, and is different to the other issue. I would also suggest raising a support case as the engineers there can help you diagnose more about what's happening in your environment.
10-08-2018 02:51 AM
Teams vs proxy does NOT seem to be the issue. the autoupdate aspects of the default Teams install does though:
Default / current install:
Task bar shortcut target:
C:\Users\%username%\AppData\Local\Microsoft\Teams\Update.exe --processStart "Teams.exe"
Now, when you use the task bar icon to open Teams, it opens in normal time.
n.b. This only impacts the TASK BAR icon for Teams. You will also need to stop Teams automatically opening on login (settings of teams, un-tick Auto login)/StartupTab of Task manager, disable Teams).
If you still want Teams to auto start, but use the new settings above, you will need to create a shortcut and drop into:
Obviously, this has other impacts: your Teams app will cease to update. You will need to come up with a process to update it by other means. Use at your own risk!
10-08-2018 03:21 AM
10-08-2018 03:26 AM
We are staging via GPO UNC share to local folder, then proxy settings set via GPO use defined path locally, not a web address. (We do it that way as W10/Edge had issues with PAC files from a web share)
I'll have a read of the second.
10-09-2018 08:46 AM
thanks for the help all and @Steven Collier
12-03-2018 05:18 AM
I figured out that, if an environment variable HTTPS_PROXY is defined, MS Teams seems to use it, instead of the Windows "Internet Settings". Its format must be like http://user:email@example.com:port