I usually don’t blog about ADFS but since I recently had to solve this issue for a customer I thought someone else might find it usefull as well.
When you use Edge or Chrome as your primary browser and using a machine that should have SSO with Office 365 and Sharepoint you still get a login page. This happens because by default ADFS have a set of trusted browser strings and others will be prestend with a form authentication.
To fix this on your ADFS server you need to use a couple of simple powershell commands.
Let’s start with just getting what browser strings are trusted currently.
Get-ADFSProperties | Select -ExpandProperty WIASupportedUserAgents
As you can see there browser agent for Edge and Chrome are missing. To fix this we run the following powershell command.
Set-AdfsProperties –WIASupportedUserAgents @("MSAuthHost/1.0/In-Domain","MSIE 6.0","MSIE 7.0","MSIE 8.0","MSIE 9.0","MSIE 10.0","Trident/7.0", "MSIPC","Windows Rights Management Client","Mozilla/5.0","Edge/12")
Then restart the ADFS service
That is, you can verify the settings by getting the ADFS properties again
All done and Single Sign On will should now work using Edge or Chrome as well!