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
