Cant login to Outlook

Question

Can't login to Outlook online, just returns 'Something went Wrong" & "Please try the recommended action below" but only shows UTC Date: Client Id: Session Id: Client Version: BootResult: Back Filled Errors: Rejection: etc

Answer 1

Hello,

More details are needed to identify the root cause of the issue.

I'm going to run through a few steps with you. Some of these are diagnostic — they help me narrow down what's wrong, not fix it outright. So if nothing changes after a step, that's normal and expected, not a dead end. I'll keep going until we've got this resolved.

1. Have you tried an InPrivate Window?
2. Is it an Exchange account or an Outlook account?
3. Could you post a complete screenshot of the error message?

I look forward to hearing from you to get the results of the troubleshooting.

Answer 2

Hi,

The specific screen you are encountering—complete with a raw diagnostic dump containing BootResult, Session Id, and Back Filled Errors—indicates a critical failure during the Exchange Online Open Web Architecture (OWA) bootstrap phase [1].

This is almost always caused by a corrupted local storage state, an expired token handshake, or an interrupted session cookie in your browser, rather than an issue with your password or account status.

To bypass this authentication loop without generic trial-and-error, please follow this structured technical triage:

Step 1: Isolate the Browser Profile State

Before clearing global data, check if the issue is tied to your active session state:

Launch an InPrivate / Incognito window and navigate directly to [https://outlook.live.com](https://outlook.live.com).

If you can log in successfully here, the issue is strictly isolated to your primary browser profile's active cache layer [2].

Step 2: Target the Session Tokens (Advanced Clear)

Instead of wiping your entire browser history (which clears other saved logins), perform a targeted purge:

In your browser settings, search for "Cookies and site data".

Select "Manage/See all cookies and site data".

Search for live.com, microsoft.com, and office.com, then delete only the tokens associated with these specific domains [2].

Step 3: Bypass the Cached OWA Directory

Sometimes the browser attempts to boot from a broken, cached redirection URL. Try forcing a clean redirection by using the absolute OWA endpoint directly in your address bar:

[https://outlook.live.com/owa/](https://outlook.live.com/owa/)

Step 4: Rule out Script-Blocking Extensions

Aggressive privacy extensions or script-blockers can inadvertently block the initialization scripts during the BootResult execution. If you use any extension that manages scripts or tracking, temporarily toggle it off for the Microsoft login page [2].

📑 Internal Documentation & References:

[1] Microsoft Learn Administration Docs: Troubleshoot Outlook on the web sign-in issues and OWA authentication errors. (Path: Exchange Online -> Digital Workspace Services -> OWA Sign-in Architecture).

[2] Microsoft Support Knowledge Base: Fix problems signing in to Outlook on the web / Guided Walkthrough. (Document ID: KB299c3e95 - Updated Deployment).

[3] Microsoft 365 Operations: Service Health Dashboard Verification Guidelines for Endpoint Authentication Issues.