"a backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region. This resulted in the compute resources automatically restarting when connectivity was lost to virtual disks hosted on impacted storage resources."

So it wasn't a person at all, according to this theory. It was a "workflow." Perhaps AI is to blame! I think your theory was right.