> An inadvertent tenant configuration change within Azure Front Door (AFD) triggered a widespread service disruption…

> The trigger was traced to a faulty tenant configuration deployment process. Our protection mechanisms, to validate and block any erroneous deployments, failed due to a software defect which allowed the deployment to bypass safety validations.

Am I reading this right? Global – pardon, "non-regional" – #outage of #Microsoft #Azure was caused by a tenant changing their config? 👀

Cascading failure. It cascaded.

> As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy.
https://azure.status.microsoft/en-us/status/history/#incident-history-collapse-YKYN-BWZ

#Microsoft #Azure #Outage

This might be a good time to consider deploying, contributing to or otherwise supporting @nextcloud:
https://nextcloud.com/

And before anyone says that Nextcloud's UI/UX is lacking: of course it is! Nextcloud has several orders of magnitude less money to throw at UI/UX.

But guess what:
1. this is fixable if they get more resources to work with;
2. every single Nextcloud instance I know of or use (there are many) stayed up and running yesterday.

#Microsoft #Azure #Outage