> I suspect, if you check the terms of service for Azure, you wouldn't be able > to sue them for anything more than whatever your SLA says you will get. I'm > sure their liability is limited up front, not matter what they admit to have > done or not.
That doesn't stop lawyers from trying. > FWIW, I thought it was a pretty straightforward explanation of what happened > and the steps they took to prevent it from happening again. Agreed. I'm just being cynical today, I guess. --Matt Ross Ephrata School District ----- Original Message ----- From: Tim Evans [mailto:[email protected]] To: NT System Admin Issues [mailto:[email protected]] Sent: Tue, 05 Mar 2013 13:08:08 -0800 Subject: RE: Details of the February 22nd 2013 Windows Azure Storage Disruption > I suspect, if you check the terms of service for Azure, you wouldn't be able > to sue them for anything more than whatever your SLA says you will get. I'm > sure their liability is limited up front, not matter what they admit to have > done or not. > > FWIW, I thought it was a pretty straightforward explanation of what happened > and the steps they took to prevent it from happening again. > > …Tim > > -----Original Message----- > From: Matthew W. Ross [mailto:[email protected]] > Sent: Tuesday, March 05, 2013 12:38 PM > To: NT System Admin Issues > Subject: Re: Details of the February 22nd 2013 Windows Azure Storage > Disruption > > > What more can be said? Having had very similar issues where I work > > (co-worker patched and rebooted all the production servers in a small > > resource domain 3 days early because he clicked the wrong box) why > wouldn't > > you take this at face value? > > Because Microsoft wouldn't want to be sued by everybody who lost business > during the outage. It is in their best interest to say "Yup, it was a > problem, and we fixed it." It is _not_ in their best interest to say "Yup, > it was a problem. We forgot to do something we were supposed to do. We fixed > it." It's a small thing, but it's still important to those pesky lawyers. > > <cynic>And why wouldn't they lie, if it makes them look better anyways? > Maybe they had a much more major issue. Sure, it's more likely that they had > their certificate issue, but who knows.</cynic> > > > --Matt Ross > Ephrata School District > > > ----- Original Message ----- > From: Steven Peck > [mailto:[email protected]] > To: NT System Admin Issues > [mailto:[email protected]] > Sent: Tue, 05 Mar 2013 > 12:11:41 -0800 > Subject: Re: Details of the February 22nd 2013 Windows Azure > Storage Disruption > > > > Did you just manage to agree and also imply "Sure, they released it but > are > > probably still not telling us what 'really happened"? > > > > Because that's sort of what it seems like you just did. They said they > had > > a process and human error entered the process. Now that they know what > > happened they can take steps to hopefully reduce the chance of it > happening > > again. > > > > What more can be said? Having had very similar issues where I work > > (co-worker patched and rebooted all the production servers in a small > > resource domain 3 days early because he clicked the wrong box) why > wouldn't > > you take this at face value? > > > > Steven Peck > > http://www.blkmtn.org > > > > > > > > On Tue, Mar 5, 2013 at 10:36 AM, Matthew W. Ross > > <[email protected]>wrote: > > > > > Agreed, but I also know that all released information goes through PR. > I'm > > > sure this released report was scrubbed clean of anything that could have > > > made Microsoft liable. > > > > > > Heck, I'm guilty of a bit of spin. I accidentally plugged a switch back > > > into itself, causing a loop? My internal release states "A network > > > configuration error occurred". Sm:)e. > > > > > > > > > --Matt Ross > > > Ephrata School District > > > > > > > > > ----- Original Message ----- > > > From: Ben Scott > > > [mailto:[email protected]] > > > To: NT System Admin Issues > > > [mailto:[email protected]] > > > Sent: Tue, 05 Mar 2013 > > > 10:28:00 -0800 > > > Subject: Re: Details of the February 22nd 2013 Windows Azure > > > Storage Disruption > > > > > > > > > > On Tue, Mar 5, 2013 at 12:43 PM, Tim Evans <[email protected]> > wrote: > > > > > > > > > > > > > > > http://blogs.msdn.com/b/windowsazure/archive/2013/03/01/details-of-the-february-22nd-2013-windows-azure-storage-disruption.aspx > > > > > > > > I give MSFT credit for doing a good analysis and *publishing it*. A > > > > lot of companies just say "Sorry, we've fixed it, and we promise it'll > > > > never happen again (and this time, we really mean it)" over and over. > > > > Good on them for that. > > > > > > > > -- Ben > > > > > > > > ~ 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 > > > > > > > > > > ~ 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 > > > > > > > > > > ~ 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 > > ~ 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 > > > ~ 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 ~ 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
