Google chrome asking for username and password for OWA

Solution 1:

If your organization is using a logo or retrieves any of the images using an FTP path, you'll have to authenticate for that FTP connection. This would be why, even if you don't authenticate, you can still get to the OWA site. Have your OWA admin check where the images are being hosted from and redress (move them to your company website perhaps?) accordingly.

Solution 2:

This is probably a proxy username and password having do do with either a pac file that chrome doesn't auto-discover, but IE and Firefox do or NTLM authentication. And yes, some proxies will ask for authentication, then proceed to function just dandy without being authenticated, although they will keep asking.

Solution 3:

Try putting in the full path to the OWA site in Chrome, including the "https://", I've noticed on our WES that if you don't put the https:// and if you leave off the /owa at the end, it will flash an error page that redirects to the main login. So maybe Chrome handles that redirect page differently.