{"id":309431,"date":"2025-03-15T09:08:45","date_gmt":"2025-03-15T08:08:45","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=309431"},"modified":"2025-03-15T09:08:45","modified_gmt":"2025-03-15T08:08:45","slug":"exchange-online-service-health-incidents-ex1027675-und-ex1030895","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2025\/03\/15\/exchange-online-service-health-incidents-ex1027675-und-ex1030895\/","title":{"rendered":"Exchange Online Service Health Incidents: EX1027675 und EX1030895"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"\" style=\"margin: 0px 10px 0px 0px; display: inline; float: left; border-width: 0px;\" title=\"Exchange Logo\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2022\/06\/Exchange.jpg\" alt=\"Exchange Logo\" width=\"138\" height=\"121\" align=\"left\" border=\"0\" \/>Bei Microsofts Exchange Online gibt es ja seit Ende Februar 2025 massive Probleme. Microsoft ver\u00f6ffentlicht im Exchange Online Service Health-Dashboard auch Statusmeldungen zu diversen Vorf\u00e4llen. Ich stelle nachfolgend die Incidents EX1027675 und EX1030895 zu den <em>Non-Delivery Report (NDR) containing an error stating \"554 5.6.0 Corrupt message content\"\u00a0<\/em>Fehlern ein.<\/p>\n<p><!--more--><\/p>\n<p>Ich selbst haben keinen Zugriff auf diese Eintr\u00e4ge. Ein Blog-Leser hat mir mal einen Schwung Meldungen zugeschickt (danke), die ich hier im Blog ver\u00f6ffentliche.<\/p>\n<h2>Incident EX1027675<\/h2>\n<p>Hier der Text des Vorfalls EX1027675 zu den <em>Non-Delivery Report (NDR) containing an error stating \"554 5.6.0 Corrupt message content\"\u00a0<\/em>Fehlern beim Versenden von Anh\u00e4ngen:<\/p>\n<blockquote><p>Microsoft<br \/>\nUsers may encounter delays or failures when sending or receiving email messages in Exchange Online<\/p>\n<p>ID: EX1027675<\/p>\n<p>Issue type: Incident<\/p>\n<p>Status<\/p>\n<p>Service Restored<\/p>\n<p>Impacted services<\/p>\n<p>Exchange Online<\/p>\n<p>Details<\/p>\n<p>Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online<\/p>\n<p>User impact: Users may have encountered delays or failures when sending or receiving email messages in Exchange Online.<\/p>\n<p>Final status: We've identified that the remaining impact relates to a separate issue which exhibits a nearly identical impact to users. We've confirmed that our fix completed in the affected environment and impact for this issue is remediated based on our internal monitoring. We'll continue investigating the root cause of the remaining impact and supplying further updates in EX1030895.<\/p>\n<p>Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may have been affected.<\/p>\n<p>Start time: Friday, March 7, 2025, at 5:30 PM UTC<\/p>\n<p>End time: Thursday, March 13, 2025, at 5:00 PM UTC<\/p>\n<p>Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that resulted in impact for a portion of service infrastructure.<\/p>\n<p>Next steps:<\/p>\n<p>&#8211; We're reviewing our service update validation procedures to detect and prevent similar issues from occurring in the future.<\/p>\n<p>This is the final update for the event.<\/p><\/blockquote>\n<p>&#8212;<\/p>\n<blockquote><p>Microsoft<br \/>\nUsers may encounter delays or failures when sending or receiving email messages in Exchange Online<\/p>\n<p>ID: EX1027675<\/p>\n<p>Issue type: Incident<\/p>\n<p>Status<\/p>\n<p>Service Degradation<\/p>\n<p>Impacted services<\/p>\n<p>Exchange Online<\/p>\n<p>Details<\/p>\n<p>Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online<\/p>\n<p>User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.<\/p>\n<p>More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating \"554 5.6.0 Corrupt message content\".<\/p>\n<p>Additionally, users may be unable to send email messages with attached files in any connection method of Exchange Online. Sending attachments as ZIP files allows the email messages to be delivered as expected, serving as a method by which to bypass the issue while we continue to investigate.<\/p>\n<p>Current status: Though we've deployed the fix to 95 percent of the affected environment, we've received continued reports of impact that indicate our fix may not have corrected this issue as expected. We've halted the fix deployment and are reviewing these reports to determine our next steps.<\/p>\n<p>Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may be affected.<\/p>\n<p>Start time: Friday, March 7, 2025, at 5:30 PM UTC<\/p>\n<p>Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.<\/p>\n<p>Next update by: Thursday, March 13, 2025, at 6:30 PM UTC<\/p><\/blockquote>\n<h2>Incident EX1030895<\/h2>\n<p>Hier der Text des Vorfalls EX1030895:<\/p>\n<blockquote><p>Microsoft<br \/>\nUsers may encounter failures when sending or receiving some email messages in Exchange Online<\/p>\n<p>ID: EX1030895<\/p>\n<p>Issue type: Advisory<\/p>\n<p>Status<\/p>\n<p>Investigating<\/p>\n<p>Impacted services<\/p>\n<p>Exchange Online<\/p>\n<p>Details<\/p>\n<p>Title: Users may encounter failures when sending or receiving some email messages in Exchange Online<\/p>\n<p>User impact: Users may encounter failures when sending or receiving some email messages in Exchange Online.<\/p>\n<p>More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating \"554 5.6.0 Corrupt message content\".<\/p>\n<p>Current status: We're reviewing Non-Delivery Reports (NDRs) gathered from impacted users to identify why users may encounter failures when sending or receiving some email messages in Exchange Online.<\/p>\n<p>Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may be affected.<\/p>\n<p>Next update by: Thursday, March 13, 2025, at 7:30 PM UTC<\/p><\/blockquote>\n<p>&#8211;<\/p>\n<blockquote><p>Microsoft<br \/>\nSome users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages<\/p>\n<p>ID: EX1030895<\/p>\n<p>Issue type: Incident<\/p>\n<p>Status<\/p>\n<p>Service Degradation<\/p>\n<p>Impacted services<\/p>\n<p>Exchange Online<\/p>\n<p>Details<\/p>\n<p>Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages<\/p>\n<p>User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.<\/p>\n<p>More info: Users may receive a Non-Delivery Report (NDR) containing an error stating \"554 5.6.0 Corrupt message content\".<\/p>\n<p>Current status: We've identified that impact is not limited to users sending IRM protected email as we previously communicated. We've updated the title, user impact, more info and scope of impact sections of this communication to reflect that new information. Our previously stated fix will continue deploying to affected infrastructure while we continue monitoring its efficacy as it progresses. Concurrently, we've shifted attention to our reproduction efforts and deeper log analysis to further isolate the cause of impact and identify new mitigation strategies.<\/p>\n<p>Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.<\/p>\n<p>Next update by: Friday, March 14, 2025, at 6:30 PM UTC<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Bei Microsofts Exchange Online gibt es ja seit Ende Februar 2025 massive Probleme. Microsoft ver\u00f6ffentlicht im Exchange Online Service Health-Dashboard auch Statusmeldungen zu diversen Vorf\u00e4llen. Ich stelle nachfolgend die Incidents EX1027675 und EX1030895 zu den Non-Delivery Report (NDR) containing an &hellip; <a href=\"https:\/\/borncity.com\/blog\/2025\/03\/15\/exchange-online-service-health-incidents-ex1027675-und-ex1030895\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7263,7862],"tags":[7211,987],"class_list":["post-309431","post","type-post","status-publish","format-standard","hentry","category-cloud","category-stoerung","tag-exchange-online","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/309431","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=309431"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/309431\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=309431"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=309431"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=309431"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}