Skip to main content
J
jbourne6321
June 4, 2025
Solved

SSO in Edge giving me error 400

  • June 4, 2025
  • 1 reply
  • 305 views

I've been running 1Password using Azure SSO authentication for some time now and it's been going relatively smoothly. Yesterday I had one user complain they were getting the following 400 error:

I've done troubleshooting for this user and we've found that when they are signing in through Chrome (their secondary browser) then it will sign in fine, but signing in through Edge or trying to recover their account through Edge results in this error. I can't put my finger on what could be causing this although I have a feeling it's something quite simple. Has anyone else had anything previous and can advise?

Many thanks in advance.

Best answer by 1P_SimonH

Hi @jbourne6321,

Thanks for including the screenshot and the redaction!

Is it possible you're using our older "public client" config for Azure SSO? It isn't compatible with conditional access policies (CAPs) and the error you're seeing usually means CAPs are in use with the public client. If so, you can update to the private client and the user shouldn't get that error anymore: https://support.1password.com/migrate-entra-cap/ 

1 reply

1P_SimonH
1P_SimonHAnswer
Community Manager
June 4, 2025

Hi @jbourne6321,

Thanks for including the screenshot and the redaction!

Is it possible you're using our older "public client" config for Azure SSO? It isn't compatible with conditional access policies (CAPs) and the error you're seeing usually means CAPs are in use with the public client. If so, you can update to the private client and the user shouldn't get that error anymore: https://support.1password.com/migrate-entra-cap/ 

    J
    jbourne6321Author
    June 5, 2025

    It's possible, but what's throwing me is that this is only affecting a single user, in a single browser. My thinking would that if there was an incompatibility issue it would be more widespread across our userbase.

    J
    jbourne6321Author
    June 5, 2025

    Shows how much I know! Change made and this seems to be working now for the user who was experiencing issues. Many thanks for your help!

    Terms & ConditionsAccessibility statement

    ©2026 1Password. All rights reserved.
    4711 Yonge St, 10th Floor, Toronto Ontario, M2N 6K8, Canada