Forum Discussion
aleks_m
Dec 07, 2019Copper Contributor
Authentication popup for autologon.microsoftazuread-sso.com:443
Hello, Using Teams 1.2.00.32462 on Windows 10 1909. The last week or so I've been starting getting popups asking me to authenticate to autologon.microsoftazuread-sso.com:443 with a username and pas...
Carol DeMuth
Feb 12, 2020Brass Contributor
Ulf Lundqvist We have noticed the problem popping up as well. We do have single sign in enabled, but most of our users utilize different browsers - Edge and Chrome so the suggestions above aren't really helping. I would like to know if there is a solution as well
ph_ly
Feb 17, 2020Iron Contributor
Hi Carol,
I am confused as to the browser reference, as these prompts should be occurring inside of the windows teams app. The authentication setting inside of Internet Options - Intranet Zone should remediate it.
I am confused as to the browser reference, as these prompts should be occurring inside of the windows teams app. The authentication setting inside of Internet Options - Intranet Zone should remediate it.
- Carol DeMuthFeb 18, 2020Brass Contributor
ph_ly We pushed out the sites through a GPO policy for IE settings, but most of our staff use Chrome or Edge as their browser so I wasn't sure if that was causing an issue. We do have IE set as the default browser for everyone and the correct settings have been pushed out through GPO. It seems to be a problem that pops up mostly when they try to open a file like Word or Excel.
- ph_lyFeb 19, 2020Iron ContributorYes, the error originally occurred with the Edit In Teams function and seems to be more prevelent now.
The trusted/Intranet settings are respected by Chrome and Edge, actually. No need for an ie default. However in this case the Teams app uses a built in web browser which needs the settings.
If you are saying the issue persists after adding the site to the Intranet Zone (not the trusted sites zone as others have indicated, as it doesn't have the right autologon setting by default) then something else must be up. In all my instances adding the https://autologon.microsoftazuread-sso.com fixes the issue.