A Microsoft 365 outage disrupted email, collaboration tools, and cloud services worldwide after server failures spread across the company’s infrastructure Thursday, Nov. 12. Engineers still had not identified the underlying cause.
The disruption initially affected customers in the United States and other parts of the Americas before expanding internationally. Outlook and Microsoft Teams were among the first services affected, followed by several other business and consumer applications.
Microsoft reported that many servers had unexpectedly become unavailable. The failures interrupted access to services used for workplace communication, document management, security monitoring and device administration.
Microsoft 365 Outage Spreads Across Cloud Services
What initially appeared to be an email disruption developed into a broader infrastructure incident. Customers had trouble accessing Outlook, Teams, and cloud-based files and documents.
The outage also affected Microsoft Copilot, the company’s AI assistant, and Defender security services. Some administrators could not access Microsoft Intune dashboards or management features, limiting their ability to oversee devices and security settings.
Reports also indicated that some customers had difficulty connecting to Windows computers hosted in the cloud. The extent of those disruptions remains unclear.
The range of affected products raised concerns about dependencies within Microsoft’s cloud infrastructure. A failure affecting shared systems can interrupt several applications even when those services perform different functions.
Microsoft continued investigating why so many servers became unavailable. The company had not publicly identified a specific software defect or infrastructure component responsible for the incident.
Outlook Recovery Begins After 18 Hours
Signs of recovery appeared Friday morning as email traffic began returning to Microsoft’s systems.
Doug Madory, director of internet analysis at network monitoring company Kentik, reported that Exchange Online traffic had fallen approximately 85% below expected levels for about 18 hours.
In a Bluesky update, Madory said traffic began climbing sharply at 6:20 a.m. Eastern time Friday. The increase represented the strongest improvement observed since the disruption began.
The recovery indicated that Microsoft’s email infrastructure was becoming accessible again. However, improving network traffic did not establish that every affected service or customer had returned to normal operation.
Microsoft’s official service health page provides information about disruptions and recovery efforts. In its Friday update, the company said it had found no evidence connecting the incident to malicious activity.
That assessment did not establish the cause of the failures. Microsoft continued investigating the technical problem while restoring access to affected systems.
Microsoft Faces Another Major Cloud Disruption
The latest incident follows a separate Microsoft 365 outage in September that disrupted Outlook, authentication and other workplace applications over several days.
During that disruption, Microsoft identified a problem involving a core authentication configuration. The issue prevented authentication components from deploying correctly across parts of its infrastructure.
TechAmerica previously reported on the September Microsoft 365 outage, including the extended recovery efforts affecting Outlook and other enterprise services.
The November incident has not been linked to that earlier configuration problem. Microsoft has not established that the two outages share a technical cause.
The latest disruption also demonstrated the operational difficulties businesses face when multiple essential applications depend on the same cloud provider. Email, collaboration, security monitoring and device management can become unavailable during a widespread infrastructure failure.
Investigating such incidents requires engineers to distinguish the initial failure from problems that spread through connected systems. TechAmerica’s analysis of software outage investigations explains how logs, system metrics and service dependencies help technical teams identify possible causes.
For Microsoft, the immediate priority remains confirming that services have recovered and determining why the servers failed. The company reported improved availability by Friday morning, but had not announced a verified root cause or a complete recovery timeline.
