[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f-hS-8COTV8bOyS2JgMOXMCWrphgkrCHLhvQwUckPw98":3},{"article":4,"iocs":48,"watch_terms":49,"solutions":50,"lesson":59},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":30,"category":31,"article_tags":35},"4061b239-3bf3-4f96-9046-3f87b05d1028","Microsoft Cloud Outage Hits Outlook, Teams, Copilot and AI Services","microsoft-cloud-outage-hits-outlook-teams-copilot-and-ai-services-838466","A Microsoft outage disrupted Outlook, Teams and Copilot, also breaking OpenAI and Anthropic connectors to Microsoft 365 accounts. Microsoft 365, Outlook and Teams went down for thousands of US users on Thursday, November 12. Reuters reported that the disruption also hit the connectors OpenAI’s and Anthropic’s AI services use to reach Microsoft accounts. “Microsoft 365, […]","A significant Microsoft outage on November 12, 2026, disrupted services including Outlook, Teams, and Copilot, affecting thousands of US users and extending globally. The disruption also impacted connectors for OpenAI and Anthropic AI services. Microsoft initially cited heavy workloads but later identified the cause as unexpectedly unavailable servers straining the remaining infrastructure. The company implemented measures such as pausing deployments and restarting affected servers to restore capacity.","Microsoft cloud outage impacts Outlook, Teams, Copilot, and AI services.","https:\u002F\u002Fsecurityaffairs.com\u002F202932\u002Fsecurity\u002Fmicrosoft-cloud-outage-hits-outlook-teams-copilot-and-ai-services.html","https:\u002F\u002Fsecurityaffairs.com\u002Fwp-content\u002Fuploads\u002F2026\u002F11\u002Fimage-24.png","2026-11-12T20:41:47+00:00","2026-11-12T22:00:25.620687+00:00",7,[17,20,22,24,26,28],{"name":18,"type":19},"Outlook","product",{"name":21,"type":19},"Teams",{"name":23,"type":19},"Copilot",{"name":25,"type":19},"Microsoft 365",{"name":27,"type":19},"Azure",{"name":29,"type":19},"OneDrive","c70f3a41-2f0c-4608-870d-b8cbcd8be076",{"id":30,"icon":32,"name":33,"slug":34},null,"Cloud Security","cloud-security",[36,41,46],{"category":37},{"id":38,"icon":32,"name":39,"slug":40},"02371804-cf6d-4449-98de-f1a2d4d9b266","Tools","tools",{"category":42},{"id":43,"icon":32,"name":44,"slug":45},"80544778-fabb-4dcd-aa35-17492e5dcf4f","Vulnerabilities","vulnerabilities",{"category":47},{"id":30,"icon":32,"name":33,"slug":34},[],[23,25,27],{"controls":51,"vendors":52},[],[53],{"slug":54,"name":55,"logo_path":56,"roles":57},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png",[58],"affected",{"slug":60,"title":61,"body":62,"framework_refs":63,"framework_notes":68},"microsoft-cloud-outage-exposes-infrastructure-resilience-gaps","Microsoft Cloud Outage Exposes Infrastructure Resilience Gaps","A widespread Microsoft cloud outage disrupted Outlook, Teams, Copilot, and third-party AI connectors when unexpectedly unavailable servers overloaded remaining infrastructure, cascading into a global service disruption. The root issue reflects insufficient redundancy and capacity planning — when a subset of servers became unavailable, no adequate failover mechanism prevented the remaining nodes from being overwhelmed. This matters because modern organizations are deeply dependent on cloud-hosted productivity and AI services, meaning a single provider's infrastructure failure can halt business operations at scale. Microsoft's reactive measures — pausing deployments and manually restarting servers — highlight the need for automated failover and pre-tested recovery runbooks rather than ad hoc remediation.",[64,65,66,67],"NIST SP 800-53 CP-10: System Recovery and Reconstitution","NIST SP 800-53 SI-13: Predictable Failure Prevention","NIST CSF 2.0 RS.MI-01: Incidents are contained","NIS2 Article 21(2)(c)",{"NIS2 Article 21(2)(c)":69,"NIST CSF 2.0 RS.MI-01: Incidents are contained":70,"NIST SP 800-53 SI-13: Predictable Failure Prevention":71,"NIST SP 800-53 CP-10: System Recovery and Reconstitution":72},"NIS2 Article 21(2)(c) requires business continuity and crisis management measures, including service restoration plans, which would have mandated pre-tested failover procedures for essential digital infrastructure.","This category requires that incident containment actions be taken promptly; faster automated containment would have limited the blast radius before the overload spread globally.","SI-13 calls for redundant components so that unexpected unavailability of some nodes does not degrade overall system capacity, directly addressing the cascading overload seen in this outage.","CP-10 requires that systems recover and reconstitute to a known state after disruption; pre-tested reconstitution procedures would have replaced the ad hoc server-restart approach used here."]