← All stories
● Covered by 13 sources · 30 reportsMedium impact8 negative22 neutral

Microsoft 365 Services, Including Outlook and Teams, Experience Widespread Outage

🔄 Updated 4d ago — new reporting from Guardian Technology
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Multiple Microsoft 365 services, including Outlook and Teams, were affected.
  • The outage began Thursday, November 12, impacting users globally.
  • Microsoft attributed the issue to unexpectedly unavailable servers causing elevated load.
  • Downdetector reported over 100,000 Outlook outage reports at its peak.
  • Microsoft implemented alternative health check methods to restore server availability.
  • Microsoft's AI software Copilot was also affected by the outage.
  • The outage impacted users in 74 countries and territories.
  • The disruption affected banks, governments, and courts globally.
  • The outage affected AI companies OpenAI and Anthropic.
  • The outage began around 6 PM GMT on Thursday.
  • The outage lasted nearly 24 hours.
  • Japanese workers used fax machines during the outage.
  • The outage affected Microsoft Defender security software.
  • The outage affected system administrators' Intune dashboards.
  • Some users experienced issues accessing cloud-based Windows computers.
  • Microsoft extended email timeout to 48 hours to preserve delayed mail.
  • The outage was caused by a technical issue during a network capacity upgrade.
  • The outage affected 430 million users.
  • The outage was caused by routine automated checks that took some servers offline.
  • The outage affected Miami, Maryland, and Los Angeles.
  • Arapahoe County detention facility could not take online bond payments.
  • Los Angeles County Sheriff's Department experienced email disruptions.
  • Emergency services in Fredericksburg and Gillespie County, Texas, could not receive emails.
  • The outage was fully restored by Saturday morning.
  • The outage affected healthcare services, businesses, and airlines.
  • The outage affected governments in Japan, Singapore, and Australia.
  • NHS England hospital staff resorted to paper records.
  • Ambulance services in the UK suffered a serious impact.
  • The UK court system was hit, sending juries home.
  • 15 hotel guests in Germany suffered chlorine gas poisoning due to the outage.
  • A sauna's safety system failed to send email alerts about high chlorine levels.
  • German emergency services deployed 40 first responders to the hotel.
  • Four victims were hospitalized, with one remaining for observation.
  • Microsoft confirmed the outage was not a cyberattack.
  • Microsoft Threat Intelligence observed a phishing campaign exploiting the disruption.
  • Phishing emails posed as Microsoft 365 service health notices.
  • Phishing emails referred to the actual incident identifier EX1550543.
  • The Exchange Online incident EX1550543 was marked resolved on November 13.
  • A software bug introduced in July caused the outage.
  • Over 80% of networking gateway servers became unresponsive.
  • The outage began at 11:20 AM ET on Thursday, November 12.
  • The outage continued until 11:10 AM ET the following day.
  • The outage was caused by a previously undetected software bug, increased traffic after a Microsoft Teams failover, and reduced server capacity.
  • The bug was in an update for Microsoft 365 networking gateway servers.
  • The outage is covered in Microsoft's incident IDs EX1550543 and MO1550821.
  • The outage was from November 12 at 16:20 UTC to November 13 at 16:10 UTC.
  • The outage was caused by a months-old bug, malfunctioning internal connections, and reduced server capacity.
  • The outage began with US users reporting interrupted access to Outlook email accounts.
  • Jails could not release prisoners due to the outage.
  • Schools lost contact with parents due to the outage.
  • Police departments could not receive crime reports due to the outage.
  • Charles Lamanna, executive vice-president, posted on X about the outage.

Widespread Service Disruption

On Thursday, November 12, numerous Microsoft 365 services experienced a significant outage. Users globally reported issues accessing critical platforms such as Outlook, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot, OneDrive, and Microsoft Defender XDR. Downdetector recorded over 100,000 reports for Outlook alone at the peak of the incident.

Cause Identified as Server Unavailability

Microsoft confirmed the outage, initially noting elevated load across multiple regions. Further investigation revealed that a large number of servers became unexpectedly unavailable, which shifted the traffic load onto the remaining infrastructure. The company stated that the elevated load was not due to an overall increase in traffic but rather the reduced capacity of its server fleet.

