A Microsoft 365 administrator should check the tenant’s Exchange Online service health and then report the issue or open a support request with the complete OWA error payload so Microsoft can investigate the mailbox backend.
Since the failure persists across browsers and devices after session, cache, and private-window testing, repeating client-side troubleshooting is unlikely to add useful evidence.
1. Check for a tenant-scoped Exchange Online incident
- Sign in to the Microsoft 365 admin center with an administrator account.
- Go to Health → Service health → Exchange Online.
- Review:
- Active issues Microsoft is working on
- Issues for your organization to act on
- Issue history for October 26, 2026
- Open any matching incident and check its User Impact, affected services, status, and updates.
The Service health dashboard can expose tenant- or region-specific incidents that do not appear on the public status page. Service Support and Helpdesk administrators can view service health. ^1^
If a matching incident exists, use its incident ID and monitor the posted mitigation. A prior case with the same BootResult: throttle and TooManyObjectsOpenedException signature was associated with an Exchange Online incident, but that report was from November 2025 and does not establish that the October 26, 2026 failure is the same incident. ^2^
2. Report it if Service health shows no incident
On Health → Service health, select Report an issue and submit the failure. Microsoft correlates these reports across organizations and can publish an incident or advisory if it identifies a service-originated problem. ^1^
Include:
- Affected user’s sign-in address
- Exact UTC occurrence:
2026-10-26T12:24:46.028Z
- Request ID:
[GUID]
- HTTP status:
500
- Exception:
Microsoft.Exchange.Data.Storage.TooManyObjectsOpenedException
-
BootResult: throttle
- Error source:
StartupData
- Whether one or multiple mailboxes are affected
- Whether Outlook desktop or mobile is also affected
- Business impact and when the issue began
- Confirmation that it reproduces across multiple browsers/devices and after signing out of active sessions
Do not post the mailbox address, tenant identifiers, or fresh diagnostic IDs publicly; provide them only inside the authenticated support case.
3. Run the tenant-side connectivity diagnostic
Before opening the case, an administrator can go to:
Microsoft 365 admin center → Help & support
Enter a description such as:
Outlook on the web HTTP 500, TooManyObjectsOpenedException, BootResult throttle, StartupData
Run Outlook user connectivity diagnostics if offered. It checks service-side settings affecting the selected user. Microsoft documents the admin-center diagnostics as non-destructive unless the administrator consents to a proposed change. ^3^
Record the diagnostic result or run ID for the support request. The documented EWS Throttling diagnostic is migration-specific, so it should not be substituted for this OWA startup failure unless a third-party EWS migration is also involved.
4. Escalate through Microsoft 365 support
If no incident explains the failure:
- In the admin center, select Help & support.
- Enter the exception and request ID.
- If the suggested results do not resolve it, select Contact Support.
- Choose phone or email, provide the evidence above, and request investigation of the affected Exchange Online mailbox and OWA startup throttling.
- If all subscriptions were purchased through a Microsoft partner, contact that partner instead; Microsoft’s direct online support requires an eligible subscription purchased through Microsoft. ^4^
If you are not an administrator, send the error package to your organization’s Microsoft 365 administrator. Only an administrator can inspect tenant Service health and open the business support request.
The available information does not establish whether this is a product bug, a mailbox-specific condition, or an active Exchange Online incident. Microsoft support must correlate the request ID and UTC timestamp with backend telemetry to make that determination.
References
- How to check Microsoft 365 service health
- Error TooManyObjectsOpenedException persistent - Microsoft Q&A
- Self-help diagnostics for issues in Exchange Online and Outlook
- Get support for Microsoft 365 for business