Proxy rules for login interface

Question

We're rolling out MS Teams behind a corporate proxy which requires users to accept an AUP the first time they access the Internet in a session.

This policy is bypassed for all traffic with a User agent string containing "Teams/*", but the login interface seems to use a generic UAS instead, so it failing until the user opens their browser and accepts the AUP to 'unlock' their Internet access.

I've also added http*://login.microsoft.com/* and http*://*.msidentity.com/* to bypass this policy, but it still seems to be failing. Do I need to add the A records that these CNAMEs resolve to as well? As these are hosted by a CDN, is there a more granular set of URLs I can add, or do I need to add the whole CDN Domain?

adam deltinger · Answer

Have you read this threads:https://techcommunity.microsoft.com/t5/microsoft-teams/issue-with-microsoft-teams-through-proxy/m-p/1621325https://www.lee-ford.co.uk/prepare-network-microsoft-teams/It might give you some light to the situation! Also Microsoft has a doc about proxies here:https://docs.microsoft.com/en-US/microsoftteams/proxy-servers-for-skype-for-business-online?Adam

Forum Discussion

Proxy rules for login interface

Share

Resources