So you’re saying you have a Proxy somewhere and your Microsoft Teams Room isn’t signing into Teams?

Jimmy Vaughan
4 min readDec 29, 2019
A proxy server functions on behalf of the client when requesting service, potentially masking the true origin of the request to the resource server and is not uncommon in enterprise networks.

One of the challenging parts about setting up the Microsoft Teams Room systems for customers is that they want to treat it as something other than what it is and try to make it more complicated than things need to be.

It is a purpose built Windows 10 PC that acts similar to those that you deal with everyday as an IT administrator.

This is the case many times when for example you are dealing with the AV department for the conference room solutions and the IT department doesn’t want the AV equipment on their network. While not always the case, I find myself as the person asking “It’s not signing into Teams, do you have a proxy?” Only to hear the reply of “I don’t know, how can I tell?” way too many times in a troubleshooting effort.

While there are many ways of “investigating” if there is a proxy (for example looking at the PC that the AV department is working on), I am going to focus here on a few tricks to make sure that you are navigating the proxy correctly on the Microsoft Team Room systems so that they can sign into Teams.

I previously wrote an article about debugging the “cannot fetch calendar” error and this result could happen as well if your calendar is M365 while your Skype server is on-prem. You might also encounter the error could not sign into Teams if you have a proxy, but your on-prem Skype might actually sign in, so it sometimes presents a challenge to the non-network skilled techs who are just looking for everything to “just work”.

On one particular installation I was challenged with, there was an on-prem Skype server with O365 exchange and Teams online. Skype signed in just fine since I was within the network, but exchange and Teams would not login. My first step was to go in and see if Microsoft Edge would navigate to any page on the internet and sure enough it could not reach any. So I knew that I was dealing with an issue reaching outside but was on the local LAN since Skype worked just fine. I found the proxy information on a different PC and copied that over and now Microsoft Edge could navigate as expected in admin, but it still would not login. I checked audit logs on O365 to see if the account had ever attempted a login and if we…

--

--

Jimmy Vaughan

With over 20 years of experience in AV and IT roles for a well diverse combination of employers, I have a specialty in devices and solutions for meeting spaces.