← Voltar ao feed

Microsoft 365 global outage Nov 12-13, 2026: latent gateway server bug from July update caused cascading failure

11 fonte(s) · 17 atualização(ões) · publicado 12/11/2026 16:03 · coletado há 9 horas

Matéria consolidada. Reúne 20 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 11 fontes trouxeram em 17/11/2026 12:07; os links antigos trazem para cá.

Fontes: securityonline.info ↗ bleepingcomputer.com ×2 ↗ gbhackers.com ×2 ↗ olhardigital.com.br ×2 ↗ wired.com ×3 ↗ techcrunch.com ×2 ↗ securityweek.com ↗ digit.fyi ↗ malwarebytes.com ↗ securityaffairs.com ↗ zdnet.com ↗

On November 12, 2026, a widespread Microsoft 365 outage disrupted Outlook/Exchange Online, Teams, SharePoint Online, OneDrive, Office for the web, Copilot, and Microsoft Defender XDR, affecting users globally across business, education, government, healthcare, law enforcement, emergency services, aviation and transportation (malwarebytes.com; wired.com; bleepingcomputer.com; securityaffairs.com; zdnet.com; techcrunch.com; securityweek.com; digit.fyi). It started in the Americas with Outlook and Teams and expanded to 74 countries (more than 70 per wired.com, olhardigital.com.br and securityonline.info). Later reports also name Intune, Planner and Purview among the affected services (techcrunch.com; digit.fyi). Microsoft's preliminary post-incident report (dated November 15, Microsoft 365 Admin Center) gives the root cause: a latent software bug in a fix built for the Microsoft 365 networking gateway servers and rolled out from July, triggered by extra traffic after a Teams failover and by reduced gateway capacity (bleepingcomputer.com; gbhackers.com). securityonline.info (November 17) independently describes it as a lock contention defect in a July gateway hotfix and says Charles Lamanna, Microsoft Corporate Vice President, apologized on November 16 and stated that external hackers did not breach the platform. gbhackers.com describes the defect as a latent Windows bug in an internal process, which Microsoft says does not affect broader Windows deployments. Customer impact on Exchange Online lasted about 23 hours 50 minutes, from 4:20 PM UTC (11:20 AM ET) on November 12 to 4:10 PM UTC (11:10 AM ET) on November 13 (gbhackers.com; bleepingcomputer.com), although securityonline.info speaks of over 30 hours (see Conflicting Reports). The incident was an operational failure: Microsoft reports no cyberattack, exploitation, threat actor or data exposure, and says its final report is expected later this week (bleepingcomputer.com), with a repair plan listed for November 20 (gbhackers.com). Earlier wired.com and olhardigital.com.br reports that blamed a network capacity upgrade are now superseded (see Conflicting Reports).