Impact Across Microsoft Ecosystem

The outage affected both business and consumer users, preventing access to email, video conferencing, file sharing, and AI tools. While initial reports focused on Outlook, the scope expanded to include a broad range of Microsoft 365 applications. Some users also reported difficulty accessing Microsoft's own service status page during the incident.

Microsoft's Response and Resolution Efforts

Microsoft actively investigated the cause, pausing all deployments and configuration changes as a precaution. The company identified that affected servers were failing automated health checks and were experiencing elevated processor usage. Microsoft deployed targeted changes to bypass the problematic component responsible for these health checks and validated an alternative service health check method, which was then applied more broadly to bring affected servers back online and restore service capacity.

Updates

🕒 2026-11-17 · new reporting from Guardian Technology
  • The outage was caused by a months-old bug, malfunctioning internal connections, and reduced server capacity.
  • The outage began with US users reporting interrupted access to Outlook email accounts.
  • Jails could not release prisoners due to the outage.
  • Schools lost contact with parents due to the outage.
  • Police departments could not receive crime reports due to the outage.
  • Charles Lamanna, executive vice-president, posted on X about the outage.
🕒 2026-11-16 · new reporting from BleepingComputer, Ars Technica
  • A software bug introduced in July caused the outage.
  • Over 80% of networking gateway servers became unresponsive.
  • The outage began at 11:20 AM ET on Thursday, November 12.
  • The outage continued until 11:10 AM ET the following day.
  • The outage was caused by a previously undetected software bug, increased traffic after a Microsoft Teams failover, and reduced server capacity.
  • The bug was in an update for Microsoft 365 networking gateway servers.
  • The outage is covered in Microsoft's incident IDs EX1550543 and MO1550821.
  • The outage was from November 12 at 16:20 UTC to November 13 at 16:10 UTC.
🕒 2026-11-16 · new reporting from SecurityWeek
  • Microsoft confirmed the outage was not a cyberattack.
  • Microsoft Threat Intelligence observed a phishing campaign exploiting the disruption.
  • Phishing emails posed as Microsoft 365 service health notices.
  • Phishing emails referred to the actual incident identifier EX1550543.
  • The Exchange Online incident EX1550543 was marked resolved on November 13.
🕒 2026-11-15 · new reporting from Tom's Hardware
  • 15 hotel guests in Germany suffered chlorine gas poisoning due to the outage.
  • A sauna's safety system failed to send email alerts about high chlorine levels.
  • German emergency services deployed 40 first responders to the hotel.
  • Four victims were hospitalized, with one remaining for observation.
🕒 2026-11-14 · new reporting from Guardian Technology
  • The outage was fully restored by Saturday morning.
  • The outage affected healthcare services, businesses, and airlines.
  • The outage affected governments in Japan, Singapore, and Australia.
  • NHS England hospital staff resorted to paper records.
  • Ambulance services in the UK suffered a serious impact.
  • The UK court system was hit, sending juries home.
🕒 2026-11-14 · new reporting from Guardian Technology
  • The outage affected Miami, Maryland, and Los Angeles.
  • Arapahoe County detention facility could not take online bond payments.
  • Los Angeles County Sheriff's Department experienced email disruptions.
  • Emergency services in Fredericksburg and Gillespie County, Texas, could not receive emails.
🕒 2026-11-13 · new reporting from BBC Technology, Tom's Hardware, TechCrunch, SecurityWeek, Ars Technica, The Verge, Engadget
  • The outage lasted nearly 24 hours.
  • Japanese workers used fax machines during the outage.
  • The outage affected Microsoft Defender security software.
  • The outage affected system administrators' Intune dashboards.
  • Some users experienced issues accessing cloud-based Windows computers.
  • Microsoft extended email timeout to 48 hours to preserve delayed mail.
  • The outage was caused by a technical issue during a network capacity upgrade.
  • The outage affected 430 million users.
  • The outage was caused by routine automated checks that took some servers offline.
🕒 2026-11-13 · new reporting from BBC Technology, Hacker News Front Page, Guardian Technology
  • Microsoft's AI software Copilot was also affected by the outage.
  • The outage impacted users in 74 countries and territories.
  • The disruption affected banks, governments, and courts globally.
  • The outage affected AI companies OpenAI and Anthropic.
  • The outage began around 6 PM GMT on Thursday.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

