Hi @Rachel,
Thank you for reaching out and sharing the details of the errors you’re seeing in Outlook. I know how disruptive it can be when you’re unable to access email - especially when both the Outlook app and Outlook on the web return different errors.
Your OWA error trace includes err: AccountTerminationException, along with Error 440 and esrc: StartupData, which typically indicates that the mailbox object itself is disabled, even when the Entra ID (Azure AD) user account still appears active. In these situations, the user can sign in normally at the identity layer, but Exchange Online treats the mailbox as terminated or disabled, preventing Outlook and OWA from loading.
This also aligns with the Outlook app message, “We couldn’t reach the email server. Please try again,” since the client can’t establish a mailbox session when the mailbox is in a disabled state.
Below are the actions required on the admin side. Kindly share these instructions with your IT administrator so they can complete the necessary checks:
1/ Check whether the mailbox is disabled
Get-Mailbox ******@domain.com | fl AccountDisabled
If the result shows AccountDisabled : True, that matches the behavior indicated by the AccountTerminationException error.
2/ Re-enable the mailbox
Set-Mailbox ******@domain.com -AccountDisabled $false
3/ (Optional) Identify any other disabled mailboxes
Get-Mailbox -ResultSize Unlimited | Where-Object { $_.AccountDisabled -eq $true }
After re-enabling, have the user try signing into Outlook on the web again.
Here are the next steps you can try after your IT administrator completes the checks above:
A/ Refresh authentication
- Sign out of all Microsoft sessions
- Sign back in using
https://outlook.office.com/
B/ Clear browser session
- Try InPrivate/Incognito
- Or clear cookies for
outlook.office.com
C/ For the Outlook app error (“We couldn’t reach the email server”)
If the mailbox is re-enabled but the desktop client still fails:
- Remove cached credentials (Windows Credential Manager > Windows Credentials > Generic Credentials > remove Outlook/Office entries)
- Disconnect and re-add the Work/School account under Windows Settings
- Restart the device and sign in again
These steps address cached authentication failures that can persist after mailbox reactivation.
I hope this information helps. Please try the steps and let me know whether they resolve the issue. If the problem persists, we can work together to find a solution.
As other users will also search for information in this community, your vote can significantly help those with similar inquiries quickly locate the most relevant resources.
Thank you for your kindness and for contributing to the forum.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.