Why were Outlook and Teams down? Microsoft shares outage details Microsoft's Exchange Online, Outlook, Teams, SharePoint and Microsoft 365 Copilot services were disrupted across 74 countries starting Thursday, November 12, according to the Associated Press, in an outage Microsoft attributed in a preliminary incident report to an unknown bug present since July 2026 in a Windows process on its network servers. Microsoft said the fault went undetected because testing ran primarily on less powerful servers, and that it was triggered when Teams traffic was routed to Exchange Online infrastructure about 15 hours before the outage while nearly 14 percent of server capacity was unavailable; within two hours more than 80 percent of affected servers stopped responding. Microsoft confirmed the incident was not caused by a cyberattack or AI agents and said it will publish a final report with preventive measures on November 20th. The disruptions to Microsoft’s services began on Thursday, November 12th and continued into Friday. The issues affected several of Microsoft’s most widely used cloud services, including Exchange Online, Outlook, Teams, SharePoint, and Microsoft 365 Copilot. For many users, the outage meant they were unable to read or send emails, or use certain features in Teams. Organizations that rely on Microsoft 365 for their day-to-day operations were also affected. According to the AP news agency https://apnews.com/article/e2330e733db280805dbf7e3eb29ee0e1 , disruptions were reported across 74 countries. According to Microsoft’s preliminary incident report PDF https://www.365fanatic.com/wp-content/uploads/2026/11/PostIncidentReport.pdf , the problems were caused by an unknown bug that had been present since July 2026, reports Cyber Security News https://cybersecuritynews.com/microsoft-outage-incident-report . The fault was found in a Windows process on the company’s network servers, causing them to become overloaded under certain conditions. The processor and RAM were subjected to increasing strain until the servers stopped responding. Microsoft states that the fault was not detected during testing because those tests were primarily carried out on less powerful servers. The problem became more severe on modern hardware with multiple processor cores. The bug was specific to Microsoft’s server infrastructure and should not affect standard Windows computers. Around 15 hours before the outage, Teams traffic was automatically routed to the same network infrastructure that handles Exchange Online. At the same time, nearly 14 percent of server capacity was unavailable. The combination of increased load and reduced capacity triggered the previously undetected software fault. When the servers stopped responding, Microsoft’s automated system attempted to redirect traffic to functioning servers. However, these too became overloaded, creating a chain reaction. Within two hours, more than 80 percent of the affected servers had stopped responding. Even the protective mechanisms normally designed to limit disruptions between different parts of the infrastructure failed. Microsoft initially attempted to restart the affected servers, but when traffic returned, they quickly became overloaded again. The company’s technicians had to develop an update that restored the previously functioning code. Once applied, the servers could be restarted and traffic gradually restored. Microsoft states that it has processed the emails that were held up in queues during the outage, and previously confirmed that the incident was not caused by a cyberattack or AI agents. The incident report is still preliminary. Microsoft plans to publish its final report, including further measures to prevent similar outages, on November 20th.