Outlook.com Web Fails to Load – Server Side Error

harry westrop 0 Reputation points
2026-04-28T14:51:41.7166667+00:00

I can’t access Outlook.com Web. After signing in, it shows “Something went wrong” with these diagnostics:

• SerializationException

• JsonSerializationException

• BootResult: fail

• ErrorUnexpectedFailure

• HTTP 500

This happens on multiple devices, browsers, networks, and even with a second Microsoft account. This appears to be a server side OWA issue in my region. Please escalate to the Outlook.com service team to repair the affected cluster.

Outlook | Web | Outlook.com | Email

1 answer

Sort by: Most helpful
  1. AI answer

    2026-04-28T14:51:58.65+00:00

    The diagnostics and the fact that it reproduces across devices, browsers, networks, and even another Microsoft account indicate a backend Outlook.com/OWA service issue that cannot be fixed from the client side.

    End users and community responders cannot directly escalate or repair Outlook.com service clusters. The supported options are:

    1. Check service health and wait
      • For widespread backend issues, remediation is handled by the Outlook/Exchange Online service team. Similar issues (for example, classic Outlook failing with Exchange Online due to backend limits) are only resolvable by the service team and require a support case from the tenant admin.
      • If using Outlook.com as part of a Microsoft 365 subscription with an organization, the Microsoft 365 admin should check the Service Health dashboard and open a support case if needed.
    2. Use alternative clients while the issue persists
      • Use Outlook for Windows, Outlook for Mac, or mobile Outlook apps if they are still working for the account.
      • If classic Outlook for Windows is also affected by a backend issue, the documented workaround is to use Outlook on the web (OWA) or the new Outlook for Windows; in this case, since OWA is failing, continue using whichever client still connects successfully.
    3. Sign out everywhere if sign-in/session corruption is suspected
      • For some Outlook.com/Outlook sign-in and mailbox access issues, signing out of all Microsoft sessions and waiting for backend changes to propagate has resolved problems, even when they appeared server-side. The documented experience shows that access may not be restored immediately and can take many hours.
    4. If mailbox might be disabled (for work/school accounts)
      • For organizational accounts in Exchange Online, similar OWA “startup” failures with HTTP errors can occur when the mailbox is disabled while the Entra ID account is still active. In that case, the tenant administrator must check whether the mailbox is disabled and re-enable it if necessary.

    Because the failure is clearly server-side and reproducible across environments, resolution depends on Microsoft’s backend service team. The practical next steps are:

    • If this is a consumer Outlook.com account only: wait and periodically retry web access; optionally use another Outlook client that still works.
    • If this is tied to a Microsoft 365 tenant: ask the tenant admin to open a support case via the Microsoft 365 Admin portal so Exchange Online/Outlook.com support can investigate and, if applicable, request a service-side fix.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.