Share via

After the last o365 update new outlook started to show the next message when I try to start it - We raid into an error - Microsoft. Exchange.Data.Storage.TenantAccessBlockedException

Anonymous
2025-06-06T00:38:23+00:00

We raid into an error - Microsoft. Exchange.Data.Storage.TenantAccessBlockedException

UTC Date: 2025-06-05T13:12:53.347Z

Client Id: --removePII--

Session Id: --removePII--

Client Version: 2025053000406

Native Host Version: 1.2025.527.300

BootResult: configuration

err: Microsoft Exchange Data Storage TenantAccessBlockedException

esr StartupData

et: ServerErmor

estack: Error: 500 at ObjectA [as createStatusErrorMessage]

(https:/res public.onecdn static microsoft/owamail hashed-

V1/mobyscripts/owa.native.ef98e6ct js:1:1043) at

hitpsres public onecdn static microsoft/owamail hashed

Vi/mobx/scripts/owa.native ef98e6c6,5:3:66034

: 500

ehk: X-OWA-Error

efe: MNOP222CA0028, SCXP29BCAD1S3

ewsver: 15208792.34

emsg: TenantAccessBlockedEror

backiilledErrors: Back Filled Errors: Unhandled Rejection: Error: S00:undefinedjundefined:undefined

Please, can somebody help me to fix this error?

Best,

Miroslav

Outlook | Windows | New Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2025-06-23T14:08:59+00:00

    Hi Alex,

    Nothing worked. :-(

    But the issue is resolved after the last O365 update.

    Looks like that some data after disconnecting old business account was still persistent is some config.

    Thank you for your help.

    Best,

    Miroslav

    0 comments

13 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-06-12T01:21:38+00:00

    Hi Miroslav Pavlovic2,

    It has been a while and I am writing to see how things are going with this issue. Have you had a chance to check the replies provided? Any update would be appreciated.

    Best regards

    Alex - MSFT | Microsoft Community Support Specialist

    0 comments
  2. Anonymous
    2025-06-12T15:48:53+00:00

    Hi Alex,

    Thank you for following up. I did not have time to finish the procedure - lot of tasks last days, but I will continue until solve the issue. I hope that tomorrow i will have quiet day to apply the other steps.

    Until now i did:

    1. Switch back to New Outlook -> not successful
    2. Clear credential cache -> I am on step d). I noticed lot of references. First, I cleaned registry Outlook folder but not worked. Now I need to finish the cleaning and go to steps 3 and 4.

    Best,

    Miroslav

    0 comments
  3. Anonymous
    2025-06-17T08:25:41+00:00

    Hi Miroslav Pavlovic2,
    If you still have further concerns, please feel free to let us know.

    0 comments
  4. Anonymous
    2025-06-24T00:20:27+00:00

    Hi Miroslav Pavlovic,

    It's wonderful news that the issue has been resolved. I sincerely apologize for any miscommunication earlier, and I truly appreciate your effort in finding a resolution. I believe that many users may encounter a similar issue, and your case could serve as a valuable reference for them.

    Therefore, I would make a brief summary of this post so that other forum members could easily find useful information here:

    Issue Description:

    After a recent Office 365 update, the user encountered the error Microsoft.Exchange.Data.Storage.TenantAccessBlockedException when launching the new Outlook. The error occurred even before login, affecting both work and personal accounts.

    Assessment:

    • The issue was likely caused by residual configuration data from a previously disconnected business account.
    • Multiple troubleshooting steps were attempted, including license verification, credential cache clearing, registry cleanup, and switching between Classic and New Outlook.
    • Ultimately, the issue was resolved after a subsequent Office 365 update.

    More Information:

    • The user confirmed that Outlook Classic worked without issues.
    • The resolution came after a new update, suggesting that the root cause may have been addressed by Microsoft in the backend or through a patch.

    As other users will also search for information in this community, your valuable vote will definitely help others with similar queries find the correct channel and useful information more quickly.

    Please let us know if you would like further assistance. 
    Greatly Appreciate again for your patience and understanding. 

    Warm regards,
    Alex - MSFT | Microsoft Community Support Specialist

    0 comments