{"id":217588,"date":"2019-05-03T08:13:39","date_gmt":"2019-05-03T06:13:39","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=217588"},"modified":"2019-05-03T08:13:39","modified_gmt":"2019-05-03T06:13:39","slug":"sharepoint-azure-office-365-teams-am-2-mai-2019-down","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2019\/05\/03\/sharepoint-azure-office-365-teams-am-2-mai-2019-down\/","title":{"rendered":"SharePoint, Azure, Office 365, Teams am 2. Mai 2019 down"},"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\" align=\"left\" height=\"56\"\/>Am gestrigen 2. Mai 2019 scheint die Microsoft-Cloud mal wieder Schluckauf gehabt zu haben. Die Dienste f\u00fcr SharePoint, Azure, Office 365, Teams waren an diesem Tag f\u00fcr manche Nutzer nicht erreichbar. <\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg04.met.vgwort.de\/na\/6f38483b721145fcb06393da8526b79f\" width=\"1\" height=\"1\"\/>Mir ist nichts aufgefallen (hab auch keine MS-Dienste in der Zeit genutzt) und <a href=\"https:\/\/azure.microsoft.com\/en-us\/status\/\" target=\"_blank\" rel=\"noopener noreferrer\">die Statusseiten<\/a> von Microsoft meldeten auch keine St\u00f6rungen (an die History komme ich mangels Konto nicht heran). Aber \u00fcber <a href=\"https:\/\/www.askwoody.com\/2019\/sharepoint-online-in-office-365-down-azure-sql-databases-down-microsoft-dynamics-down\/\" target=\"_blank\" rel=\"noopener noreferrer\">askwoody.com<\/a> bin ich auf <a href=\"https:\/\/twitter.com\/getwired\/status\/1124045308181327893\" target=\"_blank\" rel=\"noopener noreferrer\">diesen Tweet<\/a> aufmerksam geworden. <\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p lang=\"en\" dir=\"ltr\">Each of the big 3 cloud providers should host status pages on one of the other 3&#8230;<\/p>\n<p>\u2014 Wes Miller (@getwired) <a href=\"https:\/\/twitter.com\/getwired\/status\/1124045308181327893?ref_src=twsrc%5Etfw\">2. Mai 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script> <\/p>\n<p>In <a href=\"https:\/\/www.askwoody.com\/forums\/topic\/sharepoint-online-in-office-365-down-azure-sql-databases-down-microsoft-dynamics-down\/\" target=\"_blank\" rel=\"noopener noreferrer\">den Kommentare<\/a> auf askwoody.com best\u00e4tigen Leute den Ausfall. Auch Microsoft hat wohl was best\u00e4tigt, wie ein auf askwoody.com geposteter Kommentarauszug zeigt:<\/p>\n<blockquote>\n<p>Network Connectivity  <\/p>\n<p>Starting at 19:43 UTC on 02 May 2019, customers may experience intermittent connectivity issues with Azure and other Microsoft services (including M365, Dynamics, DevOps, etc).  <\/p>\n<p>Engineers have identified the underlying root cause as a name server delegation issue with DNS resolution, affecting network connectivity and downstream impact to Compute, Storage, App Service, AAD, and SQL Database services. Mitigation has been applied, and engineering teams are clearing resolver cache to fully mitigate the issue. Most services are showing recovery.<\/p>\n<\/blockquote>\n<p>In der Diskussion witzeln Leute, dass bei Microsoft die 'linke Hand' behauptet, der Dienst sei gest\u00f6rt, w\u00e4hrend die rechte Hand 'alles im gr\u00fcnen Bereich' meldet. Ich habe dann mal den Downdetector befragt und bekam folgende Anzeige, die eine St\u00f6rung am sp\u00e4ten Abend des 2. Mai 2019 zeigt. <\/p>\n<p><img decoding=\"async\" title=\"Office 365 Downdetector 2. Mai 2019\" alt=\"Office 365 Downdetector 2. Mai 2019\" src=\"https:\/\/i.imgur.com\/s6pXP62.jpg\"\/><br \/>(Downdetector-Anzeige vom 2. Mai 2019)<\/p>\n<p>Redmond Mag best\u00e4tigt in <a href=\"https:\/\/redmondmag.com\/articles\/2019\/05\/02\/microsoft-outage-thursday-afternoon.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">diesem Artikel<\/a> den Ausfall am Donnerstagnachmittag (in den USA) und einige Nutzer in Europa in den sp\u00e4ten Abendstunden traf. Benutzern von Microsoft SharePoint, Azure, Office 365 und anderen Cloud-Diensten konnten diese f\u00fcr mindestens eine Stunde nicht nutzen.  <\/p>\n<h2>Microsoft informiert \u00fcber Twitter<\/h2>\n<\/p>\n<p>Auf Twitter haben die Microsoft-Leute den <a href=\"https:\/\/twitter.com\/MSFT365Status\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft 365 Status<\/a> und den <a href=\"https:\/\/twitter.com\/AzureSupport\" target=\"_blank\" rel=\"noopener noreferrer\">Azure Status<\/a> zeitnah best\u00e4tigt. Die Nacht gab es folgende Meldung:  <\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p lang=\"en\" dir=\"ltr\">We're aware of and investigating an issue affecting access to SharePoint and OneDrive. Further details can be found in the admin center under SP178746 and OD178975.<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1124043591452626946?ref_src=twsrc%5Etfw\">2. Mai 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script> <\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p lang=\"en\" dir=\"ltr\">We've identified and corrected a DNS configuration issue that prevented users from accessing Microsoft 365 services. Further details can be found in the admin center under SP178746, OD178975, and MO178979.<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1124063490740826133?ref_src=twsrc%5Etfw\">2. Mai 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script> <\/p>\n<p>Sp\u00e4ter kam dann die Best\u00e4tigung, dass der Fehler wohl behoben sei.<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p lang=\"en\" dir=\"ltr\">We've validated through monitoring that impact associated with SP178746, OD178975, and MO178979 has been resolved. Further updates on this incident can be found in the admin center.<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1124076212282908672?ref_src=twsrc%5Etfw\">2. Mai 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script> <\/p>\n<p>Auch der <a href=\"https:\/\/twitter.com\/AzureSupport\" target=\"_blank\" rel=\"noopener noreferrer\">Azure Support<\/a> best\u00e4tigt auf Twitter, dass man die St\u00f6rung behoben habe. Ein detaillierter Bericht (RCA) soll folgen. <\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p lang=\"en\" dir=\"ltr\">Engineers have corrected the nameserver delegation issue and confirmed the issue is mitigated. A detailed RCA will be provided within approximately 72 hours at <a href=\"https:\/\/t.co\/jESqAMYkJZ\">https:\/\/t.co\/jESqAMYkJZ<\/a><\/p>\n<p>\u2014 Azure Support (@AzureSupport) <a href=\"https:\/\/twitter.com\/AzureSupport\/status\/1124114657785122817?ref_src=twsrc%5Etfw\">3. Mai 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script> <\/p>\n<p>War irgend jemand von euch betroffen? Die Zahl der Leute, die das in Europa gemerkt haben, d\u00fcrfte wegen des Ausfalls in den Nachtstunden gering gewesen sein. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Am gestrigen 2. Mai 2019 scheint die Microsoft-Cloud mal wieder Schluckauf gehabt zu haben. Die Dienste f\u00fcr SharePoint, Azure, Office 365, Teams waren an diesem Tag f\u00fcr manche Nutzer nicht erreichbar.<\/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":[1171,672],"class_list":["post-217588","post","type-post","status-publish","format-standard","hentry","category-cloud","tag-cloud","tag-microsoft"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/217588","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=217588"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/217588\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=217588"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=217588"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=217588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}