Detalhes técnicos

  • Root cause per Microsoft's preliminary report: the defective code came from a fix built specifically for Microsoft 365 networking gateway servers. It began rolling out in July and spread globally over several weeks without visible problems (gbhackers.com; bleepingcomputer.com). Under particular traffic conditions, lock contention inside an internal Windows process exhausted CPU and memory (gbhackers.com). The bug caused resource contention that is worse on machines with more cores and newer hardware. Load testing used weaker hardware with fewer cores and different traffic from production, so it missed the defect (bleepingcomputer.com; gbhackers.com). securityonline.info corroborates this: the July hotfix introduced a lock contention defect that deadlocked threads under heavy load on modern multi-core hardware, and pre-deployment tests used older servers with fewer cores and synthetic traffic.
  • Trigger chain: about 15 hours before the outage, Teams automatically failed over to the networking infrastructure used by Exchange Online, raising traffic on those servers. Nearly 14% of gateway capacity was already offline for an unrelated reason. Users were redirected to other servers, which were overwhelmed and hit the same defect, creating a feedback loop. Within two hours the defect had hit the fleet, and at its lowest more than 80% of gateway servers were unresponsive (bleepingcomputer.com; gbhackers.com). securityonline.info gives the same 14% and 80% figures and says automated load balancers rerouted traffic to healthy nodes, causing cascading overloads.
  • Safeguards meant to stop failures spreading between regions and infrastructure partitions did not contain the cascade (bleepingcomputer.com; gbhackers.com; securityonline.info says regional isolation also failed). Exchange Online could not fail over to alternative infrastructure, unlike Teams, OneDrive and SharePoint (bleepingcomputer.com; gbhackers.com). securityonline.info adds that Exchange Online is bound to the primary gateway with no cross-gateway failover, so Outlook users waited longest.
  • Restarts failed because returning servers immediately absorbed the backed-up traffic and failed again (bleepingcomputer.com; gbhackers.com). securityonline.info describes this as retry storms from queued client requests that re-triggered the deadlock. This matches earlier reports that restored servers sometimes became unresponsive as traffic returned (malwarebytes.com; wired.com).
  • Tenant advisories: EX1550543 and MO1550821 (gbhackers.com).
  • Earlier reporting: Microsoft said multiple servers failed automated health checks, which overloaded the remaining infrastructure and caused connectivity problems (malwarebytes.com; wired.com; bleepingcomputer.com; securityaffairs.com; zdnet.com). Wired described cascading server failures in multiple data centers, with elevated load on the remaining servers, and health check failures in a component responsible for processing server health (wired.com).
  • TechCrunch described a cascading issue in which "a large number of servers [were] unexpectedly unavailable" across Microsoft's data centers (techcrunch.com). Digit also cited overloaded infrastructure causing server unavailability and issues with a secure connection process (digit.fyi).
  • Disruptions also affected AI connectors for OpenAI and Anthropic services, impacting tools such as Copilot. Users had trouble accessing email, scheduling meetings and using AI assistant features across the UK, Europe, North America and Asia (digit.fyi). OpenAI and Anthropic also had connection problems with Microsoft 365 tools (olhardigital.com.br).
  • Reported real-world impact (olhardigital.com.br, secondary commentary): UK hospitals fell back to paper records, ambulance services were badly affected, and courts sent jurors home early. A Colorado detention facility could not process bail payments online. Airlines in India, logistics and pharmaceutical firms in Japan, and financial institutions in Hong Kong and Taiwan reported disruption.
  • The outage includes Microsoft Defender for Office 365 alongside Defender XDR: portal access was affected while endpoint protection remained functional. Management dashboards such as Intune were also impacted (techcrunch.com).
  • Microsoft paused deployments and redistributed traffic globally. Digit also lists patch deployment and server restarts among the recovery actions, plus an extended 48-hour email timeout (digit.fyi). As services recovered, users faced delayed emails and notification floods from the backlog, with queue time increased to 48 hours (wired.com).
  • The incident follows a similar disruption in September linked to authentication configuration issues (techcrunch.com).
  • Wired noted that attention turned to Microsoft's workforce reductions and increased use of AI for code generation, but no direct link to the outage was established (wired.com); Microsoft's preliminary report does not cite either factor (bleepingcomputer.com; gbhackers.com).
  • No malicious activity or cyberattack was identified as a cause (malwarebytes.com; techcrunch.com; digit.fyi; securityweek.com; wired.com; olhardigital.com.br; bleepingcomputer.com; gbhackers.com; securityonline.info). No CVEs or IOCs have been published.

