Post #1362187
2026-04-08 22:50 UTC
Replies (2)
-
@V0ldek@awful.systems 2026-04-08 23:59
The only thing I can personally confirm is the JIT permissions thing. I didn't work in the Core Azure stuff so I can't verify the rest, but none of it is unbelievable...
-
@YourNetworkIsHaunted@awful.systems 2026-04-10 00:13
I can't validate any of the internal stuff, but the attitude of layering manual solutions and mitigation scripts on top of bad design choices and praying you could keep building the next bit of the bridge as the last one collapsed underneath you would explain *a lot* of experiences I had supporting systems running on Azure. The level of weird "Azure just does that sometimes" cases and the lack of ability for their support to actually provide insight was incredibly frustrating. I think I probably ended up providing a couple of automatic recovery scripts for people to use inside their F5 guests because we never could find an actual explanation for the errors they were getting, and the node issues they describe could have explained the bursts of Azure cases that would come in some days.