![](\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2021\/05\/Cloud-Symbol.jpg\" "\\"Cloud\\"")
Bestimmte Nutzer der Microsoft-Cloud hatten am 23. M\u00e4rz 2023 Probleme, auf die Cloud-Dienste von Microsoft 365 oder Office 365 zuzugreifen. Microsoft hat das Problem eingestanden – die Ursache ist allerdings unsch\u00f6n: Es betraf Nutzer weltweit, weil eine fehlerhafte der Geo-Location gemeldet (f\u00fcr Usbekistan) gemeldet wurde, welche den Zugang dann blockte. Der Fall zeigt einmal mehr, wie schnell ganze Regionen aus der Cloud gekickt werden k\u00f6nnen.<\/p>\n
<\/p>\n
Laut Microsoft hat sofort man damit begonnen, eine k\u00fcrzlich vorgenommene \u00c4nderung r\u00fcckg\u00e4ngig zu machen. Laut Microsoft waren auch Nutzer in Japan und den Vereinigten Staaten l\u00e4ngere Zeit betroffen. Es dauerte (gem\u00e4\u00df den Microsoft Status-Tweets) ca. 9 Stunden, bis diese \u00c4nderung \u00fcber die \"Microsoft Cloud\" komplett zur\u00fcckgerollt worden war. Obwohl ich auf Twitter beim Schreiben des Beitrag Hinweise gelesen habe, dass es immer noch Nutzer mit Problemen gibt (also nach mehr als 18 Stunden). Weitere Informationen zum Ausfall hat Microsoft im Admin Center unter MO531859 ver\u00f6ffentlicht.<\/p>\n Ich habe diesen Ausfall gestern nicht mitbekommen, aber The Register hat es im Beitrag Microsoft breaks geolocation, locking users out of Azure and M365<\/a> aufgegriffen. Ein Nutzer hatte denen einige Details zus\u00e4tzliche Details zukommen lassen. Die Microsoft Statusmeldung teilte nur mit: \"Bei einer Untergruppe von Benutzern mit geolokalisierungsbasierten Zugriffsrichtlinien kam es zu Unterbrechungen bei der Anmeldung bei Azure-Diensten.\"<\/p>\n Der Tippgeber bei The Register schrieb, dass das Chaos beim Cloud-Zugriff durch eine bereitgestellte Aktualisierung verursacht wurde, die sich auf die Geolokalisierung der Benutzer auswirkte und \"versehentlich falsche IP-Standortdaten lieferte\". Jeder Benutzer, der eine IP-basierte Richtlinie f\u00fcr den bedingten Zugriff verwendete, und mit einer falschen IP als Standort gemeldet wurde, konnte sich dann nicht mehr bei den Microsoft-Diensten anmelden.<\/p>\n Der Leser postete in obigem Bild weitere Details, die seine Kunden in Darwin, Australien, zu sehen bekamen. Dort blockierte Microsoft den Zugriff auf den Teams-Dienst, weil dessen Datenverkehr angeblich aus Taschkent, der Hauptstadt von Usbekistan, kam. Ein Nutzer merkte darauf hin an<\/a>, das es \"wenig cool sei\", den Datenverkehr von US-Nutzern \u00fcber Usbekistan zu leiten.<\/p>\n Insidern ist klar, dass \"Cloud\" f\u00fcr \"den Computer eines anderen\" steht, den dieser andere jederzeit ausschalten kann. Dann ist der Zugriff auf die Cloud halt weg – egal ob beabsichtigt und unbeabsichtigt oder auf Grund eines Hacks. In Gro\u00dfbritannien war der nationale Gesundheitsdienst (National Health Service, NHS) wohl von dieser St\u00f6rung betroffen, wie auf dieser Statusseite<\/a> gemeldet wurde. War jemand von euch von diesem Ausfall betroffen?<\/p>\n Erg\u00e4nzung:<\/strong> Andreas P. hat mir dankenswerter weise die nachfolgenden Eintr\u00e4ge aus dem Admin Center f\u00fcr den Vorfall MO531859 geschickt.<\/p>\n Published Time: 23.03.2023 18:17:30<\/p>\n Title: Users with IP-based geolocation conditional access policies may be unable to access Microsoft 365 services<\/p>\n User impact: Users with IP-based geolocation conditional access policies may have been unable to access Microsoft 365 services.<\/p>\n More info: This issue affected organizations with IP-based geolocation conditional access policies applied and may have caused tenant-wide sign-in disruptions to any Microsoft 365 service.<\/p>\n Final status: We've completed our mitigation efforts and have confirmed that reverting the offending update as well as performing traffic redirections has resolved impact to all users.<\/p>\n Scope of impact: This issue may affected any user in an organization with specific IP-based geolocation conditional access policies applied.<\/p>\n Start time: Thursday, March 23, 2023, at 3:30 AM UTC<\/p>\n End time: Thursday, March 23, 2023, at 8:33 PM UTC<\/p>\n Preliminary root cause: An update applied to a section of infrastructure responsible for regulating user geolocation caused incorrect IP location data to be provided, resulting in impact to users who have an IP-based geolocation conditional access policy.<\/p>\n Next steps: We'll publish a post-incident report within five business days.<\/p>\n Published Time: 23.03.2023 17:50:16<\/p>\n Impact to the remaining United States infrastructure has now been resolved. We're continuing to work to address the remaining impact in Japan, which is believed to be extremely low at this time.<\/p>\n This quick update is designed to give the latest information on this issue.<\/p>\n Published Time: 23.03.2023 17:00:06<\/p>\n Title: Users with geolocation-based conditional access policies may be unable to access Microsoft 365 services<\/p>\n User impact: Users with geolocation-based conditional access policies may be unable to access Microsoft 365 services.<\/p>\n Current status: Our remediation efforts are ongoing and we're closely monitoring impacted infrastructure to perform traffic redirections where necessary. At this time, we expect the majority of users are no longer experiencing impact with the exception of users in Japan and a small portion of the United States. We're investigating to determine what additional steps are required to resolve the impact for these users.<\/p>\n Scope of impact: This issue may affect any user in an organization with specific geolocation-based conditional access policies applied.<\/p>\n Start time: Thursday, March 23, 2023, at 3:00 AM UTC<\/p>\n Preliminary root cause: A recent update applied to a section of infrastructure responsible for regulating user geo-location may be inadvertently causing impact.<\/p>\n Next update by: Thursday, March 23, 2023, at 10:00 PM UTC<\/p>\n Published Time: 23.03.2023 15:01:21<\/p>\n Title: Users with geolocation-based conditional access policies may be unable to access Microsoft 365 services<\/p>\n User impact: Some users with geolocation-based conditional access policies may be unable to access Microsoft 365 services.<\/p>\n More info: This issue affects organizations with geolocation-based conditional access policies applied and may cause tenant-wide sign-in disruptions to any Microsoft 365 service.<\/p>\n Current status: We're continuing to redirect traffic from the affected regions to healthy infrastructure to mitigate impact. In parallel, we're also continuing to revert the impacting change to the most recent unaffected configuration to fully remediate the issue. As these efforts continue, our telemetry and customer reports indicate that many customers are no longer experiencing impact.<\/p>\n Scope of impact: This issue may affect any user in an organization with specific geolocation-based conditional access policies applied.<\/p>\n Start time: Thursday, March 23, 2023, at 3:00 AM UTC<\/p>\n Root cause: A recent update applied to a section of infrastructure responsible for regulating user geo-location may be inadvertently causing impact.<\/p>\n Next update by: Thursday, March 23, 2023, at 8:00 PM UTC<\/p>\n Published Time: 23.03.2023 12:49:15<\/p>\n Title: Users with geolocation-based conditional access policies may be unable to access Microsoft 365 services<\/p>\n User impact: Some users with geolocation-based conditional access policies may be unable to access Microsoft 365 services.<\/p>\n More info: This issue affects organizations with geolocation-based conditional access policies applied and may cause tenant-wide sign-in disruptions to any Microsoft 365 service.<\/p>\n Current status: We're continuing to revert the change to the most recent healthy configuration. This process is progressing as expected and some customers are experiencing remediated impact.<\/p>\n Scope of impact: This issue may affect any user in an organization with specific geolocation-based conditional access policies applied.<\/p>\n Start time: Thursday, March 23, 2023, at 3:00 AM UTC<\/p>\n Root cause: A recent update applied to a section of infrastructure responsible for regulating user geo-location may be inadvertently causing impact.<\/p>\n Next update by: Thursday, March 23, 2023, at 6:00 PM UTC<\/p>\n Published Time: 23.03.2023 12:00:50<\/p>\n Title: Some users with specific conditional access policies may be unable to access any Microsoft 365 service<\/p>\n User impact: Users with specific conditional access policies applied may be unable to access any Microsoft 365 service.<\/p>\n More info: Affected users' conditional access policies may be denying access requests because their geo-locations are read as inaccurate.<\/p>\n Current status: We're continuing to receive reports that some customers may be observing a partial improvement in the service, and some customers are experiencing remediated impact while our efforts to revert the change are progressing as expected.<\/p>\n Scope of impact: Impact is specific to users, with specific conditional access policies applied, when attempting to access any Microsoft 365 service.<\/p>\n Start time: Thursday, March 23, 2023, at 3:00 AM UTC<\/p>\n Root cause: A recent update applied to a section of infrastructure responsible for regulating user geo-location may be inadvertently causing impact.<\/p>\n Next update by: Thursday, March 23, 2023, at 4:00 PM UTC<\/p>\n Published Time: 23.03.2023 11:18:09<\/p>\n We're continuing to revert the change. This process is approximately 70% complete and some users may no longer experience impact.<\/p>\n This quick update is designed to give the latest information on this issue.<\/p>\n Published Time: 23.03.2023 10:53:48<\/p>\n Title: Some users with specific conditional access policies may be unable to access any Microsoft 365 service<\/p>\n User impact: Users with specific conditional access policies applied may be unable to access any Microsoft 365 service.<\/p>\n More info: Affected users' conditional access policies may be denying access requests because user's geo-locations are read as inaccurate.<\/p>\n Current status: We're continuing to revert the change to the most recent stable version. While this process continues, some customers may observe a partial improvement in the service. Additionally, some customers may experience remediated impact.<\/p>\n Scope of impact: Impact is specific to users, with specific conditional access policies applied, when attempting to access any Microsoft 365 service.<\/p>\n Start time: Thursday, March 23, 2023, at 3:00 AM UTC<\/p>\n Root cause: A recent update applied to a section of infrastructure responsible for regulating user geo-location may be inadvertently causing impact.<\/p>\n Next update by: Thursday, March 23, 2023, at 3:00 PM UTC<\/p>\n Published Time: 23.03.2023 10:01:26<\/p>\n We're continuing to revert the change, which is progressing as expected. As of this update, the process is approximately 25% complete.<\/p>\n This quick update is designed to give the latest information on this issue.<\/p>\n Published Time: 23.03.2023 09:11:19<\/p>\n Title: Some users with specific conditional access policies may be unable to access any Microsoft 365 service<\/p>\n User impact: Users with specific conditional access policies applied may be unable to access any Microsoft 365 service.<\/p>\n More info: Affected users' conditional access policies may be denying access requests because user's geo-locations are read as inaccurate.<\/p>\n Current status: We've identified the root cause and we're reverting the offending update to the most recent stable version. This process is approximately 20% complete as of this update, and we expect this process to complete within the next seven hours.<\/p>\n Scope of impact: Impact is specific to users, with specific conditional access policies applied, when attempting to access any Microsoft 365 service.<\/p>\n Start time: Thursday, March 23, 2023, at 3:00 AM UTC<\/p>\n Root cause: A recent update applied to a section of infrastructure responsible for regulating user geo-location may be inadvertently causing impact.<\/p>\n Next update by: Thursday, March 23, 2023, at 1:00 PM UTC<\/p>\n Published Time: 23.03.2023 06:20:42<\/p>\n Title: Some users with conditional access policies may be unable to access any Microsoft 365 service<\/p>\n User impact: Users with conditional access policies applied may be unable to access any Microsoft 365 service.<\/p>\n More info: Affected users' conditional access policies may be denying access requests due to user's geo-locations being inaccurate.<\/p>\n Current status: We've determined that a recent update applied to a section of infrastructure responsible for regulating user geo-location may be inadvertently causing impact. We're developing and validating a fix to revert the offending update to the most recent stable version, which we expect to remediate impact once complete.<\/p>\n Scope of impact: Impact is specific to some users with specific conditional access policies applied attempting to access any Microsoft 365 service.<\/p>\n Start time: Thursday, March 23, 2023, at 3:00 AM UTC<\/p>\n Root cause: A recent update applied to a section of infrastructure responsible for regulating user geo-location may be inadvertently causing impact.<\/p>\n Next update by: Thursday, March 23, 2023, at 4:30 PM UTC<\/p>\n Published Time: 23.03.2023 04:46:32<\/p>\n Title: Some users in the Asia Pacific region with conditional access policies may be unable to access any Microsoft 365 service<\/p>\n User impact: Users with conditional access policies applied may be unable to access any Microsoft 365 service.<\/p>\n More info: Affected users' conditional access policies may be failing due to user's geo-locations being inaccurate.<\/p>\n Current status: We're reviewing trends in service monitoring telemetry to isolate the underlying root cause, and formulate a plan for remediation.<\/p>\n Scope of impact: Impact is specific to some users who are served through the affected infrastructure in the Asia Pacific region.<\/p>\n Next update by: Thursday, March 23, 2023, at 10:00 AM UTC<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":" Bestimmte Nutzer der Microsoft-Cloud hatten am 23. M\u00e4rz 2023 Probleme, auf die Cloud-Dienste von Microsoft 365 oder Office 365 zuzugreifen. Microsoft hat das Problem eingestanden – die Ursache ist allerdings unsch\u00f6n: Es betraf Nutzer weltweit, weil eine fehlerhafte der Geo-Location … Weiterlesen Am gestrigen Donnerstag gab es wohl einen Vorfall in der Microsoft Cloud, der bestimmte Nutzer nach einer Konfigurations\u00e4nderung von der Verwendung der Dienste von Microsoft 365 sowie Microsoft Office 365 aussperrte. Auf Twitter<\/a> best\u00e4tigte Microsoft zum 23. M\u00e4rz 2023 Probleme mit Microsoft 365. Es hie\u00df, dass man ein Problem untersuche, bei dem Benutzer, die bestimmte Zugriffsrichtlinien anwenden, m\u00f6glicherweise nicht auf einen Microsoft 365-Dienst zugreifen k\u00f6nnen.<\/p>\n
![\"Issue](\"https:\/\/i.imgur.com\/lv3qp2a.png\" "\\"Issue")
<\/p>\nUrsache: Cloud \u00fcber IP ausgeknipst<\/h2>\n
![\"MS](\"https:\/\/i.imgur.com\/s6ylcpZ.png\" "\\"MS")
<\/a><\/p>\n![\"US](\"https:\/\/i.imgur.com\/SRonmVp.png\" "\\"US")
<\/a><\/p>\n
\n– We're continuing to monitor telemetry to ensure the service remains stable.
\n– We're reviewing why impact wasn't detected prior to the update being rolled out to prevent similar issues in the future.<\/p>\n