Hi, my name is Stephen Baron and I’m a program manager at Microsoft. Often, the Azure Status page, Azure Service Health, and Azure Resource Health get confused with one another. Today, I’ll be going over the differences between each of these services to show how to best leverage their distinct capabilities so you can keep your environment healthy and your IT organization informed. You may be familiar with the Azure Status page, a global view of the health of all Azure services across all Azure regions. While the status page is good for a quick reference for incidents with wide-spread impact, we highly recommend that you instead use Azure Service Health to stay informed of Azure incidents and maintenance. Azure Service Health provides a more complete and personalized view of the different types of issues that may impact your organization. Service Health provides you with a customizable dashboard which tracks the health of your Azure services in the regions where you use them. Here you can track active events like ongoing service issues, upcoming planned maintenance activities, or relevant health advisories. Service Health also lets you set up alerts so you can be notified via your preferred communication channels, when service issues or planned maintenance activities may affect the Azure services and regions you use. You can then dig into the details to see how the service was impacted, and how it is being addressed. Azure Resource Health, on the other hand, shows you the health of your individual resources—for example, a specific Virtual Machine or SQL database. You can see a resource’s current health status as well as the times they were unavailable in the past for any reason. Resource Health can also help you diagnose and get technical support when an Azure service problem affects your resources. Together, Azure Service Health and Azure Resource Health provide you with a personalized toolset to manage and monitor the health and status of your complete Azure environment.