Remediação

  • Microsoft's fix: engineers built an update that restored the previous connection-handling code. They removed server groups from service, applied the update, restarted the servers and reintroduced traffic gradually. Mitigation began reaching affected capacity at 7:20 AM UTC on November 13 (gbhackers.com; bleepingcomputer.com). securityonline.info says the rollback window had expired, so engineers wrote an emergency patch live and remediated servers in batches.
  • Microsoft says it has added capacity, extended email delivery windows, improved connection monitoring, and added traffic distribution guardrails against redirection-triggered cascading failures (bleepingcomputer.com; gbhackers.com). Charles Lamanna apologized on X (bleepingcomputer.com), and on November 16 per securityonline.info.
  • Admins can follow tenant advisories EX1550543 and MO1550821 in the Microsoft 365 Admin Center (gbhackers.com).
  • Monitor the Microsoft service status and admin health notices, as recovery was gradual and relapses were reported.
  • Expect delayed email delivery and notification floods while the backlog clears (wired.com).
  • Verify security features (including Defender portals and policies) once access is restored.
  • Identify mission-critical services and maintain independent fallback options to improve resilience (wired.com). Given the impact on hospitals, courts and payment processing, plan manual fallbacks (olhardigital.com.br).
  • Lessons highlighted by securityonline.info (it names no customer actions): failover for Exchange Online, test hardware representative of production, and circuit-breaking degradation.
  • Beware of phishing scams masquerading as recovery offers or outage notices (gbhackers.com).
  • Organizations are putting contingency measures in place to mitigate disruption (securityweek.com).
  • Await Microsoft's final post-incident report, expected later this week, with a repair plan listed for November 20 (bleepingcomputer.com; gbhackers.com).

Relatos divergentes

  • Start date: securityweek.com says the outage began around November 13, 2026, and wired.com (later report) says it began around noon ET on November 13, while malwarebytes.com, techcrunch.com, digit.fyi, olhardigital.com.br and securityonline.info (Thursday, November 12) date it to November 12, 2026. The first wired.com report spans November 12-13. Microsoft's preliminary report, as relayed by bleepingcomputer.com and gbhackers.com, puts the start at 11:20 AM ET / 4:20 PM UTC on November 12, so November 12 is the authoritative date.
  • Cause: malwarebytes.com and other earlier sources pointed to servers failing health checks and overloading the remainder. techcrunch.com described cascading server unavailability. digit.fyi added a secure connection process issue. securityweek.com said Microsoft suspected a faulty update similar to the 2024 CrowdStrike outage. wired.com (later report) said Microsoft confirmed a technical issue introduced during a network capacity upgrade, and olhardigital.com.br (15 November, secondary) repeated it. The most recent and authoritative version is Microsoft's preliminary post-incident report dated November 15 (bleepingcomputer.com; gbhackers.com): a latent bug in a July update to the networking gateway servers, combined with a Teams failover and reduced capacity. securityonline.info (November 17) agrees (latent lock contention bug in a July gateway hotfix) but states its account rests on the article alone and did not check the vendor's post-mortem. The Microsoft report supersedes the network capacity upgrade explanation; health check failures and overload are best read as symptoms of the cascade. The final report is still pending. Slight difference in framing: gbhackers.com calls it a latent Windows defect specific to the gateway servers, while bleepingcomputer.com calls it a software bug in a Microsoft 365 gateway update.
  • Trigger: Microsoft's preliminary report (bleepingcomputer.com; gbhackers.com) describes an automatic Teams failover onto the Exchange Online infrastructure about 15 hours before the outage, while securityonline.info describes a scheduled migration of Teams traffic onto the primary gateway. Microsoft's version is more authoritative.
  • Fix: bleepingcomputer.com and gbhackers.com say engineers built an update restoring the previous connection-handling code; securityonline.info says the rollback window had expired and an emergency patch was written live. Microsoft's account (via bleepingcomputer.com and gbhackers.com) is preferred; the two may describe the same action differently.
  • Duration and recovery status: techcrunch.com reported email restored after about 18 hours by Friday morning US east coast, while wired.com reported roughly 24 hours. securityonline.info (November 17) says over 30 hours, without a primary source. securityweek.com earlier said service health was not yet fully restored and remained unstable. olhardigital.com.br (15 November) said the outage was fully resolved on Saturday, November 14, without citing a primary source. Microsoft's preliminary report gives customer impact on Exchange Online as 23 hours 50 minutes, ending 4:10 PM UTC (11:10 AM ET) on November 13 (gbhackers.com; bleepingcomputer.com). This is the most authoritative figure and contradicts the November 14 end date, the 18-hour estimate and the 30-hour claim (which may count total disruption, including backlog effects, rather than Exchange Online customer impact; this is not stated by the source). Earlier reports said there was no defined recovery timeline.

