Microsoft outage caused by old bug took Teams and Outlook offline
Microsoft has blamed a months-old bug, a failing network gateway and reduced server capacity for an outage that hit businesses, hospitals, government agencies and other groups worldwide.

Key takeaways
- Microsoft identified three combined causes: a gateway not working for Teams, reduced capacity and a hidden bug.
- The bug had been present in Microsoft's systems since July, which made a quick rollback impossible.
- Close to 14 percent of the affected gateway's capacity was already offline from an unrelated problem the day before.
- The findings come from a preliminary report, with a fuller final report promised later this week.
What Microsoft says happened
Microsoft has shared fresh details about the Microsoft outage that took services such as Outlook, Teams and Copilot 365 offline for almost a day. According to Engadget, the company has traced the disruption to three separate problems that came together to overwhelm its systems.
Charles Lamanna, the executive vice president who oversees Copilot and AI Agents, set out the causes in a post on X. He said the failure was not the result of a single fault but of several issues that lined up at the same time.
How the failure spread

Microsoft normally runs two network gateways that link different systems and let data move between them. One of these gateways was not working for Teams, so it pushed extra traffic onto the main gateway. At the same time, close to 14 percent of that gateway's capacity was already offline because of a separate problem the day before.
Those two issues exposed a hidden bug that had been sitting in the company's systems since July. The extra load, the lost capacity and the bug together caused requests to pile up until the servers gave out. The trouble struck on a Thursday, when demand from users in the United States was at its highest.
Who was affected
The disruption reached hospitals, businesses, law enforcement agencies and other groups around the world. Governments were also among those affected, according to Engadget. Because the problems began during busy hours in the United States, the timing made the impact harder for many organisations.
What happens next
Microsoft engineers worked through the night to restore service. But the bug had been in place for months, so the company could not simply roll back the changes to fix things quickly. When the servers returned, they were flooded with queued requests and stopped responding once more.
The outage ran for close to a full day. Lamanna apologised, saying the company was deeply sorry for the disruption to customers and their day-to-day operations. These findings come from a preliminary report, and Microsoft said a fuller final report would follow later this week.
Sources
Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.



