The 500 error shown in the screenshot is generated by the Outlook on the web (OWA) service itself, not by the browser. In similar Outlook/OWA sign‑in issues, the root cause is usually on the service side (for example, mailbox, license, or permissions configuration) and not something that can be fixed by clearing cache or changing browsers.
Because the account works in other Microsoft 365 apps but fails when accessing Outlook on the web, this needs to be investigated and fixed by Microsoft 365 support for the tenant. The recommended action is:
- Capture the full error details shown on the error page (UTC time, Client Id, Session Id, and the full error text).
- Open a support ticket from the Microsoft 365 admin center so Microsoft can check the mailbox and service configuration for the account and correct it on the backend.
- If the issue is widespread in the tenant, the admin should also check the service health dashboard in the Microsoft 365 admin center for any ongoing Outlook on the web incidents.
If this is a consumer Outlook.com account and not part of a Microsoft 365 organization, use the “Contact Support” option from Outlook on the web or the Outlook app to escalate the error to Microsoft, including the error details from the page.
References: