Microsoft has explicitly ruled out malicious activity as the cause, stating in official updates that there is “no evidence of malicious activity associated with this incident.” The disruption has hampered everyday operations for major businesses and personal accounts across the United States and globally. Key technical impacts include the inability to view recently used files in Word, Excel, and PowerPoint, as well as blocked external file sharing. The Copilot assistant, integrated across Microsoft 365, remains heavily disrupted, preventing users from accessing data from their emails, calendars, and files.
Recovery efforts are progressing unevenly across different regions. In service updates issued at 6 a.m. and 7 a.m. ET on Friday, Microsoft reported recovery progress across Europe and the Asia Pacific region, noting that Japan remained “comparatively more stable.” Services in North America were also improving by 7 a.m., though the company cautioned that some users may continue to experience intermittent issues as recovery actions continue. Engineers are actively working to clear email queues and backlogs that accumulated during the initial disruption.
To mitigate data loss during the extended downtime, Microsoft extended its email timeout window to 48 hours. This technical adjustment protects delayed messages from being bounced back to senders, which would normally occur if delivery fails within the standard timeframe. Consequently, emails caught in the backlog since the outage began Thursday afternoon have until at least Saturday afternoon to reach recipients once systems fully recover. This measure ensures that business-critical communications are not permanently lost during the recovery period.
The incident highlights the critical reliance on Microsoft’s ecosystem for modern corporate workflow. While the company has not announced a specific completion time for full restoration, the distinction between regional stability and global recovery suggests a phased restoration process. Users in North America and other affected areas should anticipate continued intermittent issues until the backlog is fully cleared and standard service levels are restored. The situation underscores the fragility of centralized cloud infrastructure, where a single point of failure can cascade into multi-day disruptions for global operations.
