{"id":225126,"date":"2019-11-21T20:02:51","date_gmt":"2019-11-21T19:02:51","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=225126"},"modified":"2022-03-17T12:54:03","modified_gmt":"2022-03-17T11:54:03","slug":"microsoft-365-strung-21-11-2019","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2019\/11\/21\/microsoft-365-strung-21-11-2019\/","title":{"rendered":"Microsoft 365 St&ouml;rung (21.11.2019)"},"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\"\/>Kurze Information f\u00fcr Nutzer von Microsoft 365-Cloud-Diensten. Aktuell gibt es mal wieder eine St\u00f6rung bei diesen Diensten, wie ich Statusmeldung von Microsoft entnehme.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg01.met.vgwort.de\/na\/9c6a3316b51f4d09b89cc1d90aa83f5f\" width=\"1\" height=\"1\"\/>Ich bin gerade auf Twitter auf den brandaktuellen Post von @MSFT365Status zum 21.11.2019 gesto\u00dfen. Die Leute untersuchen St\u00f6rungen, die Fehler beim Zugriff auf SharePoint Online oder OneDrive for Business ergeben.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">We're investigating an issue in which users may be experiencing intermittent delays or errors when attempting to access SharePoint Online or OneDrive for Business. Additional details can be found in the admin center under SP196346 and OD196347.<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1197586371570884608?ref_src=twsrc%5Etfw\">November 21, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script> <\/p>\n<p>Die <a href=\"https:\/\/status.office365.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">Statusseite f\u00fcr Office365.com<\/a> meldet bereits seit Tagen St\u00f6rungen, die aktuell arg ansteigen.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" title=\"Microsoft 365 St&ouml;rung (21.11.2019)\" alt=\"Microsoft 365 St&ouml;rung (21.11.2019)\" src=\"https:\/\/i.imgur.com\/TjZi93E.jpg\" width=\"641\" height=\"559\"\/><br \/>(Microsoft 365 St\u00f6rung (21.11.2019))<\/p>\n<p>Blog-Leser Andreas hat mir parallel dazu (dankenswerter Weise) per Mail folgende Statusinformationen zukommen lassen. Da geht das volle Programm ab, SharePoint, OneDrive; PowerBI und all die sch\u00f6nen Cloud-Leckereien sind nun Pustekuchen. <\/p>\n<blockquote>\n<p>-21.11.2019 18:52:27<br \/>Title: Delays or problems loading SharePoint Online sites<br \/>User Impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites.<br \/>Current status: We're working to connect the service to an alternate infrastructure as a potential mitigation action. Additionally, we're working to test for and isolate a potential cause of this impact.<br \/>Scope of impact: This issue could potentially affect any user intermittently when attempting to access SharePoint Online sites.<br \/>Start time: Thursday, November 21, 2019, at 2:45 PM UTC<br \/>Next update by: Thursday, November 21, 2019, at 8:00 PM UTC<\/p>\n<p>-21.11.2019 17:07:11<br \/>Title: Delays or problems loading SharePoint Online sites<br \/>User Impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites.<br \/>Current status: We're reviewing available diagnostic data, as well as traffic prioritization within the potentially affected SharePoint Online infrastructure, to isolate the cause of this impact.<br \/>Scope of impact: This issue could potentially affect any user intermittently when attempting to access SharePoint Online sites.<br \/>Next update by: Thursday, November 21, 2019, at 6:00 PM UTC<\/p>\n<p>-21.11.2019 16:41:29<br \/>Title: Delays or problems loading SharePoint Online sites<br \/>User impact: Users may experience intermittent delays or navigation errors when accessing SharePoint sites.<br \/>Current Status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.<\/p>\n<p>-21.11.2019 18:00:58<br \/>Title: Can't run Client Side Object Model (CSOM) and Application Programming Interface (API) scripts<br \/>User Impact: User impact: Users may intermittently encounter 500 errors within multiple services or features that leverage CSOMs or APIs.<br \/>More info: Users may notice impact if they're using services or features that leverage CSOMs or APIs.<br \/>Specifically, Power BI, Microsoft Teams, SharePoint Online and OneDrive for Business are affected:<br \/>-Power BI users may see HTTP 500 errors when they have a scheduled refresh.<br \/>-Microsoft Teams users may see HTTP 500 errors when attempting to open their files.<br \/>-OneDrive for Business users may see HTTP 500 errors when refreshing or syncing files.<br \/>-SharePoint Online users may see a 500 error or \"Internal Server Error\" when leveraging SharePoint Online APIs.<br \/>Current status: We're continuing to debug the recently deployed build in an effort to isolate which code string within the build is causing the experienced behavior. We're gathering additional stack traces for further review and to assist in our troubleshooting steps.<br \/>Scope of impact: This issue may affect any users attempting to run CSOM and API call scripts.<br \/>Next update by: Thursday, November 21, 2019, at 7:30 PM UTC<\/p>\n<p>-21.11.2019 16:32:55<br \/>Title: Can't run Client Side Object Model (CSOM) and Application Programming Interface (API) scripts<br \/>User Impact: Users may intermittently be unable to run CSOM and API call scripts within multiple services or features.<br \/>More info: Services which are impacted may include, but are not limited to, Power BI and OneDrive for Business. <br \/>Current status: We've gathered detailed logging forensics from the components producing the error. We're debugging the source code which is generating the error messages to determine the next troubleshooting steps.&nbsp; <br \/>Scope of impact: This issue may affect any users attempting to run CSOM and API call scripts.&nbsp;&nbsp; <br \/>Next update by: Thursday, November 21, 2019, at 5:30 PM UTC<\/p>\n<p>-21.11.2019 14:31:18<br \/>Title: Can't run Client Side Object Model (CSOM) and Application Programming Interface (API) scripts<br \/>User Impact: Users may intermittently be unable to run CSOM and API call scripts within multiple services or features.<br \/>Current status: We've identified a potential service update which may be the source of the impact. We're reviewing the specific configuration and code changes within the update to isolate the cause of the issue.&nbsp; <br \/>Scope of impact: This issue may affect any users attempting to run CSOM and API call scripts.&nbsp;&nbsp; <br \/>Next update by: Thursday, November 21, 2019, at 3:30 PM UTC <\/p>\n<p>-21.11.2019 13:46:56<br \/>Title: Can't run Client Side Object Model (CSOM) and Application Programming Interface (API) scripts<br \/>User Impact: Users may intermittently be unable to run CSOM and API call scripts within multiple services or features.<br \/>Current status: We're received reports of an issue with Client Side Object Model (CSOM) and Application Programming Interface (API) scripts not working for multiple services or features. We're reviewing recent changes made within the CSOM and API processing services to determine if this might be the cause of this issue.&nbsp;&nbsp; <br \/>Scope of impact: This issue may affect any users attempting to run CSOM and API call scripts.&nbsp;&nbsp; <br \/>Next update by: Thursday, November 21, 2019, at 1:30 PM UTC <\/p>\n<p>-21.11.2019 11:03:05<br \/>Title: Admin Portal usage reports are delayed<br \/>User Impact: Admins may receive delayed usage reports starting from November 11, 2019.<br \/>More info: The specific usage reports that are delayed at this time are:<br \/>-Yammer Activity<br \/>-Yammer Device usage<br \/>-Yammer Groups activity<br \/>-Office 365 Groups activity<br \/>-Office 365 Active users &#8211; Yammer active user report not available after November 11, 2019. <br \/>Current status: We've identified a delay in the source data needed to update the usage reports. We're analyzing diagnostic data to determine the cause of these delays. <br \/>Scope of impact: Any admin attempting to retrieve the affected usage reports from November 11, 2019 may be impacted. <br \/>Start time: Thursday, November 21, 2019, at 12:00 AM UTC <br \/>Next update by: Friday, November 22, 2019, at 4:00 AM UTC<\/p>\n<\/blockquote>\n<p><a href=\"https:\/\/web.archive.org\/web\/20220305122026\/https:\/\/www.news.com.au\/technology\/online\/businesses-grind-to-halt-as-essential-microsoft-services-go-offline\/news-story\/dc1b3cb259c0f2adacdeed28344c62ee\" target=\"_blank\" rel=\"noopener noreferrer\">Dieser Beitrag<\/a> aus Australien thematisiert den Ausfall ebenfalls. Ist gerade kein guter Monate f\u00fcr Microsoft und die Cloud. Bei askwoody.com hatte ich heute den Hinweis auf den Tweet von Kevin Beaumont zum Ausfall vom 20. November gesehen.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">There was a global outage of Office 365 for several hours, but thankfully Europe was in bed. <a href=\"https:\/\/t.co\/feIGv0TZNm\">https:\/\/t.co\/feIGv0TZNm<\/a><\/p>\n<p>\u2014 Kevin Beaumont (@GossiTheDog) <a href=\"https:\/\/twitter.com\/GossiTheDog\/status\/1197075540299173888?ref_src=twsrc%5Etfw\">November 20, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>  <\/p>\n<\/p>\n<p>Jemand von euch vom Ausfall betroffen?<\/p>\n<p><strong>\u00c4hnliche Artikel:<\/strong><br \/><a href=\"https:\/\/borncity.com\/blog\/2019\/11\/04\/office365-aktuell-gestrt\/\">Office365 aktuell gest\u00f6rt: EX194748 (4.11.2019)?<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2019\/10\/30\/strung-bei-microsoft-cloud-diensten-office-365\/\/\">St\u00f6rung bei Microsoft Cloud-Diensten (Office 365)?<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2019\/11\/07\/wieder-microsoft-365-cloud-strung-mo195050-7-11-2019\/\">Microsoft 365\/Office365-Cloud-St\u00f6rung (MO195050, 7.11.2019)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Kurze Information f\u00fcr Nutzer von Microsoft 365-Cloud-Diensten. Aktuell gibt es mal wieder eine St\u00f6rung bei diesen Diensten, wie ich Statusmeldung von Microsoft entnehme.<\/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-225126","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\/225126","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=225126"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/225126\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=225126"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=225126"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=225126"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}