3 ms·

I don't trust them not because they let their certs expire earlier this year causing an extended outage, it's that they didn't have a robust process for managin

• facorreia 14y ago
  "As a part of the normal operation of the Secret Store, scanning occurs on a weekly basis for the certificates being managed. Alerts of pending expirations are sent to the teams managing the service starting 180 days in advance. From that point on, the Secret Store sends notifications to the team that owns the certificate. The team then refreshes a certificate when notified, includes the updated certificate in a new build of the service that is scheduled for deployment, and updates the certificate in the Secret Store’s database. This process regularly happens hundreds of times per month across the many services on Windows Azure." http://blogs.msdn.com/b/windowsazure/archive/2013/03/01/details-of-the-february-22nd-2013-windows-azure-storage-disruption.aspx http://blogs.msdn.com/b/windowsazure/archive/2013/03/01/deta... IMO they had a rather extensive process in place. That process had a flaw, though, in which a specific kind of human error (forgetting to set up a flag) was not double-checked. As disruptive as that was, it's growing pains and overall they've had few issues for a service that is scaling up and out so quickly.