{"id":229437,"date":"2020-03-12T20:22:08","date_gmt":"2020-03-12T19:22:08","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=229437"},"modified":"2020-03-12T20:24:40","modified_gmt":"2020-03-12T19:24:40","slug":"weiter-exchange-online-probleme-12-3-2020","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2020\/03\/12\/weiter-exchange-online-probleme-12-3-2020\/","title":{"rendered":"Weiter Exchange Online Probleme (12.3.2020)"},"content":{"rendered":"

[English<\/a>]Seit dem 11. M\u00e4rz 2020 gibt es wohl eine St\u00f6rung bei Exchange Online. Benutzer konnten sich mit dem Outlook Desktop-Client nicht mehr anmelden. Die St\u00f6rung scheint weiterhin anzuhalten.<\/p>\n

<\/p>\n

\"\"Blog-Leser Andreas P. hat mir gerade per Mail die Statusmeldung zum Vorfall: EX206210, betroffener Dienst: Exchange Online, betroffenes Feature: Signin, aktueller Status: Dienstbeeintr\u00e4chtigung<\/em> geschickt. Hier der Auszug aus dem Admin-Portal \u2013 die St\u00f6rung h\u00e4lt wohl noch an.<\/p>\n

-12.03.2020 19:19:54
\nTitle: Can't sign in to Outlook on the web
\nUser Impact: Users may experience intermittent access issues when signing in from Outlook on the web.
\nCurrent status: We've determined that this issue is being caused by a recent deployment that inadvertently introduced a configuration issue affecting the infrastructure hosting the sign in process for Outlook on the web, which resulted in impact. We've halted deployment of the affected build and developed a fix for the configuration problem that's being deployed to the affected environment.
\nScope of impact: For most customers, it's unlikely that many users would report impact related to this event.
\nRoot cause: A recent deployment inadvertently introduced a configuration issue affecting the infrastructure hosting the sign in process for Outlook on the web.
\nNext update by: Friday, March 13, 2020, at 1:00 AM UTC<\/p>\n

-12.03.2020 19:30:30
\nTitle: Can't access Exchange Online Outlook client
\nUser Impact: Users may be unable to access Exchange Online using the Outlook desktop client.
\nMore info: Affected users are prompted for their credentials; however, the correct credentials aren't accepted.
\nCurrent status: We've reverted the recent change and we're testing with previously affected users to confirm that impact has been remediated.
\nScope of impact: Impact is specific to users who are served through the affected infrastructure.
\nStart time: Friday, March 6, 2020, at 8:08 PM UTC
\nRoot cause: A recent change to basic authentication behavior inadvertently resulted in impact.
\nNext update by: Thursday, March 12, 2020, at 11:00 PM UTC
\n-12.03.2020 01:35:21
\nTitle: Can't access Exchange Online Outlook client
\nUser Impact: Users may be unable to access Exchange Online using the Outlook desktop client.
\nMore info: Affected users are prompted for their credentials; however, the correct credentials aren't accepted. While we're focused on remediation, users who have access to Outlook on the web may be able to use that protocol as an alternative method to access the service.
\nCurrent status: We've identified that a recent change to basic authentication behavior inadvertently resulted in impact. We're reverting the affecting change to mitigate impact.
\nScope of impact: Impact is specific to users who are served through the affected infrastructure.
\nStart time: Friday, March 6, 2020, at 8:08 PM UTC
\nRoot cause: A recent change to basic authentication behavior inadvertently resulted in impact.
\nNext update by: Thursday, March 12, 2020, at 7:00 PM UTC
\n-12.03.2020 00:44:36
\nTitle: Can't access Exchange Online Outlook client
\nUser Impact: Users may be unable to access Exchange Online using the Outlook desktop client.
\nMore info: Affected users are prompted for their credentials; however, the correct credentials aren't accepted.
\nCurrent status: We've identified a potential basic authentication issue which may be the source of impact. We're requesting additional, decrypted Fiddler network traces from impacted users taken during reproduction of impact, as well as a Get Diagnostics report to be sent to our support team for additional review.
\nScope of impact: Impact is specific to users who are served through the affected infrastructure.
\nNext update by: Thursday, March 12, 2020, at 2:00 AM UTC
\n-11.03.2020 21:39:58
\nTitle: Can't access Exchange Online Outlook client
\nUser Impact: Users may be unable to access Exchange Online using the Outlook desktop client.
\nMore info: Affected users are prompted for their credentials; however, the correct credentials aren't accepted.
\nCurrent status: We're continuing to review a group of security tokens and subscription configurations; however, our investigation has been inconclusive so far, as the supplemental diagnostic data available to us is insufficient. We're requesting impacted customers supply a decrypted Fiddler network trace while reproducing the impact and a Get Diagnostics report to our support team, which will be crucial in helping us determine our next steps for remediating impact.
\nScope of impact: Impact is specific to users who are served through the affected infrastructure.
\nNext update by: Thursday, March 12, 2020, at 12:00 AM UTC
\n-11.03.2020 20:12:39
\nTitle: Can't access Exchange Online Outlook client
\nUser Impact: Users may be unable to access Exchange Online using the Outlook desktop client.
\nMore info: Affected users are prompted for their credentials; however, the correct credentials aren't accepted.
\nCurrent status: We're continuing to analyze recently collected network trace data, and confirm the source for this event. In parallel, we're investigating a group of security tokens and the configuration for subscriptions, to determine if they are contributing to this event.
\nScope of impact: Impact is specific to users who are served through the affected infrastructure.
\nNext update by: Wednesday, March 11, 2020, at 9:30 PM UTC
\n-11.03.2020 18:37:02
\nTitle: Can't access Exchange Online Outlook client
\nUser Impact: Users may be unable to access Exchange Online using the Outlook desktop client.
\nMore info: Affected users are prompted for their credentials; however, the correct credentials aren't accepted.
\nCurrent status: Our analysis into the reproduction of the issue has not been successful in identifying the cause of impact. We're analyzing recently collected network trace data to determine our next troubleshooting steps.
\nScope of impact: Impact is specific to users who are served through the affected infrastructure.
\nNext update by: Wednesday, March 11, 2020, at 7:30 PM UTC
\n-11.03.2020 16:19:26
\nTitle: Can't access Exchange Online Outlook client
\nUser Impact: Users may be unable to access Exchange Online using the Outlook desktop client.
\nMore info: Affected users are prompted for their credentials; however, the correct credentials aren't accepted.
\nCurrent status: We're collecting additional network trace data from affected users to identify the source for this event. In parallel, we're continuing to analyze a recent reproduction of the event to determine our next steps for remediating impact.
\nScope of impact: Impact is specific to users who are served through the affected infrastructure.
\nNext update by: Wednesday, March 11, 2020, at 6:00 PM UTC
\n-11.03.2020 15:04:40
\nTitle: Can't access Exchange Online
\nUser Impact: Users may be unable to access Exchange Online using the Outlook Desktop client.
\nMore info: Affected users are prompted for their credentials, however, the correct credentials are not accepted.
\nCurrent status: We've received reports that impact associated with EX206190 persists. We've resumed our investigation of the issue and are reviewing data from users in active reproduction of the issue to determine the cause of impact.
\nScope of impact: Impact is specific to users who are served through the affected infrastructure.
\nNext update by: Wednesday, March 11, 2020, at 3:30 PM UTC<\/p>\n","protected":false},"excerpt":{"rendered":"

[English]Seit dem 11. M\u00e4rz 2020 gibt es wohl eine St\u00f6rung bei Exchange Online. Benutzer konnten sich mit dem Outlook Desktop-Client nicht mehr anmelden. Die St\u00f6rung scheint weiterhin anzuhalten.<\/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,4322,987],"class_list":["post-229437","post","type-post","status-publish","format-standard","hentry","category-cloud","category-office","category-stoerung","tag-cloud","tag-exchange-online","tag-office","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/229437","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=229437"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/229437\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=229437"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=229437"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=229437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}