But at the most basic level - it was a human error (as I read it). "Someone" didn't mark the update package as a critical update.
Arguably (and I can see this), because the package had 5 weeks before it was required... From: Tim Evans [mailto:[email protected]] Sent: Tuesday, March 5, 2013 12:44 PM To: NT System Admin Issues Subject: Details of the February 22nd 2013 Windows Azure Storage Disruption http://blogs.msdn.com/b/windowsazure/archive/2013/03/01/details-of-the-february-22nd-2013-windows-azure-storage-disruption.aspx It sounds like they had procedures in place to prevent this from happening, but they didn't work. ...Tim ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
