{"id":227361,"date":"2020-01-23T10:42:47","date_gmt":"2020-01-23T09:42:47","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=227361"},"modified":"2020-01-23T12:33:23","modified_gmt":"2020-01-23T11:33:23","slug":"strung-bei-exchange-online-access-23-1-2020","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2020\/01\/23\/strung-bei-exchange-online-access-23-1-2020\/","title":{"rendered":"Störung bei Exchange Online\/Access (23.1.2020)"},"content":{"rendered":"

[English<\/a>]Bei Microsoft scheint es eine St\u00f6rung bei den Cloud-Diensten zu geben. Exchange Online (und gem\u00e4\u00df Titel der Statusmeldung Access) sind wohl davon betroffen, wie ich gerade von Blog-Leser Andreas P. erfahren habe (danke daf\u00fcr).<\/p>\n

<\/p>\n

\"\"Die St\u00f6rung hat bereits heute Nacht begonnen und h\u00e4lt bisher an. Benutzer k\u00f6nnen sich im Web nicht an Outlook anmelden, wobei das nur Nutzer betrifft, die aktuell noch nicht im Web unter Outlook angemeldet sind und das nicht gecached haben.<\/p>\n

Auf den Twitter-Kan\u00e4len von Azure und Office365 habe ich nichts zur St\u00f6rung gefunden. Ursache ist laut den Statusmeldungen ein von Microsoft in der Cloud durchgef\u00fchrtes Konfigurationsupdate f\u00fcr den HTTP-Proxy (Hypertext Transfer Protocol), welches einen Bug (von Microsoft als Codefehler tituliert) enthielt. Aktuell ist die Mannschaft dabei, ein Korrekturupdate auszurollen. Nachfolgend finden sich noch einige Ausz\u00fcge aus laufenden Statusmeldung. Irgend jemand betroffen?<\/p>\n

Statusmeldungen von Microsoft<\/h3>\n

Hier ein Auszug der Statusmeldungen aus dem Dashboard, welches nur Admins zug\u00e4nglich ist (danke an Andreas f\u00fcr den Auszug).<\/p>\n

-23.01.2020 09:52:58<\/p>\n

Title: Can't sign in to Outlook on the web<\/p>\n

User Impact: Users may be unable to sign in to Outlook on the web.<\/p>\n

More info: This issue only impacts users who do not have Outlook on the web cache. Users who are currently signed in may not experience impact.<\/p>\n

Current status: We're in the final stages of deployment and can confirm that users will start to experience relief as it progresses across the environment.<\/p>\n

Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.<\/p>\n

Start time: Thursday, January 23, 2020, at 1:45 AM UTC<\/p>\n

Root cause: A configuration update for the Hypertext Transfer Protocol (HTTP) proxy contains a code error.<\/p>\n

Next update by: Thursday, January 23, 2020, at 11:00 AM UTC<\/p>\n

-23.01.2020 07:55:11<\/p>\n

Title: Can't sign in to Outlook on the web<\/p>\n

User Impact: Users may be unable to sign in to Outlook on the web.<\/p>\n

More info: This issue only impacts users who do not have Outlook on the web cache. Users who are currently signed in may not experience impact.<\/p>\n

Current status: The deployment is taking longer than expected. We're investigating ways to expedite the process and we're continuing monitoring the deployment status.<\/p>\n

Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.<\/p>\n

Start time: Thursday, January 23, 2020, at 1:45 AM UTC<\/p>\n

Root cause: A configuration update for the Hypertext Transfer Protocol (HTTP) proxy contains a code error.<\/p>\n

Next update by: Thursday, January 23, 2020, at 9:00 AM UTC<\/p>\n

-23.01.2020 05:55:33<\/p>\n

Title: Can't sign in to Outlook on the web<\/p>\n

User Impact: Users may be unable to sign in to Outlook on the web.<\/p>\n

More info: This issue only impacts users who do not have Outlook on the web cache. Users who are currently signed in may not experience impact.<\/p>\n

Current status: The deployment is progress as expected and is approximately 95 percent complete.<\/p>\n

Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.<\/p>\n

Start time: Thursday, January 23, 2020, at 1:45 AM UTC<\/p>\n

Estimated time to resolve: Within the next one to two hours.<\/p>\n

Root cause: A configuration update for the Hypertext Transfer Protocol (HTTP) proxy contains a code error.<\/p>\n

Next update by: Thursday, January 23, 2020, at 7:00 AM UTC<\/p>\n

-23.01.2020 04:01:40<\/p>\n

Title: Can't sign in to Outlook on the web<\/p>\n

User Impact: Users may be unable to sign in to Outlook on the web.<\/p>\n

More info: This issue only impacts users who do not have Outlook on the web cache. Users who are currently signed in may not experience impact.<\/p>\n

Current status: We've determined that a configuration update for the Hypertext Transfer Protocol (HTTP) proxy contained a code error. We've developed and validated a fix for the code error and are deploying it to the affected infrastructure.<\/p>\n

Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.<\/p>\n

Root cause: A configuration update for the Hypertext Transfer Protocol (HTTP) proxy contained a code error.<\/p>\n

Next update by: Thursday, January 23, 2020, at 5:00 AM UTC<\/p>\n

-23.01.2020 03:27:12<\/p>\n

Title: Can't sign in to Outlook on the web<\/p>\n

User Impact: Users may be unable to sign in to Outlook on the web.<\/p>\n

More info: This issue may only impact users who do not have Outlook on the web cache. Users who are currently signed in may not experience impact.<\/p>\n

Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.<\/p>\n

Scope of impact: This issue could potentially affect any of your users intermittently if they are routed through the affected infrastructure.<\/p>\n","protected":false},"excerpt":{"rendered":"

[English]Bei Microsoft scheint es eine St\u00f6rung bei den Cloud-Diensten zu geben. Exchange Online (und gem\u00e4\u00df Titel der Statusmeldung Access) sind wohl davon betroffen, wie ich gerade von Blog-Leser Andreas P. erfahren habe (danke daf\u00fcr).<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7263,270,7862],"tags":[1171,7211,987],"class_list":["post-227361","post","type-post","status-publish","format-standard","hentry","category-cloud","category-office","category-stoerung","tag-cloud","tag-exchange-online","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/227361","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=227361"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/227361\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=227361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=227361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=227361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}