{"id":282177,"date":"2023-06-05T18:58:33","date_gmt":"2023-06-05T16:58:33","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=282177"},"modified":"2024-06-11T16:21:49","modified_gmt":"2024-06-11T14:21:49","slug":"exchange-online-strung-5-juni-2023","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2023\/06\/05\/exchange-online-strung-5-juni-2023\/","title":{"rendered":"Exchange Online-St&ouml;rung (5. Juni 2023) &#8211; Werk russischer Hacker?"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"margin: 0px 10px 0px 0px;\" title=\"Stop - Pixabay\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2021\/06\/Stop01.jpg\" alt=\"Stop - Pixabay\" width=\"131\" height=\"131\" align=\"left\" \/>[<a href=\"https:\/\/borncity.com\/win\/2023\/06\/06\/exchange-online-down-for-hours-june-5-2023\/\" target=\"_blank\" rel=\"noopener\">English<\/a>]Zum 5. Juni 2023 hat es bei Microsofts Exchange Online wohl eine massivere St\u00f6rung gegeben. Administratoren kamen nicht mehr ins Admin-Center und Outlook konnte im Web nicht mehr erreicht werden. Ein Nutzer hat mich auf diese St\u00f6rung hingewiesen, die kurz vor 16:00 Uhr deutscher Zeit begann, inzwischen (18:40 Uhr) aber wohl weitgehend behoben ist. Microsoft hat die St\u00f6rung inzwischen best\u00e4tigt. <strong>Erg\u00e4nzung:<\/strong> Inzwischen behauptet die pro-russische Hackergruppe Anonymous Sudan f\u00fcr die St\u00f6rung (per DDoS) verantwortlich zu sein.<\/p>\n<p><!--more--><\/p>\n<h2>Eine Lesermeldung<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg07.met.vgwort.de\/na\/5c23806534784d71bbd62b0f7b0c1d16\" alt=\"\" width=\"1\" height=\"1\" \/>Ein Blog-Leser hat sich kurz vor 18:00 Uhr bei mir per E-Mail gemeldet und berichtete \u00fcber die aufgetretene St\u00e4rung bei Exchange Online. Laut Leser gab es wohl \"einen richtig gro\u00dfen Exchange Online Ausfall\". Der Leser hat mir folgenden Screenshot des Service Health Dashboard\u00a0 mitgeschickt, der die Statusseite zeigt. Dazu schrieb der Leser:<\/p>\n<p><img decoding=\"async\" title=\"Exchange Online-St\u00f6rung (5. Juni 2023)\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2023\/06\/jf3wRXh.png\" alt=\"Exchange Online-St\u00f6rung (5. Juni 2023)\" \/><\/p>\n<blockquote><p>Ist bei uns trotz Azure Location West (Holland\/Irland) bemerkbar, dass Outlook kein Connect bekommt bzw. Outlook Online nur Fragmentiert was anzeigt. Mal gehts, mal gehts nicht, dann gehts dann wieder nicht :-)<\/p>\n<p>Mal schauen ob es noch mehr werden wie 100 &#8230;<\/p>\n<p>Im Admin Center schaut das ganze aus wie ein Alarmstufe Rot auf der Enterprise :-D<\/p><\/blockquote>\n<p><a href=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2023\/06\/vIgboVz.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Exchange Online-St\u00f6rung (5. Juni 2023)\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2023\/06\/vIgboVz.png\" alt=\"Exchange Online-St\u00f6rung (5. Juni 2023)\" width=\"641\" height=\"374\" \/><\/a><br \/>\n(Zum Vergr\u00f6\u00dferen klicken)<\/p>\n<p>Auf reddit.com gibt es ebenfalls <a href=\"https:\/\/web.archive.org\/web\/20231121030849\/https:\/\/www.reddit.com\/r\/sysadmin\/comments\/141g7wk\/o365_issues\/\" target=\"_blank\" rel=\"noopener\">diesen Thread<\/a>, wo jemand gegen 16:00 Uhr nachfragt, ob es eine St\u00f6rung g\u00e4be. Dort best\u00e4tigen weitere Betroffene den Ausfall. Ich habe mal den downdetector (bzw. die deutsche Seite allestoerungen.de) befragt und bekam diesen Ausfall quasi best\u00e4tigt &#8211; es gibt einen Peak bei den St\u00f6rungsmeldungen.<\/p>\n<p><img decoding=\"async\" title=\"Exchange Online-St\u00f6rung (5. Juni 2023)\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2023\/06\/nl1tlCV.png\" alt=\"Exchange Online-St\u00f6rung (5. Juni 2023)\" \/><\/p>\n<h2>Microsoft best\u00e4tigt den Ausfall<\/h2>\n<p>Auf Twitter gibt es von Microsoft inzwischen die Best\u00e4tigung zu einem Problem. Am 5. Juni 2023 schreibt <a href=\"https:\/\/twitter.com\/MSFT365Status\/status\/1665734492122742790?\" target=\"_blank\" rel=\"noopener\">Microsoft365-Status<\/a> gegen 16:47 Uhr deutscher Zeit folgendes:<\/p>\n<blockquote><p>We're investigating an issue with accessing Outlook on the web. Further details can be found under EX571516 in the admin center.<\/p><\/blockquote>\n<p>Sp\u00e4ter wurde das dann folgenderma\u00dfen erg\u00e4nzt:<\/p>\n<blockquote><p>We're reviewing our networking systems and recent updates in an effort to identify the underlying root cause of the issue. Additional information can be found in the admin center under EX571516.<\/p><\/blockquote>\n<p>Und vor 49 Minuten hie\u00df es:<\/p>\n<blockquote><p>We've identified downstream impact for Microsoft Teams, SharePoint Online and OneDrive for Business. We're providing full impact details and updates for those services via MO571683. Updates pertaining to Exchange and Outlook on the web will continue to be provided via EX571516.<\/p>\n<p>We've halted an ongoing deployment and are monitoring services to see if that provides relief to the environment. Further information can be found in the admin center under EX571516 and MO571683.<\/p><\/blockquote>\n<p>Es gibt also eine St\u00f6rung, die den Zugriff auf Outlook im Web verhindert. Das hat auch Auswirkungen auf Microsoft Teams, SharePoint Online und OneDrive for Business identifiziert. Microsoft will vollst\u00e4ndige Details zu den Auswirkungen und Updates f\u00fcr diese Dienste \u00fcber MO571683 bereitstellen. Updates f\u00fcr Exchange und Outlook im Web werden weiterhin \u00fcber EX571516 bereitgestellt. Inzwischen hat Microsoft in nachfolgender Meldung mitgeteilt, dass eine laufende Bereitstellung gestoppt wurde.<\/p>\n<blockquote><p>We've reverted the update and telemetry shows service improvement. We're continuing to monitor the service to ensure recovery and performing actions to address any residual impact. Further information can be found under EX571516 and MO571683 in the admin center.<\/p><\/blockquote>\n<p>Aktuell \u00fcberwacht Microsoft die Dienste und hofft, dass die St\u00f6rung langsam abklingt. War jemand von euch betroffen? Falls jemand Zugriff auf die Statusmeldungen im Admin-Center hat, kann er diese ja hier posten.<\/p>\n<h2>Pro-russische Hacktivisten verantwortlich?<\/h2>\n<p><strong>Erg\u00e4nzung:<\/strong> Inzwischen behauptet die pro-russische Hackergruppe Anonymous Sudan f\u00fcr die St\u00f6rung verantwortlich zu sein. Nachfolgender <a href=\"https:\/\/twitter.com\/CyberNews\/status\/1665778337485144068\" target=\"_blank\" rel=\"noopener\">Tweet<\/a> verweist auf <a href=\"https:\/\/cybernews.com\/security\/microsoft-outlook-outage-anonymous-sudan\/\" target=\"_blank\" rel=\"noopener\">diesen Beitrag<\/a>, wo Ausz\u00fcge der Stellungnahmen dieser Hacktivisten zu finden sind. Die Hacktivisten geben an, Microsofts Server per DDoS-Angriff \u00fcberlastet zu haben. Wie belastbar das ist, kann ich nicht beurteilen.<br \/>\n<a href=\"https:\/\/twitter.com\/CyberNews\/status\/1665778337485144068\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2023\/06\/lel9EM4.png\" alt=\"Exchange Online outage\" \/><\/a><br \/>\nMicrosofts Statusmeldungen<\/p>\n<p><strong>Erg\u00e4nzung:<\/strong> Andreas P. hat mir inzwischen die nachfolgenden Ausz\u00fcge aus dem Status Dashboard von Exchange Online geschickt.<\/p>\n<blockquote><p>Share: Incident: EX571516, impacted service: Exchange Online, impacted feature: E-Mail and calendar access, current status is: Service restored<\/p>\n<p>Published Time: 05.06.2023 19:58:46<\/p>\n<p>Title: Some users were unable to access Outlook on the web, and may have experienced issues with other Exchange Online services<\/p>\n<p>User impact: Users were unable to access Outlook on the web, and may have experienced issues with other Exchange Online services.<\/p>\n<p>More info: Additionally, other Microsoft 365 services also experienced impact:<br \/>\nMicrosoft Teams<br \/>\n&#8211; Users may have had difficulties scheduling meetings and\/or live events<br \/>\n&#8211; Users may have had trouble loading people profile cards<br \/>\n&#8211; Users may have had issues loading file lists<br \/>\n&#8211; Users may have been unable to create new teams &amp; channels<br \/>\n&#8211; Users may have been unable to install apps<br \/>\n&#8211; Users may have experienced issues performing searches<br \/>\n&#8211; Users may have seen delays in admin policy changes taking effect<br \/>\n&#8211; Users might have seen errors when using messaging extensions<br \/>\n&#8211; Users may have been unable to view up to date Presence information<br \/>\n&#8211; Teams Graph APIs may have been impacted<br \/>\n&#8211; Assignments tab in Teams may have not loaded<br \/>\n&#8211; Teams Admin Center functionalities were not performing as expected<\/p>\n<p>SharePoint Online and OneDrive for Business<br \/>\n&#8211; Users may have been unable to use Search functionality<\/p>\n<p>Microsoft Power Automate in Microsoft 365<br \/>\n&#8211; Users were unable to trigger flows using Office 365 connectors in Microsoft Power Automate<\/p>\n<p>Power Apps in Microsoft 365<br \/>\n&#8211; Users were unable to run apps in Power Apps that utilize Office 365 connectors<br \/>\n&#8211; Flows using the Office 365 Groups, Groups Mail, Outlook, Users, and Videos connectors may have been impacted<\/p>\n<p>Final status: We've completed the restarts to address the residual impact, and after an extended period of monitoring, we've confirmed that the issue is resolved. We continue to investigate why the update caused impact and further details will be provided within the Post-Incident Report.<\/p>\n<p>Scope of impact: Impact was primarily to users hosted within infrastructure that received the update prior to the deployment halt. However, any user may have experienced some degree of impact as described in the \"More Info\" section above.<\/p>\n<p>Start time: Monday, June 5, 2023, at 2:10 PM UTC<\/p>\n<p>End time: Monday, June 5, 2023, at 5:13 PM UTC<\/p>\n<p>Preliminary root cause: A recent update, intended to add additional resilliencies against downstream request remaining in a hanging state, inadvertently caused impact.<\/p>\n<p>Next steps:<br \/>\n&#8211; We're reviewing dump files gathered from impacted components during the incident to better understand why impact occurred.<br \/>\n&#8211; We're investigating to content of the update to identify the underlying root cause.<\/p>\n<p>We'll publish a Post-Incident report within five business days.<\/p>\n<p>Published Time: 05.06.2023 19:07:56<\/p>\n<p>Telemetry indicates that service availability is at approximately 99.9% across the service. We're continuing to isolate a small number of components which remain in an unhealthy state and are performing targeted restarts to remediate the residual impact.<\/p>\n<p>This quick update is designed to give the latest information on this issue.<\/p>\n<p>Published Time: 05.06.2023 18:19:40<\/p>\n<p>Title: Some users are unable to access Outlook on the web, and may experience issues with other Exchange Online services<\/p>\n<p>User impact: Users are unable to access Outlook on the web, and may experience issues with other Exchange Online services.<\/p>\n<p>More info: Additionally, other Microsoft 365 services are also experiencing impact:<br \/>\nMicrosoft Teams<br \/>\n&#8211; Users may have difficulties scheduling meetings and\/or live events<br \/>\n&#8211; Users may have trouble loading people profile cards<br \/>\n&#8211; Users may have issues loading file lists<br \/>\n&#8211; Users may not be able to create new teams &amp; channels<br \/>\n&#8211; Users may not be able to install apps<br \/>\n&#8211; Users may have trouble issuing searches<br \/>\n&#8211; Users may see delays in admin policy changes taking effect<br \/>\n&#8211; Users might see errors when using messaging extensions<br \/>\n&#8211; Users may not see up to date Presence information<br \/>\n&#8211; Teams Graph APIs may be impacted<br \/>\n&#8211; Assignments tab in Teams may not load<br \/>\n&#8211; Teams Admin Center functionalities may not perform as expected<\/p>\n<p>SharePoint Online and OneDrive for Business<br \/>\n&#8211; Users may be unable to use Search functionality<\/p>\n<p>Current status: We've reverted a change which occurred just prior to impact starting and after service replication took place, telemetry is showing significant improvement in availability across the service. Additionally, we've received confirmation from previously impacted users that the issue is no longer occurring. We're continuing to monitor to ensure recovery and are isolating any sections of the service showing residual impact which would require additional recovery actions.<\/p>\n<p>Scope of impact: Impact is specific to users routed through the affected infrastructure.<\/p>\n<p>Next update by: Monday, June 5, 2023, at 6:00 PM UTC<\/p>\n<p>Published Time: 05.06.2023 17:58:00<\/p>\n<p>We've prevented the potentially problematic update from propagating further across the service and are reviewing options to revert the change quickly and safely in those portions of our infrastructure where it has been applied.<\/p>\n<p>This quick update is designed to give the latest information on this issue.<\/p>\n<p>Published Time: 05.06.2023 17:14:38<\/p>\n<p>We've identified an update which was applied around the time that impact started. We're reverting the update to potentially mitigate impact whilst we continue to investigate the underlying cause of the issue.<\/p>\n<p>This quick update is designed to give the latest information on this issue.<\/p>\n<p>Published Time: 05.06.2023 17:09:33<\/p>\n<p>Title: Some users are unable to access Outlook on the web.<\/p>\n<p>User impact: Users are unable to access Outlook on the web.<\/p>\n<p>More info: Additionally, other Microsoft 365 services are also experiencing impact:<br \/>\nMicrosoft Teams<br \/>\n&#8211; Users may have difficulties scheduling meetings and\/or live events<br \/>\n&#8211; Users may have trouble loading people profile cards<br \/>\n&#8211; Users may have issues loading file lists<br \/>\n&#8211; Users may not be able to create new teams &amp; channels<br \/>\n&#8211; Users may not be able to install apps<br \/>\n&#8211; Users may have trouble issuing searches<br \/>\n&#8211; Users may see delays in admin policy changes taking effect<br \/>\n&#8211; Users might see errors when using messaging extensions.<br \/>\n&#8211; Teams Graph APIs may be impacted<\/p>\n<p>Current status: We're continuing to review monitoring health systems targeted at networking, Client Access Front End (CAFE) routing, and database storage to determine the underlying cause of the issue.<\/p>\n<p>Scope of impact: Impact is specific to users routed through the affected infrastructure.<\/p>\n<p>Next update by: Monday, June 5, 2023, at 4:30 PM UTC<\/p>\n<p>Published Time: 05.06.2023 16:52:56<\/p>\n<p>Title: Some users may be unable to access Outlook on the web.<\/p>\n<p>User impact: Users may be unable to access Outlook on the web.<\/p>\n<p>Current status: We're reviewing monitoring telemetry to isolate the source of the issue.<\/p>\n<p>Scope of impact: Impact is specific to users routed through the affected infrastructure.<\/p>\n<p>Next update by: Monday, June 5, 2023, at 4:00 PM UTC<\/p>\n<p>Published Time: 05.06.2023 16:32:40<\/p>\n<p>Title: We're looking into a potential problem.<\/p>\n<p>User Impact: We're investigating the potential end-user impact.<\/p>\n<p>Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.<\/p><\/blockquote>\n<p>Und hier ist der zweite Auszug:<\/p>\n<blockquote><p>Share: Incident: MO572252, impacted service: Microsoft 365 suite, impacted feature: Portal, current status is: Service degradation<\/p>\n<p>Published Time: 05.06.2023 22:11:47<\/p>\n<p>Title: Can't access Outlook on the web and other Microsoft services and features<\/p>\n<p>User impact: Users may be unable to access Outlook on the web or other Microsoft 365 services and features.<\/p>\n<p>More info: Impacted services and features may include, but are not limited to:<br \/>\nExchange Online<br \/>\n&#8211; Users are unable to access Outlook on the web<\/p>\n<p>Microsoft Teams<br \/>\n&#8211; Users may have difficulties scheduling meetings and\/or live events<br \/>\n&#8211; Users may have trouble loading people profile cards<br \/>\n&#8211; Users may have issues loading file lists<br \/>\n&#8211; Users may not be able to create new teams &amp; channels<br \/>\n&#8211; Users may not be able to install apps<br \/>\n&#8211; Users may have trouble issuing searches<br \/>\n&#8211; Users may see delays in admin policy changes taking effect<br \/>\n&#8211; Users might see errors when using messaging extensions<br \/>\n&#8211; Users may not see up to date Presence information<br \/>\n&#8211; Teams Graph APIs may be impacted<br \/>\n&#8211; Assignments tab in Teams may not load<br \/>\n&#8211; Teams Admin Center functionalities may not perform as expected<\/p>\n<p>SharePoint Online, OneDrive for Business, Microsoft Power Automate in Microsoft 365 and Power Apps in Microsoft 365 may also be experiencing some impact related to this issue.<\/p>\n<p>Current status: We've determined that impact associated with MO571683 and EX571516 is reoccurring. We suspect that impact to our services is similar, though we're investigating to determine the scope of impact and the source of the issue.<\/p>\n<p>Scope of impact: Users routed through the affected infrastructure are affected by this issue, however, impact can vary depending on where users are hosted.<\/p>\n<p>Next update by: Monday, June 5, 2023, at 9:00 PM UTC<\/p>\n<p>Published Time: 05.06.2023 19:57:28<\/p>\n<p>Title: Some users experienced impact to multiple Microsoft 365 services and features<\/p>\n<p>User impact: Users experienced impact to multiple Microsoft 365 services and features.<\/p>\n<p>More info: Impacted services and features include, but were not limited to:<br \/>\nExchange Online<br \/>\n&#8211; Users were unable to access Outlook on the web (as communicated under EX571516)<\/p>\n<p>Microsoft Teams<br \/>\n&#8211; Users may have had difficulties scheduling meetings and\/or live events<br \/>\n&#8211; Users may have had trouble loading people profile cards<br \/>\n&#8211; Users may have had issues loading file lists<br \/>\n&#8211; Users may have been unable to create new teams &amp; channels<br \/>\n&#8211; Users may have been unable to install apps<br \/>\n&#8211; Users may have experienced issues performing searches<br \/>\n&#8211; Users may have seen delays in admin policy changes taking effect<br \/>\n&#8211; Users might have seen errors when using messaging extensions<br \/>\n&#8211; Users may have been unable to view up to date Presence information<br \/>\n&#8211; Teams Graph APIs may have been impacted<br \/>\n&#8211; Assignments tab in Teams may have not loaded<br \/>\n&#8211; Teams Admin Center functionalities were not performing as expected<\/p>\n<p>SharePoint Online and OneDrive for Business<br \/>\n&#8211; Users may have been unable to use Search functionality<\/p>\n<p>Microsoft Power Automate in Microsoft 365<br \/>\n&#8211; Users were unable to trigger flows using Office 365 connectors in Microsoft Power Automate<\/p>\n<p>Power Apps in Microsoft 365<br \/>\n&#8211; Users were unable to run apps in Power Apps that utilize Office 365 connectors<br \/>\n&#8211; Flows using the Office 365 Groups, Groups Mail, Outlook, Users, and Videos connectors may have been impacted<\/p>\n<p>Final status: We've completed the restarts to address the residual impact, and after an extended period of monitoring, we've confirmed that the issue is resolved. We continue to investigate why the update caused impact and further details will be provided within the Post-Incident Report.<\/p>\n<p>Scope of impact: Impact was primarily to users hosted within infrastructure that received the update prior to the deployment halt. However, any user may have experienced some degree of impact as described in the \"More Info\" section above and in Service Health Dashboard post MO571683.<\/p>\n<p>Start time: Monday, June 5, 2023, at 2:10 PM UTC<\/p>\n<p>End time: Monday, June 5, 2023, at 5:13 PM UTC<\/p>\n<p>Preliminary root cause: A recent update, intended to add additional resilliencies against downstream request remaining in a hanging state, inadvertently caused impact.<\/p>\n<p>Next steps:<br \/>\n&#8211; We're reviewing dump files gathered from impacted components during the incident to better understand why impact occurred.<br \/>\n&#8211; We're investigating to content of the update to identify the underlying root cause.<\/p>\n<p>We'll publish a Post-Incident report within five business days.<\/p>\n<p>Published Time: 05.06.2023 19:07:52<\/p>\n<p>Telemetry indicates that service availability is at approximately 99.9% across the service. We're continuing to isolate a small number of components which remain in an unhealthy state and are performing targeted restarts to remediate the residual impact.<\/p>\n<p>This quick update is designed to give the latest information on this issue.<\/p>\n<p>Published Time: 05.06.2023 18:21:37<\/p>\n<p>Title: Some users are experiencing impact to multiple Microsoft 365 services and features<\/p>\n<p>User impact: Users are experiencing impact to multiple Microsoft 365 services and features.<\/p>\n<p>More info: Impact services and features include, but are not limited to:<br \/>\nExchange Online<br \/>\n&#8211; Users are unable to access Outlook on the web (as communicated under EX571516)<\/p>\n<p>Microsoft Teams<br \/>\n&#8211; Users may have difficulties scheduling meetings and\/or live events<br \/>\n&#8211; Users may have trouble loading people profile cards<br \/>\n&#8211; Users may have issues loading file lists<br \/>\n&#8211; Users may not be able to create new teams &amp; channels<br \/>\n&#8211; Users may not be able to install apps<br \/>\n&#8211; Users may have trouble issuing searches<br \/>\n&#8211; Users may see delays in admin policy changes taking effect<br \/>\n&#8211; Users might see errors when using messaging extensions<br \/>\n&#8211; Users may not see up to date Presence information<br \/>\n&#8211; Teams Graph APIs may be impacted<br \/>\n&#8211; Assignments tab in Teams may not load<br \/>\n&#8211; Teams Admin Center functionalities may not perform as expected<\/p>\n<p>SharePoint Online and OneDrive for Business<br \/>\n&#8211; Users may be unable to use Search functionality<\/p>\n<p>Current status: We've reverted a change which occurred just prior to impact starting and after service replication took place, telemetry is showing significant improvement in availability across the service. Additionally, we've received confirmation from previously impacted users that the issue is no longer occurring. We're continuing to monitor to ensure recovery and are isolating any sections of the service showing residual impact which would require additional recovery actions.<\/p>\n<p>Scope of impact: Impact is specific to users routed through the affected infrastructure.<\/p>\n<p>Next update by: Monday, June 5, 2023, at 6:00 PM UTC<\/p>\n<p>Published Time: 05.06.2023 17:58:21<\/p>\n<p>We've identified an update which was applied around the time that impact started. We've prevented the potentially problematic update from propagating further across the service and are reviewing options to revert the change quickly and safely in those portions of our infrastructure where it has been applied.<\/p>\n<p>This quick update is designed to give the latest information on this issue.<\/p>\n<p>Published Time: 05.06.2023 17:29:32<\/p>\n<p>Title: Some users are experiencing impact to multiple Microsoft 365 services and features<\/p>\n<p>User impact: Users are experiencing impact to multiple Microsoft 365 services and features.<\/p>\n<p>More info: Impact services and features include, but are not limited to:<br \/>\nExchange Online<br \/>\n&#8211; Users are unable to access Outlook on the web (as communicated under EX571516)<\/p>\n<p>Microsoft Teams<br \/>\n&#8211; Users may have difficulties scheduling meetings and\/or live events<br \/>\n&#8211; Users may have trouble loading people profile cards<br \/>\n&#8211; Users may have issues loading file lists<br \/>\n&#8211; Users may not be able to create new teams &amp; channels<br \/>\n&#8211; Users may not be able to install apps<br \/>\n&#8211; Users may have trouble issuing searches<br \/>\n&#8211; Users may see delays in admin policy changes taking effect<br \/>\n&#8211; Users might see errors when using messaging extensions.<br \/>\n&#8211; Teams Graph APIs may be impacted<\/p>\n<p>SharePoint Online and OneDrive for Business<br \/>\n&#8211; Users may be unable to use Search functionality<\/p>\n<p>Current status: We're reviewing monitoring health systems targeted at networking, Client Access Front End (CAFE) routing, and database storage to determine the underlying cause of the issue.<\/p>\n<p>Scope of impact: Impact is specific to users routed through the affected infrastructure.<\/p>\n<p>Next update by: Monday, June 5, 2023, at 4:30 PM UTC<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>[English]Zum 5. Juni 2023 hat es bei Microsofts Exchange Online wohl eine massivere St\u00f6rung gegeben. Administratoren kamen nicht mehr ins Admin-Center und Outlook konnte im Web nicht mehr erreicht werden. Ein Nutzer hat mich auf diese St\u00f6rung hingewiesen, die kurz &hellip; <a href=\"https:\/\/borncity.com\/blog\/2023\/06\/05\/exchange-online-strung-5-juni-2023\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/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,8387,987],"class_list":["post-282177","post","type-post","status-publish","format-standard","hentry","category-cloud","category-stoerung","tag-cloud","tag-exhange-online","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/282177","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=282177"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/282177\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=282177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=282177"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=282177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}