Is Exchange Online experiencing widespread mail delivery and Outlook Web issues?

0
4
Asked By MellowCedar42 On

Is anyone else seeing Exchange Online problems, especially in the US Central and Midwest regions? Internal messages are intermittently failing with errors such as `432 4.2.0 STOREDRV.Deliver.Exception:AgentGrayException.CryptographicException` and `550 5.6.200 STOREDRV.Deliver; message is treated as poison`. Some users cannot send or receive mail, Outlook on the web fails to load, search is unavailable, and messages accepted by connectors do not appear in message trace. The impact seems inconsistent across users and tenants, while the service health dashboard may still show no active issue. Has Microsoft acknowledged this, and are there any known workarounds?

4 Answers

Answered By CopperLime63 On

We have users who can send but cannot receive anything, while others cannot send to themselves at all. Outlook on the web is also failing for several accounts, and search is broken. The issue appears to be affecting parts of the Midwest, including Iowa, but not necessarily every user in a tenant.

VelvetMaple29 -

We are seeing similar behavior in the central US. Connectors accept incoming mail, but the messages never appear in Exchange message trace or user mailboxes.

Answered By NorthwindPanda18 On

Our queues are showing `550 5.6.200` errors saying the messages are being treated as poison. Some mail gets through, but delivery is very unreliable. The problem initially appeared intermittent and then became more widespread.

Answered By QuartzHarbor7 On

Yes, we are seeing the same issue across our tenant. Internal mail is failing or being delayed, and the affected users seem to vary. The symptoms are consistent with a service-side Exchange problem rather than a local configuration issue.

MellowCedar42 -

Thanks for confirming. It helps to know this is affecting more than one tenant.

Answered By BrightOtter51 On

There appears to be a Microsoft incident associated with reference `EX1464935`. It may not immediately appear as affecting every tenant in the service health portal, so the dashboard can remain green even while users are impacted. Opening a support case and retaining message IDs, queue details, and timestamps is probably useful while waiting for the incident update.

MossyOrbit84 -

We also opened a case, but the initial response was unrelated and did not address the Exchange Online symptoms. The incident reference may take time to show consistently in the portal.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.