Microsoft blames monster email outage on software defect introduced in July fix (theregister.com)
186 points by Bender 10 hours ago
mike_hearn 8 hours ago
No big surprises here. Big outages at big firms seem to always look like this.
The electricity industry has this notion they call a black start, where they bring the grid online from zero. It's a very difficult operation because you can't start a generator straight into an offline grid otherwise it gets hit with full demand and can't keep frequency in the right range, which can damage equipment. So they have to start by disconnecting all the loads and then bringing load blocks back in sequence, trying to roughly balance available generation with the size of the next block. In practice black starts are extremely rare, but they can happen after a cascading failure in which something causes some generating stations to trip, redirecting load onto the remaining stations which can't handle it causing them to trip in turn. The entire grid can collapse in just 60 seconds or so once that kind of runaway failure starts.
This kind of outage is very analogous to a black start. A few servers get into trouble - maybe they're in a crash loop or maybe their caches are cold - the load balancers shift traffic onto the remainder which then can't handle the load either and so the failure cascades. Once a service is in this state sometimes the only remedy is to disconnect all load, bring the servers back to stability, then bring load blocks back online in small chunks, making sure to never hit anything with the full load immediately to ensure any caches or JIT compilers have time to warm up.
It's the sort of thing that requires a bit of preparation because naive ways of doing it like just randomly dropping 90% of requests will yield a broken service for everyone. Ideally your LB can drop traffic by modulus of the session cookie or similar, so users are let back in atomically.
Black starting a service is obviously quite hard to practice, but is probably something that sufficiently well resourced SRE teams should try once a quarter or so on a test cluster. I used to be an SRE at Google and although we regularly started up new clusters and moved traffic around between them, actually starting an isolated service instance entirely from scratch was never something we practiced. I remember in a few cases teams discovered devs had introduced circular dependencies by accident, i.e. starting service X required service X to already exist, or it depended on service Y that in turn depended on X. Sometimes you can only find these things by practicing.
nilptr an hour ago
There's literally no such thing as "black start" at Microsoft that I am aware of. The way services are brought online initially is through a build out process coordinated through hundreds of Teams. It's an organic, messy, and painful way of doing things. As such, build outs are a human driven process with bits of automation spanning sometimes 20+ years of engineering touches, troubleshooting guide, and some additional tribal knowledge thrown in passed down through the years. There is little consistency across teams and sometimes even within a team as every Azure Cloud is effectively slightly "different".
CobaltFire 2 hours ago
I never worked in civilian power generation, but I can vouch for this on Nuclear Ships.
We had to practice load pickup on a normal start at the pier often, but we likely practiced a full SCRAM to back online (including a FULL load shutdown) more.
Having predefined lists of what gets brought up at various points helps a ton, but it's still not an easy or simple operation.
TomatoCo 14 minutes ago
I imagine the predefined list is easier when it's all consumers that are under your control. I figure with civilian power some random percent of houses'll kick their AC on after power is restored.
Rygian 2 hours ago
Back in 2025, Spain did a very-dark-brown-almost-black start (with help from neighbours), starting with one hydropower plant and increasing from there.
It went remarkably well.
rawgabbit 3 hours ago
It's more testing theater on their end; it's just perfunctory rubber stamping. There was and is no real performance testing under simulated near-real world conditions.
solyin an hour ago
Did you do anything to try and fix that?
rawgabbit 12 minutes ago
scheme271 an hour ago
Texas was on the verge of having to do a black start a few years ago when winter weather started causing failures. I think people were quoting potentially weeks to get everything back online. As it was, I think people didn't have power for days during sub-freezing temps due to load shedding.
tonfa 2 hours ago
Somewhat related: https://company.sbb.ch/en/railway-development/services-rus/e...
SBB just finished their project to be able to restart the grid in 5min. (There was a famous multi hour outage a few decade ago that I think motivated this work)
nickdothutton 2 hours ago
3-5 days in the UK according to "regulations". Some talk of it potentially taking 7-14 days under certain bad circumstances.
brunoborges 2 hours ago
The biggest challenge of bringing a resilient system back online after an outage, is the resiliency of said system fighting back.
2muchcoffeeman an hour ago
Good to know even Google introduces circular dependencies!
jvidalv 3 hours ago
Happened to Spain last year. The black start.
nialv7 2 hours ago
that's not the problem with grid black start at all? black start is difficult because many types of generators themselves need power to start. it's a circular dependency problem, not a load management one.
avianlyric an hour ago
It’s both, but every grid has a sub-set of power stations with black-start capability (a crap ton of diesel generators), that exists to break the circular dependency problem and bootstrap the rest of the grid.
But load management while bootstrapping the rest of the grid is still very hard. Often the reason for really long blackout, ones measured in days rather than hours, is repeated cascading failures as operators try to reconnect parts of a the grid, and accidentally overload recovered parts of the grid, causing generators to trip off again.
bragh an hour ago
That was a very enlightening moment in Factorio when I had already converted everything to power and the whole grid blacked out and I needed to get it going somehow again.
EGreg 7 hours ago
In software servers this is called the “thundering herd” problem. It is why clients are coded do not just exponential backoff but random offsets too.
chinathrow 6 hours ago
It's also a well known problem, so no excuse for that.
dijit 2 hours ago
VirusNewbie an hour ago
xunil2ycom 3 hours ago
Well stated.
mindwok 2 hours ago
The biggest surprise here is that they're using Windows for critical network infrastructure. I'm surprised a Windows process has any role here outside the Exchange servers themselves.
devy an hour ago
Not a surprise. It's Microsoft, Windows is their bread & butter for a long time. And Windows Kernel team is actually full of amazing engineers, reputable computer scientists. Disclaimer, my former boss worked at Windows Kernel team, she's the most talented engineers I have ever worked with, she then went on lead core platform engineer at Shopify many years later.
Before Linux took over the server market in 2000, Windows server was the dominant player in mid-market (enterprise market has IBM mainframes too). But you would have be old enough to remember that decades ago.
mindwok 32 minutes ago
I have heard this repeated a few times now and it surprises me. Since going deep on Linux I've resented any time I had to use Windows, but folks I really respect often speak highly of the kernel. It'd be cool if they open source it one day and we get a good deep dive into the internals.
makeitdouble 12 minutes ago
freecodeio an hour ago
windows kernel might be the only thing high in quality in entirety of microsoft, although that's just my personal opinion
anonymous908213 an hour ago
syngrog66 an hour ago
engineering unwise. but might be wise purely from biz POV: dogfooding.
RachelF 2 hours ago
Someone has to do the testing, and Microsoft tests in production.
In 2014 Microsoft cancelled the dedicated SDET (Software Development Engineer in Test) role, triggering significant layoffs.
mosura 2 hours ago
Just be grateful they no longer put the configuration in SharePoint. (In an Excel document).
nashashmi 9 hours ago
Original source information: https://x.com/clamanna/status/2122209697226948729
Better summary: https://www.neowin.net/news/microsoft-finally-explains-why-o...
ncr100 9 hours ago
They talk about their relatively low-end testing environment PASSing the July code, and being different from their high-end production environment machines, sadly hiding the concurrency bug during the test phase.
Is this commonly acceptable? I'd imagine it's a costly trade-off?
bayindirh 9 hours ago
Depends on what low/high end are. If low end is 4 core and deployment is 128 cores, this is not acceptable.
But if low is 64 and high is a whole cluster, now that's a different kind of maths.
Edit: The article states the following:
> "lock contention inside an internal Windows process which caused the machine's resources (CPU & memory) to be exhausted."
So, it's more the former. The testing machine is probably a 8 year old server on an office shelf, and prod machines are 64-128 core cutting edge Xeons/EPYCs.
Lock contention. It was MUTEX spins in Windows 95, it's lock contention in 2026. Why this is still a thing, Microsoft?
(Man, I felt old while writing this.)
lokar 8 hours ago
I always this was standard to have a test setup in the production environment on the latest hardware (that’s how you qualified that hardware in the first place) running one “unit” of the system (whatever that is) at full scale and load (ideally higher).
jakewins 2 hours ago
awesome_dude 23 minutes ago
When i saw the lock contention - I immediately thought distributed lock component
munchbunny an hour ago
At Microsoft's scale, it's extremely difficult to simulate production scale because the sheer size of the production system is overwhelming, and many issues emerge from the combination of sheer volume and the complexity that reality tends to introduce.
Microsoft tests its stuff on their own employees (old citation, but still true today: https://devblogs.microsoft.com/oldnewthing/20110802-00/?p=10...), and that includes Exchange online. However, even though Microsoft is a pretty big company, it's still teeny compared to its customer base.
notyourwork 8 hours ago
Testing at production scale is extremely difficult. It’s also financially expensive. In my experience, you balance the two where big changes are tested with some simulation setup to gain confidence. Though, the ci/cd pipeline never has close to full scale automated testing.
Choad_20261104 7 hours ago
...and many times you test to experience, and experience cannot possibly build interferences that simulate the instances you have not experienced nor what has been imagined based on that experience. some ways of precipitating the demons that are in the ontology of not knowing what you don't know are monte carlo, or perhaps noise injection, but those are time consuming, quite wasteful, and truly hated by people used to working with deterministic machines. that makes finding corner cases very difficult
plus, mistakes are the essence of learning and sometimes mistakes are necessary.
likewise, we are a very efficient world and efficiency hates redundancy, and hates nonconformity...of which those are two of the features that make exploits widely successful and failures massively impactful
pwarner 2 hours ago
I think MS could afford a bit of a test lab?
marcta 2 hours ago
awesome_dude 25 minutes ago
I read that part of their statement as "QA were set a priority to ensure existing hardware wasn't affected, which reduced their (QAs) capacity to test on new hardware which was assumed to be safe"
They find QA dirty in their statement, because they don't state who set that priority, nor why the new hardware was felt to be less likely to be affected (what did their risk matrix look like for their hardware profiles i wonder)
k0morebi 2 hours ago
Not a network engineer so genuinely curious how these things are handled at the epic scale of 365, azure, aws and so on.
Extent of my knowledge is nginx or traefik load balancing which at this scale is virtually equal to no knowledge. But seems like there would be systems in place to simply drop a sliding percentage of excessive traffic or block some regions once critical thresholds are reached rather than compounding the problem with forwarding the growing number of requests downstream to next victim server.
hmokiguess 9 hours ago
> The engineers who worked feverishly to restore services deserve commendation and will hopefully never have to buy their own beverages in Redmond again (or at least escape the next round of firings).
What does this mean? I didn't understand
giancarlostoro 8 hours ago
People should buy them drink, as for the firings side note Microsoft recently had a "voluntary exit" offer mailed to a fourth of their workforce:
https://www.geekwire.com/2026/microsoft-makes-new-voluntary-...
How long until Microsoft fires key people to the point that outages become more common? All in the name of AI, which I don't believe for a second, they're just trying to maintain stock market profitability math by firing enough, they'll just hire more people when they make more.
Choad_20261104 7 hours ago
The opportunity/command to exit is not always negative. In many of my career moves, it turned out that the next job was better and came far sooner than the severance calculation had allowed for. Some within weeks. Hardly had time to relax. It seems like for talented individuals opportunity always pops up.
giancarlostoro 7 hours ago
thewebguyd 7 hours ago
> How long until Microsoft fires key people to the point that outages become more common?
Already happening. Granted, not a global outage like this one, but there's not a single day without a service degradation or advisory on the admin portal for 365. The "It's now called Microsoft 360" memes are well earned, and their support is atrocious. I get the feeling that everyone who knows how it works is gone.
abrichr 9 hours ago
I think it means that people will hopefully buy them beers as thanks
nashashmi 8 hours ago
An artistic way of saying the engineers should get praised and rewarded.
AdamN 8 hours ago
You mean like the Covid nurses? With stickers that say 'You Rock!!' or 'Hero' and a $5 gift certificate to Dairy Queen?
deathanatos an hour ago
BoiledCabbage 6 hours ago
bayindirh 9 hours ago
In sysadmin speak this is hoping that Microsoft gives them free beverage credits (or give them some kind of bonus because of their efforts) and don't fire them as soon as the fix is deployed to scapegoat them.
In a rare occurrence, The Register sides with the Microsoft developers. Not that they're anti-developers, but they are anti Microsoft because of its well-earned reputation for EEE and Halloween Documents.
voidfunc 8 hours ago
It means they deserve "Thanks" (buying a beer/coffee is a token Thank You) and hopefully they are removed from the pool of candidates for the next layoff.
Surprised so many people are struggling with this...
Having been on incidents like this before though, yea, that aint happening.
bayindirh 8 hours ago
> Having been on incidents like this before though, yea, that aint happening.
Been there, through that, and sadly you're right. The bitter part is I didn't want extra compensation or anything. Just a thank you and a day off is more than enough for me, so to recharge and ride the wave of what we (not I, we) have accomplished, so I can work with extra motivation for some time.
Instead, got a 5 minute coffee break and dived to the next non-urgent ticket. Yeah, great way to thank and motivate the people who spent 24 hours in an underground office cutoff from the world, trying to save a system from melting down.
Glad I'm not there anymore.
27183 8 hours ago
> Having been on incidents like this before though, yea, that aint happening.
Yeah, instead what will happen is their manager will ask them why they didn't get as many story points done this sprint as they did last sprint and their performance will be marked "degraded".
Molitor5901 9 hours ago
It kind of feels like they are saying, look, we know we caused the problem, but we fixed it. So we're good, right?
colonCapitalDee 8 hours ago
Seems like a pretty standard big company severe outage to me. These things happen!
p4ul 7 minutes ago
Indeed! A "normal accident" as they say.
And it's also possible that these normal accidents might become more frequent with all the layoffs, AI code, and AI-generated exploits. I guess we'll see.
syngrog66 an hour ago
broadstrokes: bitten by concurrency, contention, thundering herd, and a proximate cause which was not in fact the root cause and the root cause had been lurking latent for several months so hard to undo surgically fast. combined with insufficient load/release testing and insufficient mitigation in prod.
toss1 9 hours ago
>> "the processes that led to an update with a latent defect reaching production deserve a long, hard look. "
Indeed they do deserve a long hard look.
Toss1's conjecture:
We are now seeing the beginning of an era of latent technical debt brought about by too rapidly firing developers and switching to AI code generation (nevermind vibe-coding). Even well-prompted and well-monitored by top expert coders and architects, there is latent technical debt, and it is more diffuse, harder to find, and harder to fix, and will start showing up in outages like this.
(It first seemed the ATC outage was another example, but it now seems it was merely the usual management incompetence if not an outright manipulative ploy to 'justify' more spending for a single-bid contract [0])
[0] https://ajsignalnotnoise.substack.com/p/faa-air-traffic-cont...
nialse 4 hours ago
Suggested reformulation of the conjecture:
"Complex systems are kept stable by organisational knowledge of their weaknesses and how to compensate for them. Organisational change erodes this knowledge while the underlying weaknesses remain. A previously stable system thus becomes increasingly vulnerable to failure."
When it is said that software is a solved problem, what is ment by that is really that programming, typing up the code, is a solved problem. Software engineering, systems architecture and the complexities in distributed systems are not, while leads to confusion when not being mindful of the difference.
toss1 13 minutes ago
And so we now have additional mysterious banking system issues today... Hmmm
wduquette 8 hours ago
So maybe we shouldn’t be putting all our eggs in one basket?
falserum 36 minutes ago
Why? Outage is not so bad if 1) everybody is suffering and 2) it is not your fault.
Cynic in me does not see any need to change anything.
dweinus 2 hours ago
Multiple eggs AND multiple baskets? In this economy?
dgellow 8 hours ago
Hmm, the best I can do is offer you a larger basket
marcta 2 hours ago
Subscribe now to my egg-as-a-service product
mxuribe 8 hours ago
No, no, i think we can and should still load all the eggs into a single basket...we simply have to do so at random frequencies and speeds in order to avoid cracking the eggs, plus when contention inevitably happens, we ask that the egg loaders simply hold off a little...to avoid such traffic, and until egg loading can resume! /s
nelaggy 7 hours ago
what role did ai play in all of this?
can we blame it for the bug? can we credit it for the fix?
might be the most important part of the full report
devy an hour ago
Interesting that it's their EVP of Copilot, Agents, and Platform at Microsoft, building the next generation of AI-powered tools for work who spoke up for he post-mortem instead of their CTO.
Does that mean Microsoft's internal code are 100% outsourced to agents / AI and human review just won't be able to catch latent bugs like this?
dogscatstrees an hour ago
> "lock contention inside an internal Windows process which caused the machine's resources (CPU & memory) to be exhausted."
Looks at my Windows Task Manager...
feverzsj 9 hours ago
Poor Microsoft can't afford more than one low-end testing environment.
preommr 9 hours ago
This is what happens when you burn billions for no reason.
Github copilot had INSANE usage. Cursor switched away from per request plans in 2025, Copilot did it this year with all the reasoning and more expensive models. It was insane, you could write out a whole page of features, and have it run on one request for hours depending on the loopholes you exploited (some models were discounted for some time, basically free in some cases, and shenanigans around switching in betwen agents)
We talk about opus et. al being heavily subsidized at like 1-2k for $30-$100. I remember seeing figures in the 10s of thousands in subsidizations for GHC. There's no way they weren't losing just massive piles of money.
dgrin91 9 hours ago
Doesn't the article state the opposite? The low end was not the problem. It was high end that was the problem.
I like ragging on Microsoft as much as the next guy, but honestly this problem sounds complex & hard to predict. AI or not, this feels like the type of bug that would have slipped by me as well.
The response clearly could have been stronger though.
thesuitonym 9 hours ago
The point they were making is that had Microsoft used high-end equipment in testing they may have found this issue before it hit production.
lkjdsklf 2 hours ago
bethekidyouwant 8 hours ago
zdragnar 9 hours ago
I read "more than one low end" as "more testing environments than one low end" rather than "more low end environments than one". It's a snarky way of saying they should have been testing high end environments for no more reason than they had the money to do it, rather than saying they should have been testing the low end more.
elcritch 9 hours ago
Think of the poor starving shareholders and CEO pay packages.
rs999gti 9 hours ago
> poor starving shareholders
You mean you and me? You realize pensions, institutions, and individual investors are shareholders as well?
triceratops 8 hours ago
elcritch 8 hours ago
panarky 6 hours ago
tenderfault 3 hours ago
This happens when you are trying to do weird things with emails rather than just deliver them to destination.
Also this is karma because Microsoft blocked in ignorance entire datacenter networks making SMBs unable to deliver messages to their networks.
Ta-ta!
pluc 3 hours ago
Nothing more cuts and more AI won't fix!
vessenes 9 hours ago
Pretty interesting that testing was aimed the worry: low spec boxes, and missed a different problem: concurrency contention for high spec boxes. Gotta be covered by someone's rule of testing, I imagine. Also, woof.
taspeotis 2 hours ago
They've done this before! https://randomascii.wordpress.com/2017/07/09/24-core-cpu-and...
ZiiS 8 hours ago
- we added a bug (yes, everyone does).
- our testing didn't cover it (again, this is expected occasionally).
- this cascaded to take down more than a billion people's service (WTF; this is not how you design systems).
- it took 15 hours to deploy the fix (not good, but at this scale maybe).
Feels like they are completely missing the point of where the problem is and how to fix it?
topaz0 10 minutes ago
Antitrust
VirusNewbie an hour ago
>- it took 15 hours to deploy the fix (not good, but at this scale maybe).
I've definitely been in similar scale war rooms and 15 hours is not acceptable.
lokar 8 hours ago
In terms of cascading failure and inability to rollback or fix quickly, MS has always been terrible.
bayindirh 8 hours ago
Also, don't forget that e-mail is a distributed system and servers retrying always keep a pressure on you, despite their best intentions, and spaced retries.
So, even when you fix the issue, it takes a bit to clear up, and the load gauge stays at the red zone for a while.
lokar 8 hours ago
spprashant 8 hours ago
These kinds of incidents should inject healthy dose of techno-skepticism in the larger conversation. The world is teetering on the edge of turning over all our processes to LLMs and retiring human labor for good.
But at the end of the day these are servers strung together sending packets over copper wires. They are extremely reliant till they are not.
When crisis strikes you can only hope there is a squad of well trained humans who can step in to untangle these messes. But as more of the labor force is stripped out of responsibilities, the longer these outages will take to resolve. Imagine being jolted out of your year-long UBI-funded vacation to login and resolve a multi-continent server outage that you only have a vague memory of.
dgellow 8 hours ago
> The world is teetering on the edge of turning over all our processes to LLMs and retiring human labor for good.
That’s Silicon Valley fantasy, it’s not even close to reality
greggoB 2 hours ago
From what I've observed, SV is doing anything and everything it can to make it reality. It's scary to see how successful their campaign has been so far.
cyberax 3 hours ago
So apparently this is the report: https://www.365fanatic.com/wp-content/uploads/2026/11/PostIn... I propose a "latent bug" drinking game.
So to recap:
1. They did not have proper cell-based architecture to partition their system into failure domains ("In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure.").
2. They did not have proper monitoring to see the encroaching collapse.
3. Stuff just keeps falling off: "Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day"
sandworm101 9 hours ago
>> "an update that returned the code path to the previously known good state in Windows."
I know I shouldn't be surprised, but I still struggle to imagine such high-capacity servers running with windows. Part of me wonders why any important server would be running windows. And I do chuckle at the "update" that returned windows to a previous state. Never admit a rollback. Never admit a previous update was less than perfect. Hold the line MS. Hold that line.
theragra 8 hours ago
But if they wouldn't do it, Windows will be even worse.
Moreover, my current switch to Linux shows that Linux is not so much better in stability as it is in public imagination. Once a month or two, I have KDE freeze so hard I barely can recover without reset (sometimes can't). Still can't find the reason. Hardware seems to be okay, it is an expensive gaming laptop.
Also, out of RAM can lead to GUI crashing even with swap enabled. True, this is unrelated to servers, which run without GUI, but still weird that it happens.
Also, when my laptop runs for weeks without reboot, it has issues with VRAM being occupied and not freed for some reason, which causes game crashes. With all the talk about Linux infinite uptime I expected better.
However, I almost can't complain about my homelab server. If there is enough disk space, it can run for months. Unfortunately, lately there are so many patches, I need to reboot almost each day (at least podman-hosting VM, if not proxmox host)
For the last half a year I run my homelab, I only had one suspicious shutdown, for which I am not sure I understand the reason well.
mannyv 7 hours ago
Hard freezes are generally related to hardware. Specifically it usually means interrupt processing has stopped, which usually means a driver issue.
stackskipton 8 hours ago
Alot of 365 is using Exchange/Sharepoint/Skype for Business code bases which were Windows specific. With Exchange, there was specifically role called "Client Access" which clients connect, the system looks up which backend server has your mailbox and proxies your connection there. Reading between the lines, my guess is this system was reused for Sharepoint/Teams/Office and they could swing off of it to secondaries but Exchange is hard locked on it.
Microsoft does greenfield new stuff on Linux mostly.
thesuitonym 9 hours ago
Yeah it's pretty crazy that Microsoft, a company most well known for it's Windows operating system, would use that same operating system on its servers.
betaby 8 hours ago
It's is crazy. Given the fact they are running Linux on their cloud. https://azure.microsoft.com/en-us/products/azure-linux/
nashashmi 8 hours ago
nashashmi 8 hours ago
Those guys are psycho-fanatics of dogfooding their own services. In the last decade or so, they have hesitantly entertained Apple ecosystems.
bayindirh 9 hours ago
They just postponed an improvement temporarily to reevaluate it later, in fact.
Here, I converted it to corporate speak for you.
k0morebi 2 hours ago
The previous know good state?
Windows 10?
7?
XP?
95?
CrzyLngPwd an hour ago
Yeah, but was the defect written by a clanker?
ChrisArchitect 8 hours ago
This MS rando on X just leaking his 'abridged' version instead of letting the official account post the report/blog later or whatever? Gotta be 'first' right bro, and now the source of every rabid tech blog for the rest of the day. bah