By Dan Lohrmann.
Microsoft continues to assist clients around the world after a major outage.Consider these headlines:France 24: ‘One of the biggest outages ever’: Disruption to Microsoft services enters second day — “An outage of Microsoft services such as Outlook, Teams and Copilot that began on Thursday continued to cause disruption to users around the world on Friday as the tech giant struggled to fix server problems it blamed for the problems. France 24’s tech correspondent Peter O’Brien takes a look at what we know about the outage which, given its scale and duration, makes it one of the ‘biggest ever,’ he says.”The Conversation: Microsoft has suffered a global outage. A tech expert explains what went wrong — “According to outage tracking site DownDetector, some 130,000 people reported issues accessing Microsoft Outlook as of early Thursday afternoon US Eastern time (early Friday morning in Sydney). In a statement on X, the tech giant said it was ‘aggressively pursuing all pathways to reduce impact’ and ‘restarting affected servers to return them to service.’“In an article for The Conversation last month, I explained how the whole internet is unlikely to go down but several services can become unavailable together when they rely on shared systems.“This outage shows precisely what happens when that shared infrastructure fails – and why we must prepare for digital outages in a similar way we do for natural disasters.”CNN: Microsoft reports ‘encouraging recovery progress’ in global outage that has impacted millions — “What’s been impacted: The outage, which began around noon ET on Thursday, left workers unable to access Outlook email, Teams meeting tools and other staples of modern office life. AI companies said they were facing issues as well. Banks, governments, health services, railways and courts all reported disruptions across Microsoft products. The outage was not caused by a cybersecurity breach, the company has said.“Global disruption: Outage reports ‘reached 74 countries and territories in about an hour,’ according to Downdetector. While some workers scrambled to find workarounds, others expressed relief in a respite from the work grind.”Forbes: Microsoft 365 Outage Continues: Tech Giant Has No Timeline For Recovery, Says It’s ‘Deeply Sorry’ — “The company said its engineers were restarting and repairing affected infrastructure before gradually bringing it back online, while also exploring additional measures to speed up recovery.“Microsoft also announced it was extending the email timeout window to 48 hours to help protect delayed messages while it works to restore services and address the email backlog.“The update did not provide an estimated timeline for when Microsoft expects to fully restore the disrupted services for all users. The disruption, which began Thursday afternoon, primarily affected Microsoft’s Exchange Online email infrastructure, preventing users from accessing their Outlook mailboxes and causing delayed email deliveries.“Other Microsoft services, including Teams, SharePoint Online, Microsoft Copilot 365, and Microsoft Defender XDR, were also impacted by the outage.”Downdetector: Status portal — “Outlook reports alone peaked at more than 2,000 times their normal level. Reports did not stay in the Americas. They jumped tenfold in the UK at 17:43, in India at 23:21 local time and in New Zealand at 06:55 local time. Between 17:00 and 18:55 UTC, nearly 3 in 10 reports came from outside the US. We count a country here once its reports reach ten times normal and at least 20 in five minutes. Reports about Microsoft 365, Copilot, Teams and OneDrive each rose more than a hundredfold, and Azure about a hundredfold. Xbox, GitHub and LinkedIn, also Microsoft’s, rose far less. Microsoft said a portion of its infrastructure was experiencing elevated load across multiple regions. At 19:38 UTC, reports were still running at more than 11,000 a minute.”BBC: Global Microsoft outage affecting tens of thousands of users — “For international organizations, this platform is essential for connecting and collaborating with colleagues around the world. Among the issues, users may be unable to view certain files or details on their calendar apps, Microsoft said.“Its AI platform, Copilot, may also be unable to work properly.”This YouTube video is from ABC News in Australia:
CBS News: Microsoft says it is seeing “continued recovery progress” as it battles major worldwide outage — “From Asia to the U.S., a Microsoft outage involving services like Outlook and Teams has dragged on for hours and impacted many users, companies and some government operations.“The outage was affecting a wide range of Microsoft 365 offerings that interact with its Exchange Online and email services. Services including Outlook, Teams and AI assistant Copilot were reported by users to be down. The effects rippled across the world, causing disruptions to business activity, government agencies and schools.”GLOBAL ISSUES, PERSONAL IMPACTS AND LESSONS LEARNEDThis has reminded many people of the large CrowdStrike incident in 2024. I actually learned of the extent of the outage after my company’s email went down on Thursday, and I also had long waits when contacting Delta Air Lines. I asked, “Is something major going on?” It turns out the answer was yes.So what can enterprise teams learn from this situation? How can governments and others prepare? Here are five areas to consider:1. Diversify Communication Channels: Relying exclusively on an integrated cloud suite like Teams and Outlook leaves organizations blind and mute when the platform fails. Enterprises and public agencies must maintain out-of-band communication pathways (such as encrypted SMS, independent messaging apps or analog phone trees) to coordinate disaster response and reach staff.Also, organizations running purely on-premises Exchange servers were not directly impacted by this Microsoft cloud outage, as their email routing and storage operate on local infrastructure independent of Microsoft 365. However, organizations running hybrid Exchange environments did experience disruptions whenever mail flow, authentication or user mailboxes routed through Microsoft’s cloud.2. Consider Decoupling Single-Vendor Solutions: Monolithic reliance on a single provider for identity management, email, storage and productivity tools multiplies systemic risk. Governments and critical infrastructure operators must evaluate multivendor or hybrid architectures to prevent total operational paralysis during a major vendor failure.Ask: How did we manage during this outage? Could we communicate via other channels? In this case, Google services and most other vendors were still operating with email and other products, but they have experienced previous outages as well.3. Enforce Independent Cloud Backups: Service availability is not data protection. Organizations must continuously export and back up mission-critical data, such as Exchange mailboxes, SharePoint repositories and document stores. Isolate vendor-agnostic storage platforms to protect against prolonged downtime or data corruption risks.4. Refine Incident-Driven IT Runbooks: During high-stress outages, panicked administrators often exacerbate issues by making reactive modifications, such as resetting masses of passwords or altering DNS records. IT teams must establish clear, rehearsed operational runbooks that mandate waiting for official vendor status updates before executing destructive troubleshooting steps.5. Perform Realistic Failure-Mode Drills and Exercises: Standard tabletop exercises and disaster recovery plans frequently fail because they assume minor regional glitches rather than cascading control-plane failures. Enterprises should conduct regular chaos-engineering simulations, such as intentionally severing API dependencies or simulating endpoint blackouts to uncover hidden operational coupling before an actual crisis hits.FINAL THOUGHTSAs I write this blog on Friday, Nov. 13, 2026, Microsoft is still rolling out fixes and has yet to publish its full post-incident report. Portals such as this one provide regular Microsoft updates: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirectSome may wonder: What caused the outage? See this video for a basic explanation:
window.fbAsyncInit = function() {
FB.init({
appId : ‘314190606794339’,
xfbml : true,
version : ‘v2.9’
});
};
(function(d, s, id){
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) {return;}
js = d.createElement(s); js.id = id;
js.src = “https://connect.facebook.net/en_US/sdk.js”;
fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, ‘facebook-jssdk’));
——————————————————-
Click Here For The Original Source.
