After you experience a Microsoft Azure service issue, you likely need to explain what happened to your customers, management, and other stakeholders. That’s why Azure Service Health provides official incident reports and root cause analyses (RCAs) from Microsoft.
Showing 11 – 19 of 19 posts found
When your Azure resources go down, one of your first questions is probably, “Is it me or is it Azure?” Azure Service Health helps you stay informed and take action when Azure service issues like incidents and planned maintenance affect you by providing a personalized health dashboard, customizable alerts, and expert guidance.
Azure Service Health se développe pour que vous soyez toujours informé de la disponibilité de vos ressources Azure. Dès à présent, vous pouvez configurer des alertes d’intégrité des ressources pour être immédiatement informé lorsqu’une ressource ne sera pas disponible en raison de problèmes sur la plateforme Azure, et cela même avant que les pannes ne soient déclarées.
Today I am excited to announce the general availability (GA) of Azure Service Health, a personalized dashboard that provides guidance and support when issues in Azure services affect you.
An industry-wide, hardware-based security vulnerability was disclosed today. Keeping customers secure is always our top priority and we are taking active steps to ensure that no Azure customer is…
When an Azure service incident affects you, we know that it is critical that you are equipped with all the information necessary to mitigate any potential impact. The goal for the Azure Service…
On November 18, 2014, many of our Microsoft Azure customers experienced a service interruption that impacted Azure Storage and several other services, including Virtual Machines.
Yesterday evening Pacific Standard Time, Azure storage services experienced a service interruption across the United States, Europe and parts of Asia, which impacted multiple cloud services in these regions. I want to first sincerely apologize for the disruption this has caused.
Introduction As a follow-up to my March 1 posting, I want to share the findings of our root cause analysis of the service disruption of February 29th. We know that many of our customers were…