{"id":323779,"date":"2026-04-16T16:01:54","date_gmt":"2026-04-16T14:01:54","guid":{"rendered":"https:\/\/borncity.com\/blog\/?p=323779"},"modified":"2026-04-16T16:02:25","modified_gmt":"2026-04-16T14:02:25","slug":"microsoft-365-stoerung-bei-google-chrome-15-4-2026","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2026\/04\/16\/microsoft-365-stoerung-bei-google-chrome-15-4-2026\/","title":{"rendered":"Microsoft 365: St\u00f6rung bei Google Chrome (15.4.2026)"},"content":{"rendered":"

\"StopKurze Information f\u00fcr Administratoren von Microsoft 365-Instanzen. Falls Benutzer sich \u00fcber Probleme mit dem Chrome-Browser beschweren, liegt an Microsoft bzw. an Chrome (einem Zertifikat wird nicht mehr vertraut). In diesem Tweet<\/a> hat Microsoft vor einer Stunde mitgeteilt, dass man derzeit ein Problem beim Zugriff auf bestimmte webbasierte Microsoft 365-Dienste bei Verwendung der neuesten Version von Google Chrome untersuche. Man will inzwischen das Problem behoben haben.<\/p>\n

<\/p>\n

\"\"Auf reddit.com gibt es seit 7 Stunden diesen Thread<\/a> zum Thema, und der Thread-Starter schreibt:<\/p>\n

Hat noch jemand Probleme, dass purview.microsoft.com und security.microsoft.com\/ nicht mit Chrome 147.0.7727.102 laden?<\/p>\n

Beide Seiten funktionieren einwandfrei in Firefox 149.0.2 und Edge 147.0.3912.60, aber Chrome 147.0.7727.102 l\u00e4dt nur eine leere Seite.<\/p>\n

intune.microsoft.com\/ funktioniert in allen drei Browsern einwandfrei, ebenso wie entra.microsoft.com\/<\/p><\/blockquote>\n

Details zur Microsoft-Meldung finden sich angeblich auf der Microsoft 365-Statusseite<\/a> (da finde ich aber nichts) oder im Microsoft 365 Admin Center\u00a0unter MO1281730<\/a>. Der mir zug\u00e4ngliche Spiegel-Server sagt dazu:<\/p>\n

MO1281730 – Users may have been unable to access Microsoft 365 web-based services correctly when using Google Chrome<\/p>\n

Status: serviceRestored
\nStart Time: Wed Apr 15 15:00:00 2026
\nEnd Time: Thu Apr 16 07:56:00 2026
\nService: Microsoft 365 suite
\nFeature Group: Portal
\nClassification: incident
\nLast Updated: Thu Apr 16 09:23:33 2026
\nRoot Cause: N\/A
\nNext Update: N\/A
\ncollapse section Details<\/p>\n

Time: Thu Apr 16 09:21:11 2026
\nDescription: Title: Users may have been unable to access Microsoft 365 web-based services correctly when using Google Chrome<\/p>\n

User impact: Users may have been unable to access Microsoft 365 web-based services correctly when using Google Chrome.
\nMore info: Impacted users may have experienced Microsoft 365 web apps and portals not rendering as expected when accessed via the Google Chrome browsers. This may have included, but was not limited to: – Microsoft 365 admin center failing to load or missing UI elements such as search bars or pages – An inability to open Excel or PowerPoint files through Microsoft 365 web pages – Issues accessing apps such as OneDrive and Planner through the browser<\/p>\n

This issue only impacted the latest version of Google Chrome (Version 147). Other browsers, including Microsoft Edge, were unaffected. As a workaround, impacted users could have used the Microsoft Edge browser.<\/p>\n

Additionally, desktop based clients were unaffected, and users may have been able to leverage these services.<\/p>\n

Final status: We've completed the mitigation actions, and telemetry showed that the issue is resolved. Users may need to refresh their browser pages to experience relief.<\/p>\n

Scope of impact: Some users attempting to access Microsoft 365 web-based services via Google Chrome (version 147) may have been impacted.<\/p>\n

Start time: Wednesday, April 15, 2026, at 7:00 PM UTC
\nEnd time: Thursday, April 16, 2026, at 11:56 AM UTC<\/p>\n

Preliminary root cause: As part of broad changers related to DigiCert Global Root CA (G1), Google Chrome no longer trusts these authentication configurations (more information can be found here<\/a>). In preparation, most Microsoft 365 web-based services had transitions to an alternate authentication configuration authorities, however, a small number were not fully addressed. Once the Google Chrome change occurred, the authentication configurations were no longer accepted, resulting in impact.<\/p>\n

Next steps: – We're investigating why some services had not fully transitioned off the specific authentication configurations.
\nWe'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.<\/p><\/blockquote>\n

Inzwischen schreibt Microsoft in diesem Tweet<\/a>, dass man die erforderlichen Ma\u00dfnahmen ergriffen und das Problem behoben habe. Nutzer m\u00fcssen m\u00f6glicherweise ihre Browser-Seiten aktualisieren, damit die \u00c4nderung wirksam wird. F\u00fcr weitere Informationen wird auf MO1281730<\/a> im Admin-Center verwiesen.<\/p>\n","protected":false},"excerpt":{"rendered":"

Kurze Information f\u00fcr Administratoren von Microsoft 365-Instanzen. Falls Benutzer sich \u00fcber Probleme mit dem Chrome-Browser beschweren, liegt an Microsoft bzw. an Chrome (einem Zertifikat wird nicht mehr vertraut). In diesem Tweet hat Microsoft vor einer Stunde mitgeteilt, dass man derzeit … Weiterlesen →<\/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,1356,153,7862],"tags":[406,7377,987],"class_list":["post-323779","post","type-post","status-publish","format-standard","hentry","category-cloud","category-google-chrome-internet","category-microsoft-office","category-stoerung","tag-chrome","tag-microsoft-365","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/323779","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=323779"}],"version-history":[{"count":2,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/323779\/revisions"}],"predecessor-version":[{"id":323781,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/323779\/revisions\/323781"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=323779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=323779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=323779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}