{"id":298072,"date":"2024-08-05T22:05:00","date_gmt":"2024-08-05T20:05:00","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=298072"},"modified":"2024-08-06T00:25:49","modified_gmt":"2024-08-05T22:25:49","slug":"microsoft-365-gestrt-05-08-2024","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2024\/08\/05\/microsoft-365-gestrt-05-08-2024\/","title":{"rendered":"Microsoft 365 gestört (05.08.2024)"},"content":{"rendered":"

\"Stop[English<\/a>]Es gibt zum 5. August 2024 erneut eine St\u00f6rung bei den Microsoft 365 Features und Diensten, der wohl verschiedene Nutzer weltweit betrifft. Microsoft hat das Problem bereits unter MO851360 im Statusbereich f\u00fcr Administratoren von MS 365 best\u00e4tigt. Die Auswirkungen sind, je nach Nutzer, wohl verschieden. Manche stellen einen z\u00e4hen Zugriff auf Microsoft 365 Features und Dienste fest, andere Nutzer k\u00f6nnen diese \u00fcberhaupt nicht erreichen.<\/p>\n

<\/p>\n

Blog-Leser Andreas P. hat mir per E-Mail den Inhalt eine Mail zukommen lassen (danke daf\u00fcr), in der das Problem von Microsoft best\u00e4tigt wird.<\/p>\n

Users may be unable to access or use Microsoft 365 services and features<\/p>\n

ID: MO851360<\/p>\n

Issue type: Advisory<\/p>\n

Status<\/strong><\/p>\n

Investigating<\/p>\n

Impacted services<\/strong><\/p>\n

Microsoft 365 suite<\/p>\n

Details<\/strong><\/p>\n

Title: Users may be unable to access or use Microsoft 365 services and features
\nUser impact: Users may be unable to access or use Microsoft 365 services and features.
\nMore info: Impacted services include but may not be limited to Microsoft Teams.
\nCurrent status: We're investigating a potential issue with Microsoft 365 and checking for impact to your organization. We'll provide an update within 30 minutes.<\/p><\/blockquote>\n

Auf X wird ebenfalls auf den obigen Statuseintrag verwiesen, w\u00e4hrend die Seite mit dem Office 365-Status<\/a> keine St\u00f6rungen aufwies, als ich nachgeschaut habe.<\/p>\n

Erg\u00e4nzung:<\/strong> Die Kollegen von Bleeping Computer berichten hier<\/a>, dass die St\u00f6rung um\u00a0 18:22 UTC (19:22 Uhr MEZ) begonnen habe und \u00fcber zwei Stunden dauerte. In der Zeit seien einige Dienste in Nord- und S\u00fcdamerika nicht erreichbar gewesen. In der Azure Status-History findet sich diese Information.<\/p>\n

Between 18:22 and 19:49 UTC on 5 August 2024, a subset of customers experienced intermittent connection errors, timeouts, or latency while connecting to Microsoft services that leverage Azure Front Door (AFD), as a result of an issue that impacted multiple geographies. The issue was limited to internal Microsoft services hosted on AFD, and did not impact external commercial customers using AFD.<\/p>\n

What do we know so far?<\/strong><\/p>\n

We engaged several teams to investigate, and determined that the impact was caused by a recent configuration change made by an internal service team that uses AFD. Once that change was understood as the trigger event, we initiated a rollback of the configuration change which fully mitigated all customer impact.<\/p>\n

How did we respond?<\/strong><\/p>\n