Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)<\/p>\n
Problem-ID: EX1056704<\/p>\n
Betroffene Dienste: Exchange Online<\/p>\n
Status: Dienstbeeintr\u00e4chtigung<\/p>\n
Problemtyp: Hinweis<\/p>\n
Startzeit: 14. Apr. 2025, 02:00 MESZ<\/p>\n
Benutzerauswirkungen<\/p>\n
Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.<\/p>\n
More info<\/p>\n
Some users may receive the following error: \"HTTP 503 Service Unavailable.\"<\/p>\n
Additionally, when attempting to complete operations in the EAC, admins are returned a \"503 Service Unavailable\" error. This can potentially impact any EAC related operation, including but not limited to mailbox provisioning. Admins who can leverage PowerShell to complete these tasks can do so to avoid this issue.<\/p>\n
Scope of impact<\/p>\n
Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.<\/p>\n
Aktueller Status<\/p>\n
26. Apr. 2025, 03:55 MESZ<\/p>\n
Our previously mentioned change continues to saturate. In the interim, we're manually reducing the retry traffic for affected environments to alleviate impact to the affected API and expedite mitigation.<\/p>\n
Next update by:<\/p>\n
Samstag, 26. April 2025 um 14:00 MESZ<\/p>\n
Updateverlauf<\/p>\n
26. Apr. 2025, 01:54 MESZ<\/p>\n
We've applied a change to a portion of impacted service infrastructure that's generating high app requests and retries to the aforementioned API to reduce the number of requests and improve the overall health of the service. We're monitoring as this change saturates throughout the affected infrastructure to ensure it completes and addresses impact.<\/p>\n
25. Apr. 2025, 23:59 MESZ<\/p>\n
We suspect high app requests and retries to an API that facilitates Outlook (classic) and the EAC are resulting in the impact. While we continue our analysis of stack logs and investigation into the identified connectivity and latency issues to confirm our suspicion, we're reviewing potential options to reduce this traffic and provide relief.<\/p>\n
25. Apr. 2025, 20:25 MESZ<\/p>\n
We're continuing our review of the stack logs in parallel with our investigation into the identified connectivity and latency issues in the provisioning handler calls to progress our investigation into the underlying cause of this issue, so we can determine our next steps regarding impact remediation.<\/p>\n
25. Apr. 2025, 16:29 MESZ<\/p>\n
Our analysis of call stack logs related to the workload management module and suitability verifier in the directory layer is ongoing. We're analyzing these stack logs to identify a potential correlation in the data, to aid in identifying the root cause and help developing a mitigation plan. We're continuing to investigate connectivity issues and high latency in provisioning handler calls, and its impact on service performance.<\/p>\n
25. Apr. 2025, 14:13 MESZ<\/p>\n
We're continuing our review of call stack logs related to the workload management module and suitability verifier in the directory layer, to identify the root cause before formulating a plan for remediation. We're also analyzing connectivity issues and high latency in provisioning handler calls, and its impact on service performance.<\/p>\n
25. Apr. 2025, 10:20 MESZ<\/p>\n
Our analysis into the source of the high latency and timeout errors on the section of Exchange Online infrastructure is progressing, but is taking longer than expected due to the complexity and scope of the issue.<\/p>\n
25. Apr. 2025, 07:47 MESZ<\/p>\n
Our analysis into the source of the high latency and timeout errors on the portion of Exchange Online infrastructure continues and is taking longer than expected due to the complexity and scope of the issue.<\/p>\n
25. Apr. 2025, 05:53 MESZ<\/p>\n
We're continuing to investigate the source of the high latency and timeout errors on a portion of Exchange Online infrastructure to help with isolating the root cause.<\/p>\n
25. Apr. 2025, 03:49 MESZ<\/p>\n
We've identified high latency and timeout errors on a portion of Exchange Online infrastructure responsible for EAC and Outlook (classic) functionality. We're further investigating the source of the latency and timeout errors to help with the root cause investigation.<\/p>\n
25. Apr. 2025, 01:53 MESZ<\/p>\n
We've amended the Title, User impact, and More info sections of this communication to more fully capture the affected scenarios. We're further analyzing a portion of Exchange Online infrastructure responsible for EAC and Outlook (classic) functionality to help with understanding the root cause. Additionally, we're investigating if a possible networking issue could be contributing to the \"503 Service Unavailable\" errors to help with the underlying investigation.<\/p>\n
24. Apr. 2025, 13:25 MESZ<\/p>\n
We're continuing to proceed with further troubleshooting to rule out potential sources of impact and inform our next steps. As previously mentioned, it may take some additional time before we can locate a path to resolution.<\/p>\n
24. Apr. 2025, 05:37 MESZ<\/p>\n
Our review of the latest collected data has been inconclusive. We're proceeding with further troubleshooting to rule out potential sources of impact and inform our next steps. Due to the complexity of the issue, it may take some additional time before we can identify a path to remediation.<\/p>\n
24. Apr. 2025, 01:56 MESZ<\/p>\n
We've completed the previously mentioned configuration change to a subset of Exchange Online directory infrastructure to assist us in evaluating the impact to the admin API, and we're investigating the data collected from this change to isolate the root cause of the issue and identify a new path to remediation.<\/p>\n
24. Apr. 2025, 00:11 MESZ<\/p>\n
We're implementing a configuration change in a subset of Exchange Online directory infrastructure to test for impact to the admin API and to help us determine if a recent update to assist with onboarding virtual assistant to the Exchange admin center resulted in impact.<\/p>\n
23. Apr. 2025, 22:45 MESZ<\/p>\n
We're analyzing recent updates to a subset of directory infrastructure for Exchange Online to determine if any updates correlate with the returned 503 errors. This will help us to confirm a potential root cause and what steps we can take to resolve the issue.<\/p>\n
23. Apr. 2025, 19:17 MESZ<\/p>\n
We've confirmed that all functions within the Exchange admin center could be impacted and we've updated the \"Title\", \"User impact\" and \"More info\" sections of this communication to reflect our new understanding of the impact scenario. We're analyzing Admin API failures on a subset of directory and authentication service infrastructure, along with recent updates pertaining to the Exchange admin center, to better understand why 503 errors are returned and what steps we can take to resolve the issue.<\/p>\n
22. Apr. 2025, 18:35 MESZ<\/p>\n
We've determined that reverting the service update hasn't remedied the issue when managing mailboxes. We've isolated and are further analyzing a group of errors occurring on a subset of directory and authentication service infrastructure to help us confirm the source for this event, along with our next troubleshooting steps for remediating the impact.<\/p>\n
18. Apr. 2025, 22:22 MESZ<\/p>\n
We've identified a recent change intended to provide optimizations to our logging capabilities introduced a code issue which resulted in latency on the affected infrastructure, resulting in impact when attempting to process admins actions when managing mailboxes in the Exchange admin center. We're developing a fix for this issue which will undergo testing and validation, after which we'll deploy our fix to the impact environment. We'll provide an estimated timeline for completion of the fix deployment with our next scheduled update.<\/p>\n
18. Apr. 2025, 20:20 MESZ<\/p>\n
We suspect that a recent change may be responsible for impact. We're reviewing recent changes to identify if any may potentially be responsible for impact and determine our next steps.<\/p>\n
18. Apr. 2025, 10:46 MESZ<\/p>\n
Our investigation into understanding the source of the spike in service latency errors from the LDAP to determine the underlying root cause is ongoing.<\/p>\n
18. Apr. 2025, 06:04 MESZ<\/p>\n
We're continuing with our investigation into understanding the source of the spike in service latency errors from the LDAP to determine the underlying root cause.<\/p>\n
17. Apr. 2025, 21:59 MESZ<\/p>\n
We're continuing our investigation into the previously mentioned spike in service latency errors from the LDAP to isolate the root cause of impact and identify a path to remediation.<\/p>\n
17. Apr. 2025, 18:55 MESZ<\/p>\n
We're analyzing a spike in service latency errors from the Lightweight Directory Access Protocol (LDAP) that may point to a potential root cause and what steps we can take to resolve the issue.<\/p>\n
17. Apr. 2025, 17:26 MESZ<\/p>\n
We're continuing to analyze HAR logs provided by affected users along with spikes in service processing errors to better understand the underlying root cause and what steps we can take to address the issue.<\/p>\n
17. Apr. 2025, 15:35 MESZ<\/p>\n
Our investigation thus far into service-side logs has been inconclusive, we're analyzing HTTP Archive format (HAR) file logs provided by affected users to determine our next troubleshooting steps.<\/p>\n
17. Apr. 2025, 13:31 MESZ<\/p>\n
We've applied performance optimization actions and restarted the aforementioned section of infrastructure, however, telemetry indicates this didn't provide the expected relief and mitigation. We're continuing our investigation into service-side logs to isolate the source of the previously mentioned leak, in order to develop an effective remediation plan.<\/p>\n
16. Apr. 2025, 20:11 MESZ<\/p>\n
We've confirmed that packet loss is occurring within the call IDs provided and are analyzing them to determine the source and cause of the issue.<\/p>\n
16. Apr. 2025, 18:17 MESZ<\/p>\n
Our analysis of the provided HAR captures has identified that a portion of infrastructure that facilitates Exchange admin center mailbox management is over-encumbered due to an errant process leak, resulting in impact. We're expanding our investigation to include service-side logs to isolate the source of the leak and develop a remediation strategy.<\/p>\n
16. Apr. 2025, 17:11 MESZ<\/p>\n
We're continuing our analysis of provided HAR captures to better understand the impact scenario and determine our next steps.<\/p>\n
16. Apr. 2025, 16:50 MESZ<\/p>\n
We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"
Kurze Frage in die Runde der Blog-Leser: Mit ist gerade eine Leser-Mail von David F. zugegangen, der von einer St\u00f6rung bei Exchange Online seit dem gestrigen 22. April 2025 berichtet. David schrieb, dass man im Unternehmen seit gestern um die … Weiterlesen →<\/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-310844","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\/310844","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=310844"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/310844\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=310844"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=310844"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=310844"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Exchange](\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2022\/06\/Exchange.jpg\" "\\"Exchange")
Kurze Frage in die Runde der Blog-Leser: Mit ist gerade eine Leser-Mail von David F. zugegangen, der von einer St\u00f6rung bei Exchange Online seit dem gestrigen 22. April 2025 berichtet. David schrieb, dass man im Unternehmen seit gestern um die Mittagszeit (11-13 Uhr) keinen Zugriff auf die Postf\u00e4cher bei Exchange online mehr habe. Das betrifft alle User, sowie auch Shared Mailboxes, Ressourcen usw. in Exchange Online. Beobachtet das noch jemand?<\/p>\n![\"Exchange](\"https:\/\/i.postimg.cc\/9QQwCB8k\/image.png\")
<\/p>\n