Kurze Frage in die Runde der Blog-Leser: Mit ist gerade eine Leser-Mail von David F. zugegangen, der von einer Störung 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ächer bei Exchange online mehr habe. Das betrifft alle User, sowie auch Shared Mailboxes, Ressourcen usw. in Exchange Online. Beobachtet das noch jemand?
Anzeige
Nachtrag: Der Betroffene hat sich zum 24. April 2024 gemeldet und schrieb: "Die Kommentare haben dann die Lösung gebracht. Heute früh funktioniert es für uns wieder." Laut Störungs-Portal besteht das Problem aber weiterhin:
Current status Apr 24, 2025, 5:37 AM GMT+2
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.
Next update by: Thursday, April 24, 2025 at 1:30 PM GMT+2
Admins may be unable to utilize the Exchange admin center and are returned a 503 error
Issue ID: EX1056704
Affected services: Exchange Online
Status: Service degradation
Issue type: Advisory
Start time: Apr 2, 2025, 6:29 AM GMT+2
More info
Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
When attempting to complete operations in the Exchange admin center, users are returned a 503 "Service Unavailable" error.
Scope of impact
Any admin attempting to manage mailboxes in the Exchange admin center may be affected.
Andreas P. hat sich per Mail zum 27. April 2025 gemeldet und obigen Screenshot geschickt. Dazu folgende Original-Meldung:
Admins can't manage mailboxes in the Exchange admin center and receive an error message
ID: EX1056704
Issue type: Advisory
Status: Service Degradation
Impacted services: Exchange Online
Details
Title: Admins can't manage mailboxes in the Exchange admin center and receive an error messageUser impact: Admins can't manage mailboxes in the Exchange admin center and receive an error message.
More info: Within the provided HTTP Archive (HAR) trace, the error message states "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Current status: 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.
Scope of impact: Your organization is impacted by this event, and all admins attempting to manage mailboxes in the Exchange admin center are affected.
Next update by: Friday, April 18, 2025, at 8:30 PM UTC
Andreas ergänzte: Im Admin Center gibt es noch viel mehr und es ist nicht nur ein Problem mit dem Exchange Admin Center. Probleme mit Outlook im Online Mode kann ja lustig werden …
Anzeige
Users may be unable to run Outlook (classic) in online mode and admins unable to utilize the Exchange admin center (EAC)
Problem-ID: EX1056704
Betroffene Dienste: Exchange Online
Status: Dienstbeeinträchtigung
Problemtyp: Hinweis
Startzeit: 14. Apr. 2025, 02:00 MESZ
Benutzerauswirkungen
Users may be unable to run Outlook (classic) in online mode and admins may be unable to utilize the EAC.
More info
Some users may receive the following error: "HTTP 503 Service Unavailable."
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.
Scope of impact
Any user who attempts to start Outlook (classic) in online mode or any admin utilizing the EAC may be impacted by this event.
Aktueller Status
26. Apr. 2025, 03:55 MESZ
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.
Next update by:
Samstag, 26. April 2025 um 14:00 MESZ
Updateverlauf
26. Apr. 2025, 01:54 MESZ
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.
25. Apr. 2025, 23:59 MESZ
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.
25. Apr. 2025, 20:25 MESZ
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.
25. Apr. 2025, 16:29 MESZ
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.
25. Apr. 2025, 14:13 MESZ
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.
25. Apr. 2025, 10:20 MESZ
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.
25. Apr. 2025, 07:47 MESZ
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.
25. Apr. 2025, 05:53 MESZ
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.
25. Apr. 2025, 03:49 MESZ
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.
25. Apr. 2025, 01:53 MESZ
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.
24. Apr. 2025, 13:25 MESZ
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.
24. Apr. 2025, 05:37 MESZ
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.
24. Apr. 2025, 01:56 MESZ
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.
24. Apr. 2025, 00:11 MESZ
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.
23. Apr. 2025, 22:45 MESZ
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.
23. Apr. 2025, 19:17 MESZ
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.
22. Apr. 2025, 18:35 MESZ
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.
18. Apr. 2025, 22:22 MESZ
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.
18. Apr. 2025, 20:20 MESZ
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.
18. Apr. 2025, 10:46 MESZ
Our investigation into understanding the source of the spike in service latency errors from the LDAP to determine the underlying root cause is ongoing.
18. Apr. 2025, 06:04 MESZ
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.
17. Apr. 2025, 21:59 MESZ
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.
17. Apr. 2025, 18:55 MESZ
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.
17. Apr. 2025, 17:26 MESZ
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.
17. Apr. 2025, 15:35 MESZ
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.
17. Apr. 2025, 13:31 MESZ
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.
16. Apr. 2025, 20:11 MESZ
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.
16. Apr. 2025, 18:17 MESZ
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.
16. Apr. 2025, 17:11 MESZ
We're continuing our analysis of provided HAR captures to better understand the impact scenario and determine our next steps.
16. Apr. 2025, 16:50 MESZ
We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
Anzeige
c'mon .. das geht besser .. wir ITler brauchen mehr Infos ..
Hat jemand am DNS oder an der Firewall gespielt?
Was genau ist zu der Zeit passiert?
Funktioniert der Zugriff per OWA und handelt es sich nur um ein lokales Problem?
Fragen über Fragen ;-) Danke im voraus für die Antworten.
PS: Nein, wir haben keine Probs in der Firma.
Okay, ich merke schon ich habe mein Problem nicht gut genug beschrieben!
Die Postfächer selbst funktionieren ohne Störung. Nur die Verwaltung der Postfächer in Exchange Online ist nicht mehr möglich. Schon das anzeigen der Postfächer (als globaler Admin) bleibt ohne Ergebnis.
Im 365 Admin Portal sind weiterhin alle User / Postfächer verfügbar und können darüber, in geringerem Umfang bearbeitet werden.
An Einstellungen wurde nichts geändert. Ich konnte mir das Problem nur mit einer Störung bei Microsoft erklären, weshalb ich die Email an den Blog schickte.
es gibt einen Service Health Eintrag dazu
Issue ID: EX1056704
"Admins can't manage mailboxes in the Exchange admin center and receive an error message"
Danke an alle für die Hilfe. Heute funktioniert unsere Umgebung wieder, laut Portal besteht das Problem aber weiterhin:
Current status
Apr 24, 2025, 5:37 AM GMT+2
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.
Next update by:
Thursday, April 24, 2025 at 1:30 PM GMT+2
Es gibt eine Störungsmeldung dazu im Admin-Center, vielleicht hilft das ja: Administratoren können keine Postfächer im Exchange Admin Center verwalten und erhalten eine Fehlermeldung
Problem-ID: EX1056704
Betroffene Dienste: Exchange Online
Status: Dienstbeeinträchtigung
Problemtyp: Hinweis
Startzeit: 2. Apr. 2025, 06:29 MESZ
Mehr Info
Innerhalb der bereitgestellten HTTP-Archiv-Ablaufverfolgung (HAR) lautet die Fehlermeldung "Parsing of Response Content Failed in Api OperationsParsing of Response Content Failed in Api Operations"
Umfang der Auswirkungen
Jeder Administrator, der versucht, Postfächer im Exchange Admin Center zu verwalten, kann betroffen sein.
Aktueller Status
22. Apr. 2025, 18:35 MESZ
Wir haben festgestellt, dass das Problem beim Verwalten von Postfächern durch das Zurücksetzen des Dienstupdates nicht behoben wurde. Wir haben eine Gruppe von Fehlern, die in einer Teilmenge der Verzeichnis- und Authentifizierungsdienstinfrastruktur auftreten, isoliert und analysieren sie weiter, um die Ursache für dieses Ereignis zu bestätigen, zusammen mit unseren nächsten Schritten zur Fehlerbehebung zur Behebung der Auswirkungen.
Nächste Aktualisierung von:
Mittwoch, 23. April 2025, um 17:30 Uhr UTC
Danke – ich komme (mangels Konto) leider nicht auf das Admin Center drauf
Issue ID: EX1056704
Admins can't manage mailboxes in the Exchange admin center and receive an error message
Just heute Vormittag habe ich den Anruf von einem Mitarbeiter eines ehm. Kunden erhalten, der vorsichtig anfühlen wollte, ob ich wieder Support übernehmen wöllte. Ich könnte mir vorstellen, diese oder eine andere aktuelle Störung bei Emails war der finale Trigger.
Kurz vor Corona haben sich unsere Wege einvernehmlich getrennt. Man wollte unbedingt zur Microsoft Cloud und O364 ziehen, den Microsoft Way also, ich genau nicht.
C'est la vie – ich habe lachend abgewunken…
Dieses geplänkel nervt so….
Es wurde alles gesagt Problem-ID: EX1056704 – alles andere können sich Admins selbst zusammen reimen.
Aber ich kann auch bei jeder Gelegenheit von mir behaupten was für ein Crazy genialer Typ ich bin.
Als würde eine Freie Autowerkstatt sich gegen VW auflehnen und meinen SIE sind so toll sie kümmern sich nicht mehr um VW – man macht nur noch was einem gefällt und zusagt.
Die meisten hier sind sicher noch in der freien Wildbahn tätig, in der nicht nur der IT'ler entscheidet was die Firmen benutzen wollen & müssen.
Du scheinst ein Problem zu haben… lass Dir helfen…
Naja, den Support bei einer Migration zu OnPremise könnte man ja machen ;-)
Ansonsten sehe ich das ziemlich gleich, wobei, vor Corona wars gefühlt nicht so schlimm. Aber wer jetzt noch nach dem Masterschlüsseln und den Dauerproblemen da in die Cloud geht, der muss dann halt sehen, wie er zurecht kommt.
Ich warte ja noch darauf, dass sich Trump am Datenschutzabkommen vergreift. DANN gehts richtig ab.
Aber als M$-prostituiertes Unternehmen kann man die Kunden besser über den Tisch ziehen und fett abkassieren :-) Spam Schutz dazu kaufen, Backup dazu kaufen. Klar – alles Abo pro Kopf / Monat.
Wer will schon gute Lösungen die dazu noch weniger kosten.
Ich hatte bei einigen wenigen Benutzern (inkl. mir) auch einen Disconnect bei Outlook (classic client). Nach einem Neustart von Outlook hat es sich wieder verbunden. Ich habe auch in den letzten Tagen keine Änderungen an Firewall, DNS, Firmwareupdates, usw. getätigt.
Ja, Problem ist bei Microsoft seit 02. April bekannt. Problem-ID: EX1056704
Leider sehr suboptimal.
Sind auch seit gestern betroffen.
Mit Outlook New wäre das nicht passiert.
Gibt bei uns hin und wieder beim Reporting Fehler wie:
"||The database 'EURPR04DG559-db151' to be accessed on server 'am9pr04mb8940.eurprd04.prod.outlook.com' is not mounted or is not available.
A server side error has occurred because of which the operation could not be completed. Please try again after some time. If the problem still persists, please reach out to MS support."
Die hatten wir vor einigen Tagen noch nicht.
Habe in OWA immer wieder die Meldung einzelne Mails können nicht geladen werden. Seit heute.