{"id":271103,"date":"2022-07-31T00:01:17","date_gmt":"2022-07-30T22:01:17","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=271103"},"modified":"2023-06-22T15:30:22","modified_gmt":"2023-06-22T13:30:22","slug":"microsoft-365-dienste-gestrt-29-juli-2022","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2022\/07\/31\/microsoft-365-dienste-gestrt-29-juli-2022\/","title":{"rendered":"Microsoft 365-Dienste gestört (29. Juli 2022)"},"content":{"rendered":"

Noch ein kurzer Nachtrag, auch am 29. Juli 2022 gab es eine St\u00f6rung bei den Diensten von Microsoft 365 – die letzte St\u00f6rung hatte ich ja am 28. Juli gemeldet (siehe Auch Microsoft 365-Dienste gest\u00f6rt (28. Juli 2022)<\/a>).<\/p>\n

<\/p>\n

\"\"Blog-Leser Andreas P. hat mich Samstag-Morgen per Mail mit den notwendigen Details versorgt.<\/p>\n

Published Time: 29.07.2022 19:21:02
\nTitle: Some users may experience intermittent connectivity issues
\nUser Impact: Users may experience intermittent connectivity issues when attempting to connect to Microsoft 365 services.
\nMore info: Impacted scenarios included, but are not limited to:
\n– Inability to join Microsoft Teams calls and meetings
\n– Degraded audio and visual quality during Microsoft Teams calls and meetings
\n– Inability to access the Exchange Online service through all protocol methods
\n– Delays accessing the capacity settings page via the Power BI admin portal
\nCurrent status: Our telemetry continues to indicate that our services are performing as expected. We continue to monitor the environment to ensure that the issue doesn't reoccur.
\nScope of impact: This issue could have impacted any region intermittently; however, the regions surrounding South Africa, Brazil, North America, Canada, Japan and Korea saw the greatest levels of impact.
\nStart time: Friday, July 29, 2022, at 10:30 AM UTC
\nRoot cause: An unexpected increase in user requests resulted in network congestion.
\nNext update by: Friday, July 29, 2022, at 8:00 PM UTC
\nPublished Time: 29.07.2022 17:53:18
\nTitle: Some users may experience intermittent connectivity issues
\nUser Impact: Users may experience intermittent connectivity issues when attempting to connect to Microsoft 365 services.
\nMore info: Impacted scenarios include, but are not limited to:
\n– Inability to join Microsoft Teams calls and meetings
\n– Degraded audio and visual quality during Microsoft Teams calls and meetings
\n– Inability to access the Exchange Online service through all protocol methods
\n– Delays accessing the capacity settings page via the Power BI admin portal
\nCurrent status: Our monitoring telemetry indicates that the issue has recovered. We're continuing to actively monitor the environment and perform a set of proactive changes to prevent this type of issue from reoccurring.
\nScope of impact: This issue is specific to a subset of traffic routed through infrastructure in South Africa, Brazil, North America, Canada, Japan and Korea. This issue is also causing impact for users located in regions surrounding the infrastructure hosted in those locations.
\nStart time: Friday, July 29, 2022, at 10:30 AM UTC
\nRoot cause: An unexpected increase in user requests resulted in network congestion.
\nNext update by: Friday, July 29, 2022, at 5:30 PM UTC
\nPublished Time: 29.07.2022 16:29:14
\nTitle: Some users may experience intermittent connectivity issues
\nUser Impact: Users may experience intermittent connectivity issues when attempting to connect to Microsoft 365 services.
\nMore info: Impacted scenarios include, but are not limited to:
\n– unable to join Microsoft Teams calls and meetings
\n– degraded audio and visual quality during Microsoft Teams calls and meetings
\n– unable to access the Exchange Online service through all protocol methods
\n– delays to access of capacity settings page via the Power BI admin portal
\nCurrent status: We're continuing to review traffic patterns and are applying mitigation actions where we identify isolated increases in user requests that are contributing to the network congestion.
\nScope of impact: This issue is specific to a subset of traffic routed through infrastructure in South Africa, Brazil, North America, Canada, Japan and Korea. This results in impact for users located in surrounding regions of this infrastructure.
\nNext update by: Friday, July 29, 2022, at 4:30 PM UTC
\nPublished Time: 29.07.2022 14:41:03
\nTitle: Some users in South Africa and Brazil may experience intermittent connectivity issues
\nUser Impact: Users located in South Africa and Brazil may experience intermittent connectivity issues with Microsoft 365 services.
\nMore info: Impacted scenarios include, but are not limited to:
\n– unable to join Microsoft Teams calls and meetings
\n– degraded audio and visual quality during Microsoft Teams calls and meetings
\n– unable to access the Exchange Online service through all protocol methods
\n– delays to access of capacity settings page via the Power BI admin portal
\nCurrent status: We've identified that an unexpected increase in user requests is contributing to impact. We're analyzing traffic patterns to assist our investigation.
\nScope of impact: This issue is specific to a subset of traffic routed through infrastructure in South Africa and Brazil. This results in impact for users located in surrounding regions of this infrastructure.
\nNext update by: Friday, July 29, 2022, at 2:30 PM UTC
\nPublished Time: 29.07.2022 13:59:50
\nTitle: Some users in South Africa may experience intermittent connectivity issues
\nUser Impact: Users located in South Africa may experience intermittent connectivity issues when accessing Microsoft 365 services.
\nMore info: Impacted scenarios include, but are not limited to:
\n– unable to join Microsoft Teams calls and meetings
\n– degraded audio and visual quality during Microsoft Teams calls and meetings
\n– unable to access the Exchange Online service through all protocol methods
\nCurrent status: We've identified a potential networking issue resulting in impact. We're reviewing service monitoring telemetry to verify that this is the root cause, before formulating a plan for remediation.
\nScope of impact: Impact is specific to some users who are served through the affected infrastructure in South Africa.
\nNext update time: Friday, July 29, 2022, at 1:30 PM UTC<\/p><\/blockquote>\n

Hier noch ein Auszug \u00fcber mehrere Tage – es ruckelt ganz sch\u00f6n oft in der Microsoft Cloud.<\/p>\n

Published Time: 29.07.2022 02:22:56
\nTitle: Some users intermittently can't send or open email messages via the Outlook desktop client and Outlook on the web
\nUser Impact: Some users are intermittently unable to send or open email via the Outlook desktop client and Outlook on the web.
\nMore info: Affected users receive a Non-Delivery Report (NDR) when attempting to send email messages, but the message still arrives for the intended recipient(s). Depending on the client leveraged, NDRs may contain the following messages:
\n\"This message could not be sent. Try sending the message again later, or contact your network administrator.\"
\n\"Your message did not reach some or all of the intended recipients.\"
\nUsers can validate that they're affected by this event by reviewing the NDR and finding \"HResult \u200f(0x8004010F)\" within the error message.
\nCurrent status: We've confirmed in our testing environment that reverting the offending update resolves the underlining issue, and have initiated the process to the rest of the affected service environment. We're monitoring the progress of the revert throughout the upcoming weekend and anticipate that impact should be remediated by Monday, August 1, 2022.
\nScope of impact: This issue impacts some users attempting to send email messages via the Outlook desktop client and Outlook on the web.
\nStart time: Tuesday, July 12, 2022, at 12:00 AM UTC
\nEstimated time to resolve: We anticipate reverting the update will be completed by Monday, August 1, 2022.
\nRoot cause: A recent update intended to optimize traffic load balancing and improve email transport times introduced a code issue that's leading to impact.
\nNext update by: Monday, August 1, 2022, at 7:30 PM UTC
\nPublished Time: 28.07.2022 02:10:31
\nTitle: Some users intermittently can't send or open email messages via the Outlook desktop client and Outlook on the web
\nUser Impact: Users are intermittently unable to send or open email via the Outlook desktop client and Outlook on the web.
\nMore info: Affected senders receive a Non-Delivery Report (NDR) when attempting to send email messages. Depending on the client leveraged, NDRs may contain the following messages:
\n\"This message could not be sent. Try sending the message again later, or contact your network administrator.\" or \"Your message did not reach some or all of the intended recipients.\"
\nAdditionally, users may see delays or failures when opening messages or attachments in Outlook on the web with the associated errors:
\n\"Your message cannot be displayed\" and \"Please check on your network or tried again later\"
\nCurrent status: We're continuing to monitor as we're reverting the offending update in our testing environment to ensure it repairs the problem without causing additional unforeseen impact. Once the validation is successful, we'll initiate the revert to the impacted environment to resolve the issue.
\nScope of impact: Your organization is affected by this event, and this issue impacts some users attempting to send or open email messages via the Outlook desktop client and Outlook on the web.
\nStart time: Tuesday, July 12, 2022, at 12:00 AM UTC
\nRoot cause: A recent update intended to optimize traffic load balancing and improve email transport times introduced a code issue that's leading to impact.
\nNext update by: Friday, July 29, 2022, at 1:30 AM UTC
\nPublished Time: 27.07.2022 19:28:05
\nTitle: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web
\nUser Impact: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web.
\nMore info: Affected users receive a Non-Delivery Report (NDR) when attempting to send email messages. Depending on the client leveraged, NDRs may contain the following messages:
\n\"This message could not be sent. Try sending the message again later, or contact your network administrator.\"
\n\"Your message did not reach some or all of the intended recipients.\"
\nCurrent status: We've confirmed that the recent update intended to optimize traffic load balancing introduced a code issue that's causing this problem. We're reverting this update to remediate impact.
\nScope of impact: Your organization is affected by this event, and this issue impacts some users attempting to send email messages via the Outlook desktop client and Outlook on the web.
\nRoot cause: A recent update intended to optimize traffic load balancing and improve email transport times introduced a code issue that's leading to impact.
\nNext update by: Thursday, July 28, 2022, at 1:30 AM UTC
\nPublished Time: 27.07.2022 01:29:21
\nTitle: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web
\nUser Impact: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web.
\nMore info: Affected users receive a Non-Delivery Report (NDR) when attempting to send email messages. Depending on the client leveraged, NDRs may contain the following messages:
\n\"This message could not be sent. Try sending the message again later, or contact your network administrator.\"
\n\"Your message did not reach some or all of the intended recipients.\"
\nCurrent status: We're continuing our investigation of sample NDRs and the aforementioned update to identify the most effective path forward to remediation. We'll provide a remediation timeline once it becomes available.
\nScope of impact: Your organization is affected by this event, and this issue impacts some users attempting to send email messages via the Outlook desktop client and Outlook on the web.
\nRoot cause: A recent update intended to optimize traffic load balancing may have introduced a regression that's leading to impact.
\nNext update by: Wednesday, July 27, 2022, at 7:00 PM UTC
\nPublished Time: 26.07.2022 23:18:28
\nTitle: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web
\nUser Impact: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web.
\nMore info: Affected users receive a Non-Delivery Report (NDR) when attempting to send email messages. Depending on the client leveraged, NDRs may contain the following messages:
\n\"This message could not be sent. Try sending the message again later, or contact your network administrator.\"
\n\"Your message did not reach some or all of the intended recipients.\"
\nCurrent status: Our investigation of sample NDRs provided by affected users indicates that a recent update intended to optimize traffic load balancing may have introduced a regression that's leading to impact. We're reviewing the potentially offending update to confirm our findings and determine a path forward to remediation.
\nScope of impact: Your organization is affected by this event, and this issue impacts some users attempting to send email messages via the Outlook desktop client and Outlook on the web.
\nNext update by: Wednesday, July 27, 2022, at 1:00 AM UTC
\nPublished Time: 26.07.2022 19:21:20
\nTitle: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web
\nUser Impact: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web.
\nMore info: Affected users receive a Non-Delivery Report (NDR) when attempting to send email messages. Depending on the client leveraged, NDRs may contain the following messages:
\n\"This message could not be sent. Try sending the message again later, or contact your network administrator.\"
\n\"Your message did not reach some or all of the intended recipients.\"
\nCurrent status: We're continuing to examine message details from sample NDRs provided by affected users. Additionally, we're exploring whether a possible save conflict within the email-sending process may be contributing to the impact.
\nScope of impact: Your organization is affected by this event, and this issue impacts some users attempting to send email messages via the Outlook desktop client and Outlook on the web.
\nNext update by: Tuesday, July 26, 2022, at 11:00 PM UTC
\nPublished Time: 26.07.2022 17:59:35
\nTitle: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web
\nUser Impact: Some users are unable to send email messages via the Outlook desktop client and Outlook on the web.
\nMore info: Affected users receive a Non-Delivery Report (NDR) when attempting to send email messages. Depending on the client leveraged, NDRs may contain the following messages:
\n\"This message could not be sent. Try sending the message again later, or contact your network administrator.\"
\n\"Your message did not reach some or all of the intended recipients.\"
\nCurrent status: We're analyzing details from sample NDRs received by some affected users so we can further understand the issue and determine our next steps toward remediation.
\nScope of impact: Your organization is affected by this event, and this issue impacts some users attempting to send email messages via the Outlook desktop client and Outlook on the web.
\nNext update by: Tuesday, July 26, 2022, at 6:00 PM UTC
\nPublished Time: 26.07.2022 16:03:43
\nTitle: Some users receive a Non-Delivery Report (NDR) when attempting to send email messages
\nUser Impact: Users receive a Non-Delivery Report (NDR) when attempting to send email messages.
\nCurrent status: We're analyzing system logs to determine our next troubleshooting steps.
\nScope of impact: Your organization is affected by this event, and this issue may impact any user sending email messages.
\nNext update by: Tuesday, July 26, 2022, at 4:00 PM UTC<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

Noch ein kurzer Nachtrag, auch am 29. Juli 2022 gab es eine St\u00f6rung bei den Diensten von Microsoft 365 – die letzte St\u00f6rung hatte ich ja am 28. Juli gemeldet (siehe Auch Microsoft 365-Dienste gest\u00f6rt (28. Juli 2022)).<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7263,7862],"tags":[1171,987],"class_list":["post-271103","post","type-post","status-publish","format-standard","hentry","category-cloud","category-stoerung","tag-cloud","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/271103","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=271103"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/271103\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=271103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=271103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=271103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}