{"id":229640,"date":"2020-03-17T17:30:06","date_gmt":"2020-03-17T16:30:06","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=229640"},"modified":"2020-03-18T10:16:36","modified_gmt":"2020-03-18T09:16:36","slug":"strung-microsoft-teams-rumpelt-16-3-2020","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2020\/03\/17\/strung-microsoft-teams-rumpelt-16-3-2020\/","title":{"rendered":"St&ouml;rung: Microsoft Teams rumpelt (16.\/17.3.2020)"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2014\/02\/OneDrive.jpg\" width=\"58\" height=\"56\" align=\"left\" \/>Bei der Cloud-L\u00f6sung Microsoft Teams hat es zum 16. M\u00e4rz 2020 wohl ziemliche Hakeleien gegeben. Die Cloud-gest\u00fctzte Collaborationsl\u00f6sung aus dem Haus Microsoft war pl\u00f6tzlich nicht mehr zu gebrauchen. <strong>Erg\u00e4nzung:<\/strong> Auch am 17. M\u00e4rz 2020 klemmt es.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg02.met.vgwort.de\/na\/1794563abbfb46e6b29cf9c20eb104ee\" alt=\"\" width=\"1\" height=\"1\" \/>Das es mit Microsofts Cloud-L\u00f6sungen w\u00f6chentlich mehrfach irgendwo hakt, l\u00e4sst sich an inzwischen zahlreichen Blog-Beitr\u00e4gen nachlesen. In Zeiten von Coronakrise und Home Office setzen m\u00f6glicherweise viele Nutzer genau auf diese Collaborationsl\u00f6sungen. Die Macher von Slack haben gerade einen Bug gefixt, der die \u00dcbernahme eines Benutzerkontos erm\u00f6glicht h\u00e4tte (siehe <a href=\"https:\/\/www.bleepingcomputer.com\/news\/security\/slack-bug-allowed-automating-account-takeover-attacks\/\" target=\"_blank\" rel=\"noopener noreferrer\">diesen Artikel<\/a> auf Bleeping Computer).<\/p>\n<p>Bei Microsoft war das zumindest gestern kein Problem, denn dort konnte man sich als Benutzer (wenn man zu den Pechv\u00f6geln geh\u00f6rte) unter Teams schlicht nicht mal mehr anmelden. Blog-Leser Daniel S. schickte mir zum gestrigen Abend eine Mail:<\/p>\n<blockquote><p>FYI<\/p>\n<p>Die MS Cloud dreht wieder komplett am Rad heute. Vermutlich steigen heute alle ins Home Office ein &#8211; ausgerechnet jetzt funktioniert kein Teams.<\/p>\n<p>Aktuell sind 7 Rot Meldungen im Admin-Portal<\/p>\n<p>Gru\u00df<\/p>\n<p>Daniel<\/p><\/blockquote>\n<p>Auf Nachfrage hat er mir noch den nachfolgenden Screenshot des Admin-Status geschickt, die eine St\u00f6rung zeigt.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" title=\"Teams-Status\" src=\"https:\/\/i.imgur.com\/KDGlOT9.jpg\" alt=\"Teams-Status\" width=\"454\" height=\"772\" \/><\/p>\n<p>Die Auflistung zeigt zwar viele gr\u00fcne H\u00e4kchen \u2013 aber das sind Problemchen, die das Support-Team im Laufe des Tages behoben hat. Erg\u00e4nzung: Gerade habe ich noch einen Status bekommen, dass es vor allem Europa betrag.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p dir=\"ltr\" lang=\"en\">Microsoft Teams went down for two hours as Europe logged in <a href=\"https:\/\/t.co\/4FHC09qnUc\">https:\/\/t.co\/4FHC09qnUc<\/a><\/p>\n<p>\u2014 Aryeh Goretsky (@goretsky) <a href=\"https:\/\/twitter.com\/goretsky\/status\/1239791442135887872?ref_src=twsrc%5Etfw\">March 17, 2020<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Martin Geu\u00df hatte es bereits zum Vormittag auf Dr. Windows als <a href=\"https:\/\/www.drwindows.de\/news\/digitalisierung-am-limit-microsoft-teams-kaempft-mit-aussetzern\" target=\"_blank\" rel=\"noopener noreferrer\">Digitalisierung am Limit: Microsoft Teams k\u00e4mpft mit Aussetzern<\/a> thematisiert. Inzwischen sollte das Problem weitgehend behoben sein. Blog-Leser Andreas P. hat mir die Statusausz\u00fcge aus dem Administrator-Dashboard geschickt:<\/p>\n<blockquote><p>-16.03.2020 18:57:54<br \/>\nTitle: Teams messaging functionality issues<br \/>\nUser Impact: Some users may be unable to send and receive messages or schedule meetings.<br \/>\nMore info: Additionally, some users may have been unable to create teams and update team memberships within the Microsoft Teams service.<br \/>\nCurrent status: After rerouting user connections, our telemetry indicates that service has been restored as of Monday, March 16, 2020, at 3:37 PM UTC. We'll continue to actively monitor the service for the next 24 hours to ensure additional impact does not occur.<br \/>\nScope of impact: This issue could have impacted any user who was served through the affected infrastructure. Our telemetry indicated that this issue only affected users hosted within Europe.<br \/>\nStart time: Monday, March 16, 2020, at 2:20 PM UTC<br \/>\nRoot cause: A downstream service experienced latency processing requests, resulting in errors within the service that processes chat functionality. We're actively determining what caused the downstream latency and putting in any corrective measures required.<br \/>\nNext update by: Tuesday, March 17, 2020, at 11:00 AM UTC<br \/>\n-16.03.2020 17:32:56<br \/>\nTitle: Teams messaging functionality issues<br \/>\nUser Impact: Some users may be unable to send and receive messages or schedule meetings.<br \/>\nMore info: Additionally, some users may be unable to create a team and update team memberships within the Microsoft Teams service.<br \/>\nCurrent status: We've identified a potential issue with the service responsible for chat functionality and we're reviewing diagnostic data to validate whether this is the source of the functionality degradation. We're continuing to reroute user connections to alternate components and have observed that the majority of users are seeing recovery.<br \/>\nScope of impact: This issue could impact any user who is served through the affected infrastructure.<br \/>\nNext update by: Monday, March 16, 2020, at 6:00 PM UTC<br \/>\n-16.03.2020 16:29:46<br \/>\nTitle: Teams messaging functionality issues<br \/>\nUser Impact: Some users may be unable to send and receive messages or schedule meetings.<br \/>\nMore info: Additionally, some users may be unable to create a team and update team memberships within the Microsoft Teams service.<br \/>\nCurrent status: We're restarting affected components and rerouting user requests to alternate systems to alleviate impact.<br \/>\nScope of impact: This issue could impact any user who is served through the affected infrastructure.<br \/>\nNext update by: Monday, March 16, 2020, at 5:00 PM UTC<br \/>\n-16.03.2020 15:42:37<br \/>\nTitle: Teams messaging functionality issues<br \/>\nUser Impact: Some users may be unable to send and receive messages or schedule meetings.<br \/>\nMore info: Additionally, some users may be unable to create a team and update team memberships within the Microsoft Teams service.<br \/>\nCurrent status: We've received reports of impact to multiple Microsoft Teams functionalities. We're reviewing system telemetry to isolate the source of the issue.<br \/>\nScope of impact: This issue could impact any user who is served through the affected infrastructure.<br \/>\nNext update by: Monday, March 16, 2020, at 3:30 PM UTC<\/p><\/blockquote>\n<p>Kommt nat\u00fcrlich zur Unzeit, wenn mehr Leute diesen Dienst nutzen m\u00f6chten. War jemand betroffen?<\/p>\n<h2>Neue St\u00f6rung zum 17. M\u00e4rz<\/h2>\n<p><strong>Erg\u00e4nzung:<\/strong> Auch am 17. M\u00e4rz 2020 klemmt es. Zumindest entnehme ich dies dem aktuellen Statusbeitrag des Service-Teams auf Twitter.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p dir=\"ltr\" lang=\"en\">We investigated and resolved an issue with the Teams chat service that affected some of our users in the Europe region. We determined this to be a caching issue within a component of our infrastructure. More details will updated under the SI# TM206556.<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1239901411795746816?ref_src=twsrc%5Etfw\">March 17, 2020<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Hier noch die Statusmeldungen vom 17. M\u00e4rz, die mit Blog-Leser Andreas P. zur Verf\u00fcgung gestellt hat.<\/p>\n<blockquote><p>-17.03.2020 14:51:53<\/p>\n<p>Title: Teams messaging functionality issues<\/p>\n<p>User Impact: Some users may have been unable to send and receive messages or schedule meetings and live events.<\/p>\n<p>More info: Additionally, some users may have been unable to create teams and update team memberships within the Microsoft Teams service.<\/p>\n<p>Current status: We connected the service to alternate, healthy infrastructure to mitigate impact for the affected users. Additionally, we applied a mitigation to address the caching issue that resulted in impact. Our investigation determined that the impact that occurred on Monday, March 16, was symptomatically the same as the impact from Tuesday, March 17, but with a different root cause. We'll publish a Post-Incident Report within five business days to provide additional context into the root cause of these problems.<\/p>\n<p>This communication will remain open to provide additional updates in the event this issue reoccurs.<\/p>\n<p>Scope of impact: Our telemetry indicated that this issue affected some users hosted within the Europe region.<\/p>\n<p>Start time: Monday, March 16, 2020, at 2:20 PM UTC<\/p>\n<p>Root cause: On Tuesday, March 17, a caching issue occurred within a component of the service that supports the messaging feature, resulting in impact.<\/p>\n<p>Root cause: On Monday, March 16, a downstream service was experiencing latency when processing requests, resulting in errors within the service that processes chat functionality. We're actively determining what caused the downstream latency and putting in any corrective measures required.<\/p>\n<p>Next update by: Wednesday, March 18, 2020, at 10:00 AM UTC<\/p>\n<p>-17.03.2020 13:12:29<\/p>\n<p>Title: Teams messaging functionality issues<\/p>\n<p>User Impact: Some users may be unable to send and receive messages or schedule meetings and live events.<\/p>\n<p>More info: Additionally, some users may be unable to create teams and update team memberships within the Microsoft Teams service.<\/p>\n<p>Current status: We've identified that a caching issue has caused the service which handles the messaging feature to become degraded. We've completed connecting the user connections to additional, healthy infrastructure and are monitoring the service while it recovers.<\/p>\n<p>Scope of impact: This issue could impact any user who is served through the affected infrastructure. Our telemetry indicates that this issue only affects users hosted within Europe.<\/p>\n<p>Start time: Monday, March 16, 2020, at 2:20 PM UTC<\/p>\n<p>Next update by: Tuesday, March 17, 2020, at 2:00 PM UTC<\/p>\n<p>-17.03.2020 10:34:23<\/p>\n<p>Title: Teams messaging functionality issues<\/p>\n<p>User Impact: Some users may be unable to send and receive messages or schedule meetings and live events.<\/p>\n<p>More info: Additionally, some users may be unable to create teams and update team memberships within the Microsoft Teams service.<\/p>\n<p>Current status: We've identified an issue with service that handles the messaging feature, which is causing impact. While we determine the underlying cause of this issue, we're connecting the user connections to additional, healthy infrastructure to mitigate impact.<\/p>\n<p>Scope of impact: This issue could impact any user who is served through the affected infrastructure. Our telemetry indicates that this issue only affects users hosted within Europe.<\/p>\n<p>Start time: Monday, March 16, 2020, at 2:20 PM UTC<\/p>\n<p>Next update by: Tuesday, March 17, 2020, at 12:00 PM UTC<\/p>\n<p>-17.03.2020 09:33:55<\/p>\n<p>Title: Teams messaging functionality issues<\/p>\n<p>User Impact: Some users may be unable to send and receive messages or schedule meetings.<\/p>\n<p>More info: Additionally, some users may be unable to create teams and update team memberships within the Microsoft Teams service.<\/p>\n<p>Current status: Our telemetry indicates that the impact related to this issue has returned. We're reviewing logs and additional service data to determine next steps.<\/p>\n<p>Scope of impact: This issue could impact any user who is served through the affected infrastructure. Our telemetry indicates that this issue only affects users hosted within Europe.<\/p>\n<p>Start time: Monday, March 16, 2020, at 2:20 PM UTC<\/p>\n<p>Next update by: Tuesday, March 17, 2020, at 11:00 AM UTC<\/p>\n<p>-17.03.2020 03:00:52<\/p>\n<p>Title: Teams messaging functionality issues<\/p>\n<p>User Impact: Some users may be unable to send and receive messages or schedule meetings.<\/p>\n<p>More info: Additionally, some users may be unable to create teams and update team memberships within the Microsoft Teams service.<\/p>\n<p>Current status: Our service monitoring and data analysis indicates the issue is resolved for the majority of users; though, we've identified that a small number of users hosted within Europe remain affected and we're working to remediate impact for these users. Furthermore, we're continuing to monitor service availability for the groups of users that seem to have been disproportionately affected by the issue to curb the potential for further impact.<\/p>\n<p>Scope of impact: This issue could impact any user who is served through the affected infrastructure. Our telemetry indicates that this issue only affects users hosted within Europe.<\/p>\n<p>Start time: Monday, March 16, 2020, at 2:20 PM UTC<\/p>\n<p>Root cause: A downstream service is experiencing latency processing requests, resulting in errors within the service that processes chat functionality. We're actively determining what caused the downstream latency and putting in any corrective measures required.<\/p>\n<p>Next update by: Tuesday, March 17, 2020, at 11:00 AM UTC<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Bei der Cloud-L\u00f6sung Microsoft Teams hat es zum 16. M\u00e4rz 2020 wohl ziemliche Hakeleien gegeben. Die Cloud-gest\u00fctzte Collaborationsl\u00f6sung aus dem Haus Microsoft war pl\u00f6tzlich nicht mehr zu gebrauchen. Erg\u00e4nzung: Auch am 17. M\u00e4rz 2020 klemmt es.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7263],"tags":[987,5595],"class_list":["post-229640","post","type-post","status-publish","format-standard","hentry","category-cloud","tag-storung","tag-teams"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/229640","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=229640"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/229640\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=229640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=229640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=229640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}