How outlets covered it

Microsoft 365 experienced a nearly 24-hour outage last week, affecting its cloud and Exchange infrastructure. A preliminary report attributes the incident to a latent bug in the cloud gateway, changes in network traffic, and reduced server capacity, which collectively led to resource exhaustion.

Microsoft identified a latent bug from July, malfunctioning network gateways, and reduced server capacity as the root causes of a global outage affecting Outlook, Exchange, and other Office 365 services last week. The combination of these factors led to servers becoming overwhelmed and unresponsive, prolonging recovery efforts. This incident highlights the complexities of maintaining large-scale cloud infrastructure and the impact of cascading failures.

A software bug introduced in July caused a nearly 24-hour global Microsoft 365 outage on November 12, affecting services like Outlook, Exchange Online, Teams, and Copilot. The bug, combined with increased traffic from a Teams failover and reduced server capacity, led to over 80% of networking gateway servers becoming unresponsive. This incident highlights challenges in detecting latent software defects under specific production conditions.

Microsoft confirmed its November 12 Microsoft 365 outage, which affected Exchange Online and other services, was due to a technical issue from a network capacity upgrade, not a cyberattack. Following the disruption, Microsoft Threat Intelligence observed a phishing campaign using fake service notifications to trick users into clicking malicious links.

A Microsoft 365 outage led to 15 hotel guests in Germany suffering chlorine gas poisoning after a sauna's safety system, which relied on email alerts for high chlorine levels, failed to send warnings. The incident highlights risks associated with critical safety systems depending solely on cloud services without analog backups.

Microsoft announced that its services have been fully restored following a global outage that began on Thursday. The disruption impacted governments, businesses, and public services worldwide, including critical operations in healthcare, courts, and national security agencies across multiple countries.

A Microsoft 365 outage, lasting more than 22 hours, disrupted services like Outlook for 430 million users across 70 countries. The disruption was caused by routine automated checks that overloaded servers, highlighting the reliance of businesses and institutions on major tech firms.

Microsoft experienced a global outage affecting services like Outlook and Teams for almost 24 hours, impacting over 70 countries and 430 million users. The company attributed the disruption to a technical issue during a network capacity upgrade, not a cyberattack or AI agents. Services were largely recovering, but full restoration timing was unknown.

A Microsoft Outlook outage, starting Thursday afternoon, affected email, calendar, video conferencing, and cloud storage systems for various organizations across the US. The disruption impacted local governments, schools, and businesses, causing delays in services and communication issues. While some services began to resume Friday morning, many entities reported ongoing difficulties.

A Microsoft 365 outage on Thursday affected services like Teams, Outlook, and Copilot across at least 74 countries, causing widespread connectivity problems. The disruption impacted US government operations, major tech companies like OpenAI, healthcare networks in Canada, and city services globally, highlighting reliance on Microsoft's cloud infrastructure.

Microsoft 365 services, including Outlook, Teams, and Copilot 365, experienced a widespread outage that disrupted businesses and organizations globally. Services are now gradually returning online after Microsoft addressed an issue during a network capacity upgrade.

Microsoft Outlook and 365 services are recovering after an almost two-day global outage that affected millions of users. Microsoft stated the issue was a technical problem during a network capacity upgrade, not related to cyberattack or AI, and services are being gradually restored.

Microsoft 365 services, including email, cloud, and AI, experienced a global outage starting Thursday and continuing into Friday. The disruption affected numerous organizations worldwide, from businesses and hospitals to government infrastructure, hindering critical operations like bank transfers and legal work. Microsoft extended email timeouts to 48 hours to preserve delayed mail and stated there was no evidence of malicious activity.

Microsoft experienced a global outage affecting its 365 services, including Outlook, Teams, and Copilot, for several hours. The disruption impacted users, companies, and government operations from Asia to the U.S., with Microsoft reporting ongoing recovery efforts and variable service health.

