Forum Discussion
kpsingh
Jul 09, 2020Copper Contributor
Why Teams desktop client does not auto-login using ADFS?
On a domain bound machine, while opening MS Teams it does not auto-login user and shows following prompt: Tried to SSO to MS Excel and it worked on same machine and did not prompt for cred...
- Jul 17, 2020Btw, maybe worth looking at https://docs.microsoft.com/en-us/office365/troubleshoot/sign-in/sign-in-issue-with-modern-auth
LiborTomes
Dec 07, 2020Copper Contributor
kpsingh Hello,
in my case this was helpful. You have to set ADFS properties to support Edge Chromium. However I don't have SSO running so I have to type login credentials.
AD FS on Windows 2016 and later:
Set-AdfsProperties -WIASupportedUserAgents @("MSIE 6.0", "MSIE 7.0; Windows NT", "MSIE 8.0", "MSIE 9.0", "MSIE 10.0; Windows NT 6", "Windows NT 6.3; Trident/7.0", "Windows NT 6.3; Win64; x64; Trident/7.0", "Windows NT 6.3; WOW64; Trident/7.0", "Windows NT 6.2; Trident/7.0", "Windows NT 6.2; Win64; x64; Trident/7.0", "Windows NT 6.2; WOW64; Trident/7.0", "Windows NT 6.1; Trident/7.0", "Windows NT 6.1; Win64; x64; Trident/7.0", "Windows NT 6.1; WOW64; Trident/7.0", "MSIPC", "Windows Rights Management Client", "Edg/*")
AD FS on Windows 2012 and earlier:
Set-AdfsProperties -WIASupportedUserAgents @("MSIE 6.0", "MSIE 7.0; Windows NT", "MSIE 8.0", "MSIE 9.0", "MSIE 10.0; Windows NT 6", "Windows NT 6.3; Trident/7.0", "Windows NT 6.3; Win64; x64; Trident/7.0", "Windows NT 6.3; WOW64; Trident/7.0", "Windows NT 6.2; Trident/7.0", "Windows NT 6.2; Win64; x64; Trident/7.0", "Windows NT 6.2; WOW64; Trident/7.0", "Windows NT 6.1; Trident/7.0", "Windows NT 6.1; Win64; x64; Trident/7.0", "Windows NT 6.1; WOW64; Trident/7.0", "MSIPC", "Windows Rights Management Client", "Edg/79.0.309.43")
More in this article https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/configure-ad-fs-browser-wia
Hope this helps I was stuck hours in checking SSO and AD FS.