{"id":224535,"date":"2019-11-02T13:34:20","date_gmt":"2019-11-02T12:34:20","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=224535"},"modified":"2019-11-02T13:45:07","modified_gmt":"2019-11-02T12:45:07","slug":"exchange-online-gestrt-1-11-2019","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2019\/11\/02\/exchange-online-gestrt-1-11-2019\/","title":{"rendered":"Exchange Online gest&ouml;rt (1.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\"\/>Zum 1. November 2019 scheint es bei Office365 einige Probleme mit Diensten gegeben zu haben. Unter anderem war die Anmeldung bei Exchange Online gest\u00f6rt. <\/p>\n<p><!--more--><\/p>\n<p>Ich hatte ja zum 30. Oktober 2019 bereits im Artikel <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> nachgefragt, ob es eventuell Probleme mit der Microsoft-Cloud gibt. Blog-Leser Andreas P. hat mich gestern (1.11.2019) per E-Mail kontaktiert und auf Probleme mit Exchange-Diensten hingewiesen \u2013 ich komme aber erst jetzt dazu, das aufzubereiten. Laut downdetector.com gab es gestern und vorgestern Probleme mit Office365.com die aber wohl seit einigen Stunden behoben sind. <\/p>\n<p><img decoding=\"async\" title=\"Office365-St&ouml;rung\" alt=\"Office365-St&ouml;rung\" src=\"https:\/\/i.imgur.com\/Qx6QCpQ.jpg\"\/><\/p>\n<p>Auf Twitter hat Microsoft einen entsprechenden Hinweis auf m\u00f6gliche Probleme gegeben und verweist auf einen Eintrag im Control Panel des Diensts \u2013 auf den ich aber mangels Konto nicht zugreifen kann.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">We're investigating an issue where some users are unable to access the Exchange admin center or Exchange Control Panel. Updates will be provided in EX194594.<\/p>\n<p>\u2014 Microsoft 365 Status (@MSFT365Status) <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1190164526253006850?ref_src=twsrc%5Etfw\">November 1, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>  <\/p>\n<p>Andreas hat mir einen Auszug aus den Status-Meldungen zur Verf\u00fcgung gestellt, die n\u00e4heres zu den Problemen verraten. Hier die Meldungen:<\/p>\n<blockquote>\n<p>-01.11.2019 04:28:12<br \/>Title: Can't access Exchange Online<br \/>User Impact: Users may be intermittently unable to access Exchange Online services.<\/p>\n<p>More info: Users may receive 5xx errors when accessing Exchange Online services using Outlook if dependent on Autodiscover functionality.<br \/>New users may be unable to configure Outlook for desktop or mobile if creating a profile when leveraging Autodiscover. Existing Outlook desktop users may notice intermittent access issues or login prompts if Autodiscover is triggered in their profile. <\/p>\n<p>We recommend users who have access to Outlook on the web to use that protocol as an alternative method to access the service. <\/p>\n<p>Current status: We've completed validating our fix internally and have confirmed it resolves the issue. We've initiated deployment to the affected infrastructure and we expect to fully to restore service to all impacted environments within the next six hours. <\/p>\n<p>Scope of impact: Any user may be affected by this event. <br \/>Start time: Thursday, October 31, 2019, at 3:30 PM UTC <\/p>\n<p>Root cause: A change to one of our deployment mechanisms caused it to begin improperly updating .config files that are normally untouched by this update process, preventing users from accessing Exchange Online via any protocol. <br \/>Next update by: Friday, November 1, 2019, at 7:30 AM UTC <\/p>\n<p>-01.11.2019 02:34:16<br \/>Title: Can't access Exchange Online<br \/>User Impact: Users may be intermittently unable to access Exchange Online services.<br \/>More info: Users may receive 503 errors when accessing Exchange Online services governed by .config files.<br \/>New users may be unable to configure Outlook for desktop or mobile. Existing outlook users may begin receiving the errors after 15 minutes. Additionally, any users may be unable to access Outlook on the web.<\/p>\n<p>Current status: We preparing an emergency patch for our test environment that will update a specific property within the .config files to restore service access. Once we've confirmed that this fixes the problem, we'll develop a timetable for deployment.<\/p>\n<p>Scope of impact: Any user may be affected by this event.<br \/>Start time: Thursday, October 31, 2019, at 3:30 PM UTC<\/p>\n<p>Root cause: A change to one of our deployment mechanisms caused it to begin improperly updating .config files that are normally untouched by this update process.<br \/>Next update by: Friday, November 1, 2019, at 3:30 AM UTC<\/p>\n<p>-01.11.2019 01:37:19<br \/>Title: Can't access Exchange Online<br \/>User Impact: Users may be intermittently unable to access Exchange Online services.<br \/>More info: Users may receive 503 errors when accessing Exchange Online services governed by .config files.<\/p>\n<p>New users may be unable to configure Outlook for desktop or mobile. Existing Outlook users may begin receiving the errors after 15 minutes. Additionally, any users may be unable to access Outlook on the web.<br \/>Current status: We've identified that a recent change to one of our update deployment mechanisms caused it to begin improperly updating .config files that would normally be unaffected by this update process. As a result, users accessing Exchange Online services that rely on the updated .config files will receive 503 errors. We've identified and stopped all current deployments associated with this updated mechanism to prevent further impact, and are working to identify the most expedient means of restoring service access for affected users.<\/p>\n<p>Scope of impact: Any user may be affected by this event.<br \/>Start time: Thursday, October 31, 2019, at 3:30 PM UTC<\/p>\n<p>Root cause: A change to one of our deployment mechanisms caused it to begin improperly updating .config files that are normally untouched by this update process.<br \/>Next update by: Saturday, November 1, 2019, at 2:30 AM UTC<\/p>\n<p>-01.11.2019 01:10:23<br \/>Title: Can't access Exchange Online <br \/>User Impact: Users may receive 503 errors when accessing Exchange Online services. <br \/>Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.<br \/>Scope of impact: Any user may be affected by this event.<br \/>Next update by: Friday, November 1, 2019, at 1:00 AM UTC<\/p>\n<\/blockquote>\n<p>Es gab also wohl wieder ein Problem bei der Verteilung einer Software-Aktualisierung. Konkret hat ein \u00c4nderung an einem der Microsoft Update-Bereitstellungsmechanismen dazu gef\u00fchrt, dass es die Aktualisierung von .config-Dateien fehlerhaft vorgenommen wurde (obwohl diese normalerweise von diesem Update-Vorgang nicht betroffen sein sollten). Infolgedessen erhielten Benutzer, die auf Exchange Online-Dienstes zugreifen wollten, die auf die aktualisierten <em>.config<\/em>-Dateien angewiesen sind, den 503 Fehler angewiesen. Ich ziehe aus diesem Vorfall und einer weiteren St\u00f6rung der Microsoft Cloud Mitte Oktober (<a href=\"https:\/\/borncity.com\/blog\/2019\/10\/18\/multifaktor-authentifizierung-fr-azure-u-office-365-gestrt\/\" target=\"_blank\" rel=\"noopener noreferrer\">siehe hier<\/a>) den Schluss, dass dort \u00e4hnliches wie beim Patchen von Windows-Systemen abl\u00e4uft.&nbsp; <\/p>\n<p><strong>\u00c4hnliche Artikel:<\/strong><br \/><a href=\"https:\/\/borncity.com\/blog\/2019\/10\/18\/multifaktor-authentifizierung-fr-azure-u-office-365-gestrt\/\" target=\"_blank\" rel=\"noopener noreferrer\">Multifaktor-Authentifizierung f\u00fcr Azure u. Office 365 gest\u00f6rt?<\/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\/10\/25\/microsofts-cloud-ausfall-im-oktober-2019-hintergrnde-und-verlauf\/\">Microsofts Cloud-Ausfall (Okt. 2019) \u2013 Hintergr\u00fcnde und Verlauf<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2019\/10\/27\/microsoft-erhlt-zuschlag-des-us-pentagons-fr-die-jedi-cloud\/\">Microsoft erh\u00e4lt Zuschlag des US-Pentagons f\u00fcr die Jedi-Cloud<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2019\/10\/27\/adobe-creative-cloud-75-millionen-nutzerdaten-ffentlich\/\">Adobe Creative Cloud: 7,5 Millionen Nutzerdaten \u00f6ffentlich<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Zum 1. November 2019 scheint es bei Office365 einige Probleme mit Diensten gegeben zu haben. Unter anderem war die Anmeldung bei Exchange Online gest\u00f6rt.<\/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":[7801,987],"class_list":["post-224535","post","type-post","status-publish","format-standard","hentry","category-cloud","tag-echange-online","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/224535","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=224535"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/224535\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=224535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=224535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=224535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}