Microsoft experienced a day-long global outage affecting Outlook, Teams, Copilot AI tools, Defender security software, and cloud services for consumers and businesses. The issue, which began Thursday, was attributed to a cascading software problem causing a large number of servers to become unexpectedly unavailable, with recovery efforts ongoing as of Friday morning.

A Microsoft 365 outage, lasting nearly 24 hours, disrupted services like Outlook, Teams, and Copilot for businesses globally, including 78% of Japanese companies. Some Japanese workers resorted to using fax machines to continue operations during the downtime. Microsoft reported recovery progress in Europe and America, denying a cybersecurity breach as the cause.

Microsoft services, including Teams, Outlook, and Copilot, experienced an outage due to higher-than-usual stress on its servers. Microsoft reported early signs of stabilization as work on a fix continued.

Microsoft experienced a widespread outage affecting services like Outlook, Teams, and Copilot globally, impacting government agencies, businesses, and public services including the NHS. The disruption, which began Thursday evening GMT, is attributed to server settings issues, not a cyberattack, with recovery efforts showing incremental improvement but services not fully restored.

Microsoft 365 services, including Outlook, Teams, and Copilot, experienced a global outage due to an "elevated load" on its infrastructure, not a cyber-security incident. The disruption affected millions of users across 74 countries, including government agencies and other tech companies like OpenAI. Microsoft reported that a large number of servers became unexpectedly unavailable, leading to increased traffic on remaining servers.

Microsoft is experiencing a global outage impacting services such as Teams, Outlook, and Copilot due to "connectivity problems." The disruption is reported to affect users in 74 countries, with Microsoft working to resolve the issues.

Microsoft services, including Outlook email and Teams, experienced a global outage lasting over 12 hours, impacting millions of users across 74 countries. The disruption affected banks, governments, and courts, with Microsoft stating the issue was not a cybersecurity breach.

Microsoft services including Teams, Outlook, and Copilot experienced a global outage affecting tens of thousands of users due to unexpected server unavailability. The disruption impacted Microsoft 365 users, including businesses and AI companies like OpenAI and Anthropic, highlighting the critical reliance on Microsoft's infrastructure.

Microsoft 365 services, including Outlook and Teams, experienced a widespread outage on Thursday, affecting thousands of users. Microsoft attributed the issue to an elevated load caused by unexpectedly unavailable servers and failing automated health checks. The company implemented an alternative service health check method and began applying it more broadly to restore services.

Microsoft 365 experienced a widespread outage, disrupting access to Exchange Online, Teams, SharePoint Online, Copilot, and Defender XDR for users across multiple regions. The disruption was attributed to a large number of servers becoming unavailable, leading to increased load on remaining systems, with Microsoft investigating failing health checks and elevated processor usage.

Microsoft Outlook users globally are experiencing connectivity issues across web and app platforms. Microsoft has acknowledged the outage, attributing it to elevated load on a portion of its infrastructure and investigating a specific component causing failed health checks.

Microsoft is investigating a global outage affecting multiple Microsoft 365 services, including Outlook, Teams, Copilot, and Azure, with users reporting connectivity issues. The disruption, which began Thursday afternoon ET, was caused by servers unexpectedly becoming unavailable, straining the remaining infrastructure. This incident follows an earlier, separate Teams outage in the Americas.

Microsoft services, including Teams, Outlook, and Copilot, experienced widespread outages affecting users globally. Microsoft reported investigating and resolving the issue, but users continued to report problems with various services. The company attributed the outage to unexpectedly unavailable servers, straining the remaining infrastructure.

Several Microsoft 365 services, including Outlook and Teams, experienced an outage due to elevated load across multiple regions. Microsoft is investigating the issue, restarting infrastructure, and evaluating traffic redirection to restore service capacity.

Microsoft's Outlook email service, along with Teams, SharePoint, Copilot, OneDrive, and Office for the web, is experiencing an outage preventing user access. The company attributed the incident to "a large number of servers being unexpectedly unavailable" and is investigating the cause.

Microsoft Outlook is experiencing a widespread outage, with over a hundred thousand reports on Downdetector. Microsoft confirmed the issue, stating that a large number of servers are unexpectedly unavailable, causing elevated load on the remaining infrastructure. The company is investigating the cause and working to restore service.