coreysa

4 ms·

1. 1.▲
   by coreysa 12y ago

   Almost everyone has fully recovered at this point. If you are still seeing problems with your Virtual Machine after the incident earlier this week, we want to help you!! Please send mail to azcommsm@microsoft.com and email me directly at co
2. 2.▲
   by coreysa 12y ago

   Thanks. The communications and the service health dashboard are two areas that we are creating improvement plans from the learning of this event. For the dashboard, we do expect it to continue to run even through outages like this one, but
3. 3.▲
   by coreysa 12y ago

   Keith, you can find more details in the RCA that is published here: http://azure.microsoft.com/blog/2014/11/19/update-on-azure-s... . It is updated with more details on the flighting and issues we encount
4. 4.▲
   by coreysa 12y ago

   Thanks. We are continuing to investigate this and driving needed improvements in our process and technology to avoid similar issues in the future.
5. 5.▲
   by coreysa 12y ago

   First, I am really sorry about the impact the incident had on your service. Specifically, for your changing IP, are you currently using the reserved IP feature. You can reserve both your external IP and your internal IP. External IP: http:
6. 6.▲
   by coreysa 12y ago

   Hey nnx, this is Corey from the Azure engineering team. We have a standard protocol in the team of applying production changes in incremental batches. Due to an operational error, this update was made across most regions in a short period o
7. 7.▲
   by coreysa 12y ago

   Hi, this is Corey Sanders, an engineer on the Azure compute team. Yes, our normal policy for updates is to roll them in incremental batches. In this case, due to an operational error, we did not apply the changes as per normal policy.