Mozilla Monitor website will be down for 2 hours starting 5/20/2025 at 6 AM PT. Visit our status site for updates.

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox cannot complete oauth dance to login.microsoftonline.com

  • 1 reply
  • 5 have this problem
  • 31 views
  • Last reply by dwlocks

While trying to open the outlook web interface (OWA) via any of it's various names (such as https://outlook.office365.com), I am eventually redirected to https://login.microsoftonline.com/. The firefox UI says the server cannot be found, however, if I watch the network trafic, it actually seems that the problem is SSL. The get to microsoftonline.com is marked as insecure (the lock icon has a red slash), even though the protocol is https.

I can't figure out how to get more descriptive errors.

I'm fairly sure this is a certificate problem. Chrome can access OWA, but every firefox installation on every device I have (linux and android) shows this error.

Normally ssl problems give a popup that I know how to handle. I suspect that because this is part of an oauth dance, or because it's in the middle of a redirect chain, I cannot see the correct errors.

Any ideas on how to fix this or to get more informative errors?

While trying to open the outlook web interface (OWA) via any of it's various names (such as https://outlook.office365.com), I am eventually redirected to https://login.microsoftonline.com/. The firefox UI says the server cannot be found, however, if I watch the network trafic, it actually seems that the problem is SSL. The get to microsoftonline.com is marked as insecure (the lock icon has a red slash), even though the protocol is https. I can't figure out how to get more descriptive errors. I'm fairly sure this is a certificate problem. Chrome can access OWA, but every firefox installation on every device I have (linux and android) shows this error. Normally ssl problems give a popup that I know how to handle. I suspect that because this is part of an oauth dance, or because it's in the middle of a redirect chain, I cannot see the correct errors. Any ideas on how to fix this or to get more informative errors?

Chosen solution

Updating from FF 57 to FF57.0.1 solved the problem. No clue what the root cause was.

Read this answer in context 👍 0

All Replies (1)

Chosen Solution

Updating from FF 57 to FF57.0.1 solved the problem. No clue what the root cause was.