Introduction
To keep you informed regarding the state of your cloud resources, Azure provides several experiences. This data covers recent and prospective problems, including service-impacting incidents, planned maintenance, and other modifications that can reduce your availability. In this article, we shall be learning more about it.
Azure Service Health
Three different minor services are combined to form Azure Service Health. On the Azure Status page, Azure status notifies you of any service disruptions in Azure. The webpage offers a thorough summary of the condition of all Azure services in all Azure regions.
Azure Status
On the Azure Status page, Azure status notifies you of any service disruptions in Azure. The webpage thoroughly summarizes the state of all Azure services in every Azure region. The status page is a helpful resource for issues with broad implications. Still, we firmly advise current Azure users to use Azure service health to keep up with incidents and maintenance affecting Azure.
Service Health
Your picture of the well-being of the Azure services and regions you're utilizing is provided by service health. Because the authenticated Service Health experience understands which services and resources you use, this is the best location to check for service-impacting information like outages, planned maintenance activities, and other health warnings. Setting up Service Health alerts to receive notifications via your preferred communication channels when service issues, scheduled maintenance, or other changes may affect the Azure services and regions you use is the best approach to make the most of Service Health.
Resource Health
Resource health details the condition of your unique cloud resources, such as a particular instance of a virtual machine. You can set up alerts in Azure Monitor to inform you whenever the availability of your cloud resources changes. You can keep track of your resources' accessibility. Minute by minute using Resource Health and notifications from Azure Monitor. You can rapidly determine whether a problem is caused by a problem on your end or connected to an Azure platform event.
34+ registered 
