Re:Microsoft blames monster email outage on software defect ...
by filleokus on Tuesday November 17, 2026 @08:03AM
(#50530808)
But given the size of the impact this incident had, I assume involving any team that would not be an issue.
I'm guessing there must be some deeper issue at play making it too risky or not possible. Maybe the hardware LB's were too intertwined with customer Azure loads or something?
But when you are hitting hour 12 of a global outage of one of your most central services I would assume even quite exotic solutions would be considered (e.g standing up dedicated hardware LB's with load shedding and pointing some of the DNS resolution to those)
I'm guessing there must be some deeper issue at play making it too risky or not possible. Maybe the hardware LB's were too intertwined with customer Azure loads or something?
But when you are hitting hour 12 of a global outage of one of your most central services I would assume even quite exotic solutions would be considered (e.g standing up dedicated hardware LB's with load shedding and pointing some of the DNS resolution to those)