How to fix something went wrong

Question

How to fix something went wrong

Lorie Millward 0

UTC Date: 2026-09-01T03:46:30.148Z
Client Id: 8B3B3D4D77294322BEF76753C2EBBA50
Session Id: 4259937d-e92d-42b7-a81a-716158af6a0e
Client Version: 20260821009.10
BootResult: configuration
Back Filled Errors: Unhandled Rejection: Error: 500:undefined|undefined:undefined
err: Microsoft.Exchange.Data.Storage.TenantAccessBlockedException
esrc: StartupData
et: ServerError
estack: Error: 500
    at Object.O [as createStatusErrorMessage] (https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.deepindex.9f609606.js:1:930)
    at https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.deepindex.9f609606.js:2:98134
st: 500
ehk: X-OWA-Error
efe: PH2PEPF00003857
ewsver: 15.21.360.13
reqid: 47fc8e22-26ca-12b9-b19b-f69f954b23e2
cv: 4Ty7KhsBQeXJBQCmY0GGzr.0.1.1

0 comments

1 answer

Your answer

Answer 1

Other users are reporting the same issue, which could be a server-side error. There is currently an Exchange error, and multiple users are also reporting Outlook outages.

https://status.cloud.microsoft/ You can check the status under "Exchange Online".

Current status: We're observing widespread recovery to Exchange Online mail connectivity, though the draining of backlogged mail queues may take longer for some organizations due to the volume of previously queued messages. Our recovery efforts are now focused on re-applying our targeted authentication component fix and restarting certain instances of infrastructure correlated with search functionality to ensure the full restoration of the associated scenarios.

Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.

Last updated: Tuesday, September 1, 2026 at 3:51:35 AM UTC