Login
You're viewing the functional.cafe public feed.
  • Nov 14, 2026, 12:59 PM

    I think the real story here is not that it happened, but how their incident response flailed around as if they don't even know their own infrastructure anymore. That's a cultural shift that can be pinned on dogmatic "AI" adoption even if you can't point directly to a PR from Claude as the trigger.

    💬 3🔄 2⭐ 0

Replies

  • Nov 14, 2026, 2:01 PM

    @boxobark.ing @davidgerard this was why I ripped the piss out of their status update that said they were "seeing encouraging signs of recovery" like they were mere passengers along for the ride with the rest of us

    💬 1🔄 2⭐ 10
  • 💬 0🔄 0⭐ 5
  • Nov 14, 2026, 2:18 PM

    @boxobark.ing Spend 50 years bulding things that mostly work, then fire all the architects, builders and maintenance staff in the hope that the power tools left on site or in cupboards can fix everything that breaks on their own because a lot of money was spent to buy them.

    💬 0🔄 0⭐ 5
  • Nov 14, 2026, 2:58 PM

    @boxobark.ing @davidgerard
    OK, so… MIcrosoft have always had a soft spot in their own understanding of their cloud infrastructure. I was a CTO of a company that was using Azure to provide data to a fleet of devices, and one time we rolled out an update that could;t read the result of a query from Azure, so it would send the request again. We only rolled out the update to about 1% of the fleet before the load on the SSH authentication servers overwhelmed the entire Azure west European infrastructure because crypto is expensive.

    Anyway the important thing was that you couldn’t see the issue on any of the customer facing dashboards - if we looked on the client side we could see more than 90% of requests failing but on the Azure side all we could see was lower than expected traffic. When we reported the problem to MS (initially as one endpoint having an issue) it took them many many hours to realise what the actual issue was taking down their entizre network. And they only figured it out because we did some investigating on our side to see exactly where in the connection things were failing. They couldn’t even see their entire service was down (for all customers, not just us) - though they finally twigged when I explained it wasn’t just the one endpoint, but all of them.

    Anyway, this situation looks very similar in its response shape, but mine happened 8-9 years ago, so I wouldn’t be too quick to point the finger at AI here.

    💬 3🔄 7⭐ 19
  • 💬 0🔄 0⭐ 1
  • 💬 0🔄 0⭐ 0
  • Nov 14, 2026, 3:58 PM

    @demallien yeah. Microsoft has somehow had an "AI first" attitude towards expertise and experience long before the AI actually existed to try to replace people with

    I think that's why Nadella embraced AI so hard - he recognized it as an actualization in tech of the company's existing attitudes

    💬 0🔄 0⭐ 0