Linha do tempo

  1. securityonline.info ↗ · pub. 17/11/2026 06:33 · coletado 17/11 07:00

    Microsoft 365 global outage of over 30 hours traced to latent gateway hotfix bug, not a cyberattack

    ler a análise desta fonte

    On November 12, a Microsoft 365 global outage hit more than 70 countries and disrupted enterprise email and collaboration for over 30 hours. Microsoft Corporate Vice President Charles Lamanna apologized on November 16 and said external hackers did not breach the platform. The article attributes the outage to a latent lock contention bug in a July network gateway hotfix. That bug combined with a Teams traffic migration and a roughly 14 percent loss of gateway capacity, and over 80 percent of global gateway servers went offline. This record rests on the article alone: no web research was performed, so the vendor's own post-mortem was not checked.

    Technical Details

    • A July gateway hotfix introduced a lock contention defect that deadlocked threads under heavy load on modern multi-core hardware. Pre-deployment tests used older servers with fewer cores and synthetic traffic, so they missed it.
    • About 15 hours earlier, a scheduled migration moved Teams traffic onto the primary gateway shared with Exchange Online.
    • Automated load balancers rerouted traffic to healthy nodes and caused cascading overloads. Regional isolation also failed.
    • Restarting nodes triggered retry storms from queued client requests that re-triggered the deadlock. The rollback window had expired, so engineers wrote an emergency patch live and remediated servers in batches.
    • Exchange Online is bound to the primary gateway and has no cross-gateway failover, unlike Teams, OneDrive and SharePoint. Outlook users therefore waited longest.

    Remediation

    The article names no customer actions. It points to the need for failover for Exchange Online, representative test hardware and circuit-breaking degradation.

  2. bleepingcomputer.com ↗ · pub. 16/11/2026 13:43 · coletado 16/11 15:00

    Microsoft 365 global outage on Nov 12 caused by latent gateway server bug from a July update, cascading failure

    ler a análise desta fonte

    Microsoft says a software bug introduced in July in an update to its Microsoft 365 networking gateway servers caused the worldwide outage of November 12. The outage lasted nearly 24 hours, from 11:20 AM ET on November 12 to 11:10 AM ET on November 13. It disrupted Outlook, Exchange Online, Teams and Copilot. The preliminary post-incident report in the Microsoft 365 Admin Center names three causes: the undetected bug, extra traffic after a Teams failover, and reduced capacity. The article describes an operational failure, not a cyberattack, and reports no exploitation, threat actor or data exposure. Microsoft's final report is expected later this week.

    Technical Details

    • The bug caused resource contention under certain traffic conditions, and it is worse on machines with more cores and newer hardware. Load testing used weaker hardware with fewer cores, so it missed the defect.
    • About 15 hours before the outage, Teams automatically switched to the networking infrastructure used by Exchange Online, which raised traffic on those servers.
    • Nearly 14% of gateway capacity was already offline for an unrelated reason.
    • Users were redirected to other servers, which were overwhelmed and failed in turn. Within two hours the defect had hit the fleet, and at its lowest more than 80% of servers were unresponsive.
    • Safeguards meant to stop failures spreading between regions did not contain it. Exchange Online could not fail over to alternative infrastructure, unlike Teams, OneDrive and SharePoint.
    • Restarts failed because backed-up traffic quickly overwhelmed the servers again.

    Remediation

    Engineers deployed a fix to the affected servers. Microsoft says it has since increased capacity, improved monitoring and added safeguards against redirection-triggered cascading failures. Charles Lamanna apologized on X.

  3. gbhackers.com ↗ · pub. 16/11/2026 10:53 · coletado 16/11 12:00

    Microsoft attributes 24-hour Microsoft 365 outage to latent Windows lock-contention bug that crashed over 80% of gateway servers

    ler a análise desta fonte

    Microsoft attributed the Microsoft 365 outage of November 12–13, 2026 to a latent Windows defect, not to an attack. The defect left more than 80% of the affected networking gateway servers unresponsive, according to the preliminary incident report dated November 15. Customer impact on Exchange Online lasted 23 hours 50 minutes, from 4:20 PM UTC on November 12 to 4:10 PM UTC on November 13. This summary rests on the article alone; no vendor or other primary source was checked.

    Technical Details

    • The defective code came from a fix built specifically for Microsoft 365 networking gateway servers. It began rolling out in July and spread globally over several weeks without visible problems. Microsoft says neither the defect nor this fix affects broader Windows deployments.
    • Under particular traffic conditions, lock contention inside an internal Windows process exhausted CPU and memory.
    • Testing missed the flaw because lab traffic and hardware differed from production. Newer machines with more cores were more susceptible.
    • About 15 hours before the outage, Teams failed over to the primary gateway infrastructure. A separate, unrelated issue had also removed about 14% of gateway capacity.
    • Traffic redirected to healthy servers triggered the same defect, creating a feedback loop. More than 80% of gateway servers were unresponsive in under two hours.
    • Isolation failures let the cascade cross infrastructure partitions.
    • Restarts failed because returning servers immediately absorbed the queued traffic and failed again.
    • Tenant advisories: EX1550543 and MO1550821.

    Remediation

    Engineers built an update that restored the previous connection-handling code. They removed server groups from service, applied the update, restarted the servers and reintroduced traffic gradually. Mitigation began reaching affected capacity at 7:20 AM UTC on November 13. Microsoft also added capacity, extended email delivery windows, and strengthened connection monitoring and traffic distribution guardrails. A final report is due, with a repair plan listed for November 20. The article also warns of outage-themed phishing.

  4. olhardigital.com.br ↗ · pub. 15/11/2026 10:06 · coletado 15/11 12:01

    Microsoft global outage (Outlook, Teams, Copilot) from a network capacity update disrupts services in 70+ countries

    ler a análise desta fonte

    A global Microsoft outage began on Thursday 12 November 2026 and was fully resolved on Saturday 14 November. It affected Outlook, Teams and Copilot in more than 70 countries. According to the article, the cause was an update to Microsoft's network capacity. Microsoft ruled out cyberattacks and AI-agent-related problems. The impact reached governments, hospitals, tribunals and companies. UK hospitals fell back to paper records, ambulance services were badly affected, and courts sent jurors home early. A Colorado detention facility could not process bail payments online. Airlines in India, logistics and pharmaceutical firms in Japan, and financial institutions in Hong Kong and Taiwan reported disruption. OpenAI and Anthropic had connection problems with Microsoft 365 tools. The article is commentary on concentration risk and resilience. No Microsoft advisory or other primary source was consulted, and no technical details, CVEs or IOCs are given.

  5. olhardigital.com.br ↗ · pub. 13/11/2026 17:42 · coletado 13/11 19:01

    Microsoft outage disrupts services like Outlook, Teams, and Copilot across 70+ countries

    ler a análise desta fonte

    A widespread outage affecting Microsoft systems occurred between November 12 and 13, 2026, disrupting critical platforms such as Outlook, Teams, and Copilot used by millions globally. The incident impacted over 70 countries and hindered essential workflows for many users. The source does not explicitly detail the cause, duration, or remediation of the outage. The issue highlights ongoing challenges in availability for cloud-based productivity tools from major providers.

  6. wired.com ↗ · pub. 13/11/2026 16:08 · coletado 13/11 18:00

    Microsoft 365 experiences global 24-hour outage due to network capacity upgrade issue

    ler a análise desta fonte

    Microsoft 365 suffered a widespread outage lasting approximately 24 hours, impacting services such as Outlook, Teams, and Copilot globally in more than 70 countries. The outage began around noon ET on November 13, 2026, initially affecting North America before spreading worldwide. Microsoft confirmed the cause was a technical issue introduced during a network capacity upgrade, explicitly ruling out cyberattacks and AI involvement. As services are restored, users face delayed emails and notification floods due to backlog and increased queue time set to 48 hours. The outage disrupted governments, airlines, law enforcement, emergency services, and hospitals, highlighting risks of dependency on single cloud providers. Microsoft plans a full post-incident report after investigation completes.

  7. wired.com ↗ · pub. 13/11/2026 14:15 · coletado 13/11 16:01

    Global Microsoft 365 Outage Disrupts Critical Services Worldwide Due to Data Center Server Failures

    ler a análise desta fonte

    On November 12-13, 2026, Microsoft experienced a major global outage affecting Microsoft 365 services due to cascading server failures in multiple data centers, resulting in elevated load on remaining operational servers. This outage caused widespread disruptions in essential sectors including government, healthcare, education, law enforcement, and transportation worldwide. Microsoft confirmed no indication of cyberattack involvement, attributing the failure to unexpected server unavailability and automated health check failures in a component responsible for processing server health. The outage underscored the risks of dependency on a few large tech providers for critical infrastructure. It also drew attention to Microsoft's workforce reductions and increased use of AI for code generation, though no direct link to the outage was established. Organizations are urged to identify mission-critical services and maintain independent fallback options to enhance resilience.

  8. techcrunch.com ↗ · pub. 13/11/2026 10:15 · coletado 13/11 12:00

    Microsoft's global email and cloud services outage caused by cascading server failures

    ler a análise desta fonte

    On November 12, 2026, Microsoft experienced a widespread outage initially affecting Outlook email and Teams video conferencing services in the Americas. The outage rapidly escalated into a global cloud crisis impacting consumer and business email, file storage, AI tools including Copilot, security software Defender, and internal management dashboards such as Intune. The cause was a cascading issue leading to "a large number of servers being unexpectedly unavailable" across Microsoft's data centers. Recovery efforts took approximately 18 hours, with gradual restoration of email services by Friday morning on the U.S. east coast. Microsoft has stated there is no evidence of malicious activity but continues to investigate the root cause. This incident follows a similar disruption in September linked to authentication configuration issues. The outage affected diverse industries worldwide and highlighted challenges in swift recovery from large-scale internal failures.

  9. securityweek.com ↗ · pub. 13/11/2026 10:47 · coletado 13/11 12:00

    Global Microsoft 365 Outage Disrupts Email, Teams, and AI Services with No Evidence of Cyberattack

    ler a análise desta fonte

    A widespread outage has affected Microsoft 365 services globally, including Outlook, Teams, Exchange Online, and the AI assistant Copilot, impacting millions of paid commercial subscribers and causing disruptions across various sectors including government, healthcare, and aviation. The outage began around November 13, 2026, and Microsoft is employing a measured recovery approach but has yet to fully restore service health. The company has ruled out a cyberattack and suspects a faulty update similar to prior incidents like the 2024 CrowdStrike outage. Recovery is ongoing with incremental improvements, but service availability remains unstable. Governments and businesses worldwide have reported operational impacts, and alternative contingency measures are underway to mitigate disruption.

  10. digit.fyi ↗ · pub. 13/11/2026 07:35 · coletado 13/11 08:00

    Global Microsoft 365 Outage Disrupts Multiple Services Including Exchange Online and Teams

    ler a análise desta fonte

    On November 12, 2026, a major global outage impacted Microsoft 365 services including Exchange Online, Outlook, Teams, Microsoft 365 Copilot, SharePoint Online, Intune, Planner, Defender, and Purview. Users across the UK, Europe, North America, and Asia experienced difficulties accessing emails, scheduling meetings, and using AI assistant features. The outage affected diverse sectors such as government, healthcare, education, and private businesses worldwide. Microsoft attributed the disruption to overloaded infrastructure causing server unavailability and issues with a secure connection process, with no signs of malicious activity. Recovery efforts involved patch deployment, server restarts, and traffic redistribution, with ongoing restoration and an extended 48-hour email timeout. A post-incident report is pending.

  11. malwarebytes.com ↗ · pub. 13/11/2026 05:35 · coletado 13/11 06:02

    Global Microsoft 365 outage extends disruptions to Defender XDR amid ongoing recovery efforts

    This article adds confirmation that Microsoft Defender XDR and Microsoft Defender for Office 365 are affected by the ongoing outage, highlighting the broader impact on security services in addition to productivity applications. It emphasizes the global scope of the disruption affecting diverse sectors, includes warnings about phishing risks during the outage, and notes partial, inconsistent service recovery without a clear timeframe for full restoration. These details extend the known impact beyond productivity to also include security monitoring tools and user caution advisories.

    ler a análise desta fonte

    This article adds confirmation that Microsoft Defender XDR and Microsoft Defender for Office 365 are affected by the ongoing outage, highlighting the broader impact on security services in addition to productivity applications. It emphasizes the global scope of the disruption affecting diverse sectors, includes warnings about phishing risks during the outage, and notes partial, inconsistent service recovery without a clear timeframe for full restoration. These details extend the known impact beyond productivity to also include security monitoring tools and user caution advisories.

    A continuing widespread outage impacting Microsoft 365 services has expanded to include Microsoft Defender XDR and Microsoft Defender for Office 365, affecting organizations globally across businesses, schools, and government sectors. The outage, originating on November 12, 2026, has caused interruptions to Outlook, SharePoint, Teams, Copilot, and security service portals. Microsoft confirmed no evidence of malicious activity and attributed the disruptions to multiple servers failing automated health checks, which subsequently overloaded remaining infrastructure and caused intermittent service availability. Recovery is complicated by restored servers sometimes becoming unresponsive again as traffic resumes, and no timeline for full restoration has been provided. Users are advised to verify the functioning of security features as services are restored and to avoid phishing attempts during the incident.

  12. gbhackers.com ↗ · pub. 13/11/2026 01:54 · coletado 13/11 02:00

    Microsoft 365 Outage Expands with Persistent Server Failures Impacting Core Services Globally

    This report expands on earlier accounts by confirming Microsoft’s finding that elevated traffic was not the cause; instead, multiple core servers unexpectedly failed health checks leading to capacity loss on the affected infrastructure. It documents that some restarted servers become unresponsive again once traffic resumes, and that mitigation includes temporary traffic restrictions and review of recent configuration changes with rollback as a precaution. Additionally, it clarifies that the impact on Defender XDR affects portal connectivity but not endpoint protection functionality. The update stresses the complexity of the outage due to underlying infrastructure capacity limitations rather than isolated application faults, necessitating tenant-specific governance and extended recovery timelines.

    ler a análise desta fonte

    This report expands on earlier accounts by confirming Microsoft’s finding that elevated traffic was not the cause; instead, multiple core servers unexpectedly failed health checks leading to capacity loss on the affected infrastructure. It documents that some restarted servers become unresponsive again once traffic resumes, and that mitigation includes temporary traffic restrictions and review of recent configuration changes with rollback as a precaution. Additionally, it clarifies that the impact on Defender XDR affects portal connectivity but not endpoint protection functionality. The update stresses the complexity of the outage due to underlying infrastructure capacity limitations rather than isolated application faults, necessitating tenant-specific governance and extended recovery timelines.

    On November 12-13, 2026, Microsoft 365 experienced a major outage affecting core services such as Outlook, Teams, SharePoint, Copilot, and Microsoft Defender XDR worldwide. The disruption was linked to large numbers of servers failing automated health checks and becoming unavailable, creating capacity constraints that overloaded remaining infrastructure. Microsoft ruled out increased traffic as the trigger and continues a global traffic redistribution and server restart effort. Recovery remains incomplete with some servers becoming unresponsive again under normal traffic load, prompting temporary traffic restrictions and configuration rollbacks. The outage highlights complex infrastructure dependency challenges beyond individual app availability, stressing the need for tenant-specific advisory monitoring. No malicious activity or attack has been reported, but Defender XDR portal access disruptions raise concerns for security operations continuity. Administrators are advised to monitor Microsoft’s incident advisories EX1550543 and MO1550821 for ongoing details.

  13. wired.com ↗ · pub. 12/11/2026 17:01 · coletado 12/11 18:01

    Major Microsoft Outlook and 365 Service Outage in North America Due to Server Failures

    ler a análise desta fonte

    On November 12, 2026, Microsoft experienced a significant service outage impacting Outlook and other Microsoft 365 services primarily across North America. The outage began around 10:40 am ET with issues initially reported in Microsoft Teams and later affecting Exchange Online mailboxes and other services such as SharePoint Online and Microsoft Defender XDR. Microsoft identified the root cause as servers failing automated health checks and going offline, resulting in elevated load and connectivity errors, not due to cyberattack or increased traffic. The company paused all deployments, redistributed traffic globally, and attempted server restarts to restore services. The incident caused widespread disruption to email and collaboration workflows, with recovery efforts ongoing as of the last update at 3:05 pm ET.

  14. securityaffairs.com ↗ · pub. 12/11/2026 17:41 · coletado 12/11 18:00

    Microsoft Cloud Outage Disrupts Outlook, Teams, Copilot, and AI Service Connectors

    ler a análise desta fonte

    On November 12, 2026, Microsoft experienced a significant cloud outage impacting thousands of users primarily in the US but later confirmed worldwide. Critical Microsoft 365 services including Outlook, Teams, Copilot, Exchange Online, SharePoint Online, and Microsoft Defender XDR faced disruptions. The outage also affected AI connectors for OpenAI and Anthropic's services, preventing tools like Copilot from accessing Microsoft 365 inboxes. Initially attributed to high infrastructure demand, Microsoft later identified the root cause as multiple servers unexpectedly going offline, reducing capacity and putting strain on the remaining infrastructure. Microsoft implemented mitigation by pausing deployments, redistributing traffic, and restarting servers to restore services. IT teams were advised to monitor the Microsoft 365 admin center for real-time updates and expect delayed email and message delivery during recovery.

  15. bleepingcomputer.com ↗ · pub. 12/11/2026 17:15 · coletado 12/11 18:00

    Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide

    ler a análise desta fonte

    A widespread outage is impacting multiple Microsoft 365 services globally, including Outlook, Microsoft Teams, SharePoint Online, Copilot, and Microsoft Defender XDR, resulting in connectivity issues for many users. The incident began on November 12, 2026, with initial reports of Exchange Online mailbox connectivity problems in the Americas. Microsoft identified that server unavailability, not increased traffic load, is causing elevated infrastructure strain. To mitigate, Microsoft has paused deployments, redistributed traffic, and is restarting affected servers. A separate Teams outage earlier on the same day in the Americas was resolved and attributed to infrastructure resource contention. The current incident remains unresolved, with Microsoft not confirming any link between the two disruptions.

  16. techcrunch.com ↗ · pub. 12/11/2026 16:03 · coletado 12/11 17:00

    Microsoft Outlook and multiple Microsoft services suffer widespread outage due to server unavailability

    ler a análise desta fonte

    Microsoft is currently experiencing a widespread outage impacting its Outlook email service along with other major services including Teams, SharePoint, OneDrive, Office for the web, Copilot AI, and Defender XDR. The outage initially affected users in the U.S. and the Americas but has now expanded globally to all regions. Microsoft has attributed the incident to an unexpected unavailability of a large number of servers and elevated load across its infrastructure, causing service disruptions. The root cause remains under investigation, and no indication of a security breach or exploitation has been reported. This follows a similar service disruption in September related to an authentication configuration issue.

  17. zdnet.com ↗ · pub. 12/11/2026 16:45 · coletado 12/11 17:00 primeiro registro

    Major Microsoft outage affects Outlook, Teams, CoPilot, and OneDrive with disrupted service and slow recovery

    ler a análise desta fonte

    On November 12, 2026, Microsoft experienced a widespread outage impacting several critical services including Outlook, Teams, CoPilot, and OneDrive. The outage led to significant service disruptions for users worldwide, with nearly 83,000 reported issues at its peak. Microsoft initially reported the problem was resolved by noon ET, but users continued to experience issues for hours afterward. Microsoft has halted all deployments and is restarting affected servers to mitigate the problem, attributing the outage to an unexpected number of servers being unavailable, which overloaded remaining infrastructure. The root cause of the outage remains unclear, and Microsoft's own service status page was also inaccessible during the incident, complicating situational awareness. This incident highlights vulnerabilities in cloud service infrastructures affecting essential productivity tools across many sectors.