Loading story…
Microsoft experienced a broad service disruption that affected SharePoint, Teams, Excel, the Microsoft 365 Admin Center, and Azure-hosted workloads, with users also reporting failures in Dynamics 365, Dataverse, Entra join operations, and administrative portals. Administrators said SharePoint timeouts, Teams image-loading failures, and unreachable Azure virtual machines were especially visible in West US, Canada West, and parts of US East, while Downdetector recorded a sharp spike in complaints. Microsoft acknowledged the incident and directed customers to service health alert MO1437424, saying it was investigating increased reports and reviewing telemetry to determine scope and impact.
The disruption appeared to extend beyond core collaboration services into dependent platforms and Microsoft-backed update infrastructure. Sysadmins reported Windows Media Creation Tool failures with error 0x80072EE4 - 0x20000, Windows feature enablement errors such as 0x80244022, and Windows Update failures returning 0x801901f7 on newly imaged systems. A separate outage report also indicated KaseyaOne login issues that users linked to the Azure problems, suggesting downstream impact on third-party services hosted on Microsoft infrastructure as customers saw intermittent outages, degraded functionality, and some signs of partial recovery.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
9 events from the most recent confirmed update back to the earliest known activity.
Microsoft said the Microsoft 365 outage tracked as MO1437424 was likely caused by a recent network configuration change affecting primarily North America-routed traffic. The company mitigated the incident by rolling back the change and rerouting traffic across alternate network paths, then reported telemetry showed recovery and marked the service restored.
Users reported Windows Update returning error 0x801901f7 when newly imaged systems attempted to update directly from Microsoft Update. Multiple commenters confirmed the same behavior, indicating a likely service-side disruption rather than isolated local issues.
Reddit users reported Windows Media Creation Tool failures with error 0x80072EE4 - 0x20000, along with Windows feature enablement error 0x80244022 and Windows Update error 0x801901f7. Participants suggested the problems were related to the broader Microsoft or Azure backend outage.
Users reported that images in Microsoft Teams chat were appearing as white boxes instead of loading properly. Commenters tied the issue to active Microsoft service health incident MO1437424 and said clearing the Teams cache did not resolve it.
A Reddit user reported KaseyaOne had been inaccessible for at least an hour in the EU/Merlot region, and a commenter said Kaseya was experiencing an outage. The thread attributed the login-access issue to the ongoing Azure outage, and the original poster later confirmed seeing Kaseya's status page.
Reddit users reported Azure virtual machines in West US were running according to boot diagnostics but were unreachable over RDP, with commenters suggesting broader network connectivity issues. The discussion also mentioned possible impact extending to Azure US East and that Microsoft's status page did not yet reflect the outage.
Microsoft acknowledged the disruption and said it was investigating the outage, directing administrators to service health incident MO1437424 for updates. Reddit users also referenced the incident as covering Teams image-loading failures and broader Microsoft 365 problems.
Downdetector recorded a sharp increase in user reports at 11:11 a.m. ET, reaching 2,403 reports versus a normal baseline of 29. Most complaints involved SharePoint, followed by Excel and the Microsoft 365 Admin Center.
Microsoft later said in incident MO1437424 that it began investigating increased user reports of Microsoft 365 issues after the incident started at 10:06 AM CDT. User reports described impact to SharePoint, Teams, Dynamics 365, Dataverse, Azure-hosted applications, and administrative portals.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
9 references tracked. Mallory keeps watching after this page renders.
cybersecuritynews.com
Open sourcereddit.com
Open sourcebleepingcomputer.com
Open sourcereddit.com
Open sourcereddit.com
Open sourcereddit.com
Open sourcereddit.com
Open sourcereddit.com
Open sourcereddit.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Microsoft reported multiple **service-impacting incidents** across its cloud ecosystem. Administrators in **North America and Canada** experienced an outage and degraded performance in the **Microsoft 365 admin center**, with some users also unable to access the *M365 app* or raise support tickets; Microsoft said it was analyzing telemetry, usage patterns, and **CPU utilization**, and reviewing user-provided **HAR files** to isolate the root cause. Separately, **Exchange Online** quarantined legitimate messages after an updated **URL rule** incorrectly marked some URLs as phishing, disrupting email flow for affected customers while Microsoft worked to release quarantined mail and unblock legitimate URLs. In another disruption, Microsoft attributed **Windows Update** and **Microsoft Store** failures/timeouts (notably impacting Windows 11 users) to a **utility power interruption** at a **West US datacenter**, which cascaded into issues with **Azure storage clusters** supporting content delivery; backup power engaged and power was later stabilized, but service recovery required additional remediation beyond restoring electricity.
Jun 29, 2026
Microsoft Teams experienced widespread outages, with users across the United States, Europe, and other regions reporting delays in sending messages and problems with other service functions. Microsoft acknowledged the issue publicly, stating that they were investigating the cause and observing signs of recovery, but did not initially provide a root cause or timeline for full restoration. The outage disrupted communication for many organizations relying on Teams for collaboration and messaging. Separately, a significant outage affected Microsoft 365 services—including Teams, Outlook, OneDrive, and the Copilot AI assistant—in Japan and China. This disruption was traced to a critical routing misconfiguration in Microsoft's infrastructure, which isolated healthy systems and led to intermittent login failures, degraded performance, and app loading errors. Microsoft confirmed that the incident was not the result of a cyberattack and reported that engineers had rebalanced traffic to restore service, with no data loss or security breaches identified. The outages caused notable business disruption in the affected regions, particularly for organizations dependent on Microsoft’s cloud ecosystem for daily operations.
Jun 29, 2026
Microsoft reported a **Microsoft 365 service disruption in North America** that affected access to multiple services, including the **Microsoft 365 Admin Center**, limiting administrators’ ability to manage users and view service health/security posture. Microsoft’s investigation, tracked via the Microsoft 365 admin center and service health communications, pointed to a likely **Content Delivery Network (CDN) configuration issue** as the root cause, with engineers iterating through telemetry review and narrowing the suspected trigger to CDN configuration. Amazon also experienced a **partial outage** affecting customer shopping workflows, with widespread user reports of problems loading product pages, using the mobile app, and especially **checkout/add-to-cart** functionality across major US cities. Amazon acknowledged the disruption publicly and stated it was working to resolve the issue, while the underlying cause was not yet confirmed at the time of reporting.
Jun 29, 2026