{"id":227780,"date":"2020-02-03T16:42:24","date_gmt":"2020-02-03T15:42:24","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=227780"},"modified":"2021-09-25T23:50:25","modified_gmt":"2021-09-25T21:50:25","slug":"ms-teams-wegen-zertifikatsfehler-down-3-2-2020","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2020\/02\/03\/ms-teams-wegen-zertifikatsfehler-down-3-2-2020\/","title":{"rendered":"MS Teams wegen Zertifikatsfehler down (3.2.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\" \/>[<a href=\"https:\/\/borncity.com\/win\/2020\/02\/03\/ms-teams-due-to-certificate-failure-down-feb-3-2020\/\" target=\"_blank\" rel=\"noopener noreferrer\">English<\/a>]Die 'Profis von Microsoft' sind gerade (mal wieder) dabei, einen ihrer Onlinedienste zu flicken. Microsoft Teams ist wegen eines Zertifikatsfehlers down.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg05.met.vgwort.de\/na\/bb2ae70cbaa74297811df2f84232357f\" alt=\"\" width=\"1\" height=\"1\" \/>Erst kein Gl\u00fcck und dann kommt Pech hinzu \u2013 ging mir gerade durch den Kopf, als ich auf die neueste St\u00f6rung aufmerksam wurde. Am 31. Januar 2020 hatten Nutzer von Microsoft Onlinediensten bereits unter St\u00f6rungen <a href=\"https:\/\/borncity.com\/blog\/2020\/01\/31\/strung-bei-microsoft-365-31-1-2020\/\" target=\"_blank\" rel=\"noopener noreferrer\">zu leiden<\/a> \u2013 Ursache war der Brexit. Vor lauter Begeisterung hat sich ein Internet-Anbieter, die British Telecom, einen Internet-Ausfall geg\u00f6nnt. Hat blo\u00df einige Briten getroffen, u.a. die Kunden einer britischen Bausparkasse, die dann weder Miete noch Rechnungen bezahlen konnten (das hatte aber nix mit Teams zu tun). Kann ja mal passieren.<\/p>\n<p>Blog-Leser Andreas P. informierte mich Samstag, den 1. Februar 2020, dann \u00fcber <a href=\"https:\/\/borncity.com\/blog\/2020\/02\/01\/strung-bei-microsoft-365-31-1-2020-2\/\" target=\"_blank\" rel=\"noopener noreferrer\">die noch andauernde St\u00f6rung<\/a> \u2013 folgende Grafik zeigte den Status:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" title=\"Microsoft 365 St\u00f6rung 1.2.2020\" src=\"https:\/\/i.imgur.com\/ln9yCt0.jpg\" alt=\"Microsoft 365 St\u00f6rung 1.2.2020\" width=\"367\" height=\"775\" \/><\/p>\n<p>Seit Freitag Nacht 1:00 Uhr war auch Deutschland betroffen \u2013 gut, am Wochenende arbeitet niemand, da ist 'Papi zuhause und bespasst die Kits'.<\/p>\n<h2>Microsoft Teams ausgefallen<\/h2>\n<p>Die letzten Tage sind mir dann auf Twitter die vielen Tweets zum <a href=\"https:\/\/twitter.com\/nicolenders\/status\/1221087877016227840\" target=\"_blank\" rel=\"noopener noreferrer\">Teamscommunityday<\/a> am 28.1.2020 aufgefallen. Nun gut, der ist vorbei und heute geht es zur\u00fcck in die Niederungen der Praxis. Blog-Leser Daniel S. <a href=\"https:\/\/borncity.com\/blog\/2020\/02\/01\/strung-bei-microsoft-365-31-1-2020-2\/#comment-84369\" target=\"_blank\" rel=\"noopener noreferrer\">holt uns<\/a> auf den Boden der Tatsachen zur\u00fcck.<\/p>\n<blockquote><p>Jetzt ist grad Microsoft Teams in die Binsen.<\/p>\n<p>TM202916<br \/>\nTitle: Can't access Microsoft Teams<\/p>\n<p>User Impact: Users may be unable to access Microsoft Teams.<\/p>\n<p>Current status: We're investigating an issue where users may be unable to access Microsoft Teams. We're reviewing systems data to determine the cause of the issue.<\/p>\n<p>Scope of impact: This issue may potentially affect any of your users attempting to access Microsoft Teams.<\/p>\n<p>Next update by: Monday, February 3, 2020, 4:30 PM (3:30 PM UTC)<\/p><\/blockquote>\n<p>Die Jungs und M\u00e4dels vom Microsoft 365 Status haben das auch schon brav auf Twitter best\u00e4tigt.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p dir=\"ltr\" lang=\"en\">We've determined that an authentication certificate has expired causing, users to have issues using the service. We're developing a fix to apply a new certificate to the service which will remediate impact. Further updates can be found under TM202916 in the admin center.<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1224351597624537088?ref_src=twsrc%5Etfw\">February 3, 2020<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p><a href=\"https:\/\/web.archive.org\/web\/20210917223010\/https:\/\/downdetector.com\/status\/teams\/\" target=\"_blank\" rel=\"noopener noreferrer\">Downdetector.com<\/a> oder <a href=\"https:\/\/web.archive.org\/web\/20210918202129\/https:\/\/xn--allestrungen-9ib.de\/stoerung\/teams\/\" target=\"_blank\" rel=\"noopener noreferrer\">allestoerungen.de<\/a> melden den Ausfall seit 14:40. Die Ursache ist ein Zertifikatsfehler. Puh, was ein Gl\u00fcck, dass es Twitter und E-Mail gibt \u2013 nicht auszudenken, wenn man wieder arbeiten m\u00fcsste, weil diese ganzen Helferlein nicht mehr funktionieren. D\u00fcrfte aber wohl bald behoben sein. Irgend jemand sonst noch betroffen?<\/p>\n<blockquote class=\"twitter-tweet\">\n<p dir=\"ltr\" lang=\"de\">In MS Teams gibt es viele gute Dinge zu entdecken, die einem das t\u00e4gliche Leben leichter machen k\u00f6nnen. Eines dieser Dinge sind z.B. Bots.<\/p>\n<p>Bots sind &#8211; und daher kommt der Name &#8211; wie kleine Roboter. Auf englisch Robots. Abgek\u00fcrzt Bots.Einer <a href=\"https:\/\/twitter.com\/hashtag\/Bot?src=hash&amp;ref_src=twsrc%5Etfw\">#Bot<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/Micro?src=hash&amp;ref_src=twsrc%5Etfw\">#Micro<\/a> <a href=\"https:\/\/t.co\/QdQp7XNrta\">https:\/\/t.co\/QdQp7XNrta<\/a> <a href=\"https:\/\/t.co\/RDEHdUJ9yn\">pic.twitter.com\/RDEHdUJ9yn<\/a><\/p>\n<p>\u2014 mso365.cloud (@Mso365Cloud) <a href=\"https:\/\/twitter.com\/Mso365Cloud\/status\/1223610529442344965?ref_src=twsrc%5Etfw\">February 1, 2020<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>PS: Wenn Teams wieder online ist \u2013 da gibt es (laut mso365.cloud) doch 'viele gute Dinge' zu entdecken (siehe obiger Tweet). Na denne.<\/p>\n<p><strong>Erg\u00e4nzung<\/strong>: Golem hat inzwischen die Zertifikatsgeschichte <a href=\"https:\/\/www.golem.de\/news\/teams-ausfall-microsoft-vergisst-zertifikat-zu-verlaengern-2002-146428.html\" target=\"_blank\" rel=\"noopener noreferrer\">hier aufgegriffen<\/a>. Der Part zum Lachen: Microsoft hat wohl Geld in die Hand genommen, um <a href=\"https:\/\/www.theverge.com\/2020\/1\/17\/21070838\/microsoft-teams-tv-commercial-ad-nfl-playoffs-slack-competition\" target=\"_blank\" rel=\"noopener noreferrer\">Werbung bei den NFL play offs<\/a> in den USA f\u00fcr Teams zu schalten. Und dann vergisst man, ein wichtiges Sicherheitszertifikat zu aktualisieren. Passt.<\/p>\n<p>Und hier noch die Logs, die mir Blog-Leser Andreas P. zur Verf\u00fcgung gestellt hat (danke).<\/p>\n<p>-03.02.2020 22:16:50<\/p>\n<p>Title: Can't access Microsoft Teams<\/p>\n<p>User Impact: Users may have been unable to access Microsoft Teams.<\/p>\n<p>More info: Reports of impact to other Teams features such as chat history visibility and Auto Attendant functionality were related to this authentication issue.<\/p>\n<p>Final status: Our telemetry indicates the service largely recovered around 4:30 PM UTC after the fix to an authentication certificate was deployed across the global environment. Following this remediation action, we identified and resolved some residual impact for users hosted in North America and Northern Europe regions, by performing targeted component restarts and redirecting a portion of traffic.<\/p>\n<p>Scope of impact: This issue may have impacted any of your users attempting to access Microsoft Teams. While we were performing remediation actions, residual impact to Teams features including chats, team and channel access, calendar access, and Teams calls may have been observed by users hosted in North America and North Europe.<\/p>\n<p>Start time: Monday, February 3, 2020, at 1:44 PM UTC<\/p>\n<p>End time: Monday, February 3, 2020, at 8:30 PM UTC<\/p>\n<p>Root cause: An authentication certificate expired, which impacted any user with an expired authentication token or any user trying to login and authenticate from a logged out state.<\/p>\n<p>Next steps:<br \/>\nWe're reviewing our authentication certificate deployment and provisioning procedures to help prevent similar problems in the future.<\/p>\n<p>We'll produce a post-incident report within five business days.<\/p>\n<p>-03.02.2020 21:06:25<\/p>\n<p>Title: Can't access Microsoft Teams<\/p>\n<p>User Impact: Users may be unable to access Microsoft Teams.<\/p>\n<p>More info: We confirmed that reports of impact to other Teams features such as chat history visibility and Auto Attendant functionality are related to this authorization issue.<\/p>\n<p>Current status: Our telemetry continues to indicate the service has largely recovered; however we're seeing residual impact in some specific regions. To fully remediate the issue, we're moving select traffic to alternative infrastructure and continuing to perform targeted component restarts. We've previously deployed the new authentication certificate to mitigate impact.<\/p>\n<p>Scope of impact: This issue may impact any of your users attempting to access Microsoft Teams including chats, team and channel access, calendar access, and Teams calls. Residual impact may be observed by users hosted in North America and North Europe.<\/p>\n<p>Next update by: Monday, February 3, 2020, at 10:00 PM UTC<\/p>\n<p>-03.02.2020 20:02:26<\/p>\n<p>Title: Can't access Microsoft Teams<\/p>\n<p>User Impact: Users may be unable to access Microsoft Teams.<\/p>\n<p>More info: We confirmed that reports of impact to other Teams features such as chat history visibility and Auto Attendant functionality would have been related to this authorization issue.<\/p>\n<p>Current status: We've deployed the new authentication certificate to mitigate impact and continue to perform targeted component restarts across our infrastructure to ensure the fix is applied to all affected customer environments.<\/p>\n<p>Scope of impact: This issue may impact any of your users attempting to access Microsoft Teams including chats, team and channel access, calendar access, and Teams calls.<\/p>\n<p>Next update by: Monday, February 3, 2020, at 8:00 PM UTC<\/p>\n<p>-03.02.2020 18:31:11<\/p>\n<p>Title: Can't access Microsoft Teams<\/p>\n<p>User Impact: Users may be unable to access Microsoft Teams.<\/p>\n<p>Current status: We've deployed the new authentication certificate to mitigate impact. We're currently performing targeted component restarts across our infrastructure to ensure the fix is applied to all affected customer environments. Additionally, we're investigating reports of impact to other Teams features such as chat history visibility and Auto Attendant functionality that may arise as our fix propagates.<\/p>\n<p>Scope of impact: This issue may impact any of your users attempting to access Microsoft Teams including chats, team and channel access, calendar access, and Teams calls.<\/p>\n<p>Start time: Monday, February 3, 2020, at 1:15 PM UTC<\/p>\n<p>Root cause: An authentication certificate expired, impacting any user with an expired authentication token or any user trying to login and authenticate from a logged out state.<\/p>\n<p>Next update by: Monday, February 3, 2020, at 7:00 PM UTC<\/p>\n<p>-03.02.2020 16:58:02<\/p>\n<p>Title: Can't access Microsoft Teams<\/p>\n<p>User Impact: Users may be unable to access Microsoft Teams.<\/p>\n<p>Current status: We've deployed the fix to roll out a new authentication certificate, which has completed. We're monitoring the service, however, affected users should start to see recovery in the next hour.<\/p>\n<p>Scope of impact: This issue may potentially affect any of your users attempting to access Microsoft Teams.<\/p>\n<p>Start time: Monday, February 3, 2020, at 1:15 PM UTC<\/p>\n<p>Root cause: An authentication certificate has expired causing users who have logged out and those that are still logged in to have issue using the service.<\/p>\n<p>Next update by: Monday, February 3, 2020, at 5:30 PM UTC<\/p>\n<p>-03.02.2020 16:03:33<\/p>\n<p>Title: Can't access Microsoft Teams<\/p>\n<p>User Impact: Users may be unable to access Microsoft Teams.<\/p>\n<p>Current status: We've determined that an authentication certificate has expired causing users who have logged out and those that are still logged in to have issue using the service. We're developing a fix to apply a new authentication certificate to the service which will remediate impact.<\/p>\n<p>Scope of impact: This issue may potentially affect any of your users attempting to access Microsoft Teams.<\/p>\n<p>Start time: Monday, February 3, 2020, at 1:15 PM UTC<\/p>\n<p>Root cause: An authentication certificate has expired causing users who have logged out and those that are still logged in to have issue using the service.<\/p>\n<p>Next update by: Monday, February 3, 2020, at 4:30 PM UTC<\/p>\n<p>-03.02.2020 15:13:18<\/p>\n<p>Title: Can't access Microsoft Teams<\/p>\n<p>User Impact: Users may be unable to access Microsoft Teams.<\/p>\n<p>Current status: We're investigating an issue where users may be unable to access Microsoft Teams. We're reviewing systems data to determine the cause of the issue.<\/p>\n<p>Scope of impact: This issue may potentially affect any of your users attempting to access Microsoft Teams.<\/p>\n<p>Next update by: Monday, February 3, 2020, at 3:30 PM UTC<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[English]Die 'Profis von Microsoft' sind gerade (mal wieder) dabei, einen ihrer Onlinedienste zu flicken. Microsoft Teams ist wegen eines Zertifikatsfehlers down.<\/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-227780","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\/227780","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=227780"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/227780\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=227780"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=227780"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=